« How To View, Verify and Activate Your BricsCAD Licenses | Main | My Daughter Sanjna's eco-Projects Mentioned in 'The Hindu' »

December 10, 2013

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

knosperos

Hi,
as a AutoCad long-term User (since v9) I can assure you, lisp debugging was only slightly easier then, if one did it only from the cmd line. In a bad error case, you could get several hundred lines of spaghetti lisp recursive from the point the error happened.
The way to get this output still exists, but is hidden in some error trap settings.
However, I do not really understand why one would not use Visual Lisp, as it is integrated and easy to call by the VLIDE command.
I also cannot follow the "with which the command line disappears and hides itself", but that may have been a behavior of that versions which I did not realize then.
I sympathise with the way Bricscad provides a cheap Autocad alternative on a broad functional spectrum, albeit there is no way to get arx applications running without a recompile to .brx with their libraries.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Comments are moderated, and will not appear until the author has approved them.

Your Information

(Name and email address are required. Email address will not be displayed with the comment.)