4 ms·
Many years ago, when I was designing a part in AutoCad, I drew it by hand and then back-converted the drawing into parametrized AutoLISP, which I then stored un
by jhawkinson 12y ago
Many years ago, when I was designing a part in AutoCad, I drew it by hand and then back-converted the drawing into parametrized AutoLISP, which I then stored under version control (RCS at the time).
It'd be nice to have tools that make this easy. Though I'm honestly surprised more people don't do it anyhow.
- brudgers 12y agoWith AutoCad or any software that exports DXF or IGES, Git or other version control would work fine. Nemetscheck VectorWorks wil export a design file as VectorScript [a super-set of Pascal].
- dugmartin 12y agoYou can version AutoLISP but the output is so verbose (at least for machine generated code) that diffing versions is like diffing PDFs or PCL files. You can see the changes but they don't make any sense without the whole file being rendered. NOTE: Its been 20 years since I used AutoLISP and the code I was using was being generated from software that did cut-plan optimization for lathes so I am probably speaking from a very old/ignorant point of view.
- jhawkinson 12y agoHuh? The whole point was to version the AutoLISP source, not its output. And I didn't really mean machine-generated code...human-generated. And of course, as for making sense, well, you have to use good commit logs as well. But maybe you're talking about some technology that generates AutoLISP from a GUI? I don't know anything about that...