TemporaryCAD Posted August 8, 2022 Share Posted August 8, 2022 This is really quite odd, I'm trying to work on a program and doing basic things are returning syntax errors. I was trying to create a list, with (setq lst (list 0.0 0.0)), and it was returning a syntax error. I thought it was weird but it's a monday morning, so I went to the autolisp documentation and attempted to use the given code. This is the result: Command: (setq lst1 (list 1.0 "One" 1)) ; error: syntax error Why is this happening? In another file everything is working fine, but this single file prevents me from using normal commands. I've already tried cancelling a bunch of times in case I was stuck in a subroutine. Quote Link to comment Share on other sites More sharing options...
mhupp Posted August 8, 2022 Share Posted August 8, 2022 Sometimes things get stuck have you tried closing down everything? I mean all the drawings in AutoCAD and AutoCAD itself. Quote Link to comment Share on other sites More sharing options...
Jonathan Handojo Posted August 8, 2022 Share Posted August 8, 2022 (edited) Not a bad solution @mhupp. I don't know how else it would have been. Edited August 8, 2022 by Jonathan Handojo Quote Link to comment Share on other sites More sharing options...
BIGAL Posted August 9, 2022 Share Posted August 9, 2022 Because I write and test as I go crashes in code are frequent sometimes like as Mhupp has suggested I close everything and open again and code works. Quote Link to comment Share on other sites More sharing options...
Steven P Posted August 9, 2022 Share Posted August 9, 2022 14 hours ago, BIGAL said: Because I write and test as I go crashes in code are frequent sometimes like as Mhupp has suggested I close everything and open again and code works. and likewise a code that you have tested along the way 'works' until you restart everything (often a forgotten variable hanging about).... restart is always a good 'nearly finished' test of a code 1 Quote Link to comment Share on other sites More sharing options...
Lee Mac Posted August 9, 2022 Share Posted August 9, 2022 Sounds like you've redefined a protected symbol - I would suggest enabling this option within the VLIDE to alert you to such: Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.