lisp2arx
Visual Programming for AutoLisp
Mathématiques en programmation Lisp..
doc2cpp,doc2lsp, sld2lsp, bmp2dcl,
free__GifCcapture for all-CAD'platforms..
|
Lista Forumurilor Pe Tematici
|
lisp2arx | Reguli | Inregistrare | Login
POZE LISP2ARX
Nu sunteti logat.
|
Nou pe simpatie:
Pisii
 | Femeie
24 ani
Ialomita
cauta Barbat
24 - 44 ani |
|
|
zauchan
Moderator
Inregistrat: acum 13 ani
Postari: 180
|
|
LISP is still hanging around as a platform, VBA maybe/absolutely is/was going away because its 32 bit and with 64 bit CAD and 64 bit OS and not wanting to update it and yada yada yada (Microsoft really just hates it's users).
Code:
Author: Keith™@Villiage Idiot- Seagull |
C# and VB (.net versions) are not a terribly steep learning curve for someone with programming background. They are also easily translated between one another ... if you can write one, you can pick up the other one quickly enough. They are also much more powerful and you can get into some really awesome stuff with them over LISP, but admittedly, there are some things that are just simpler to do in LISP. (Don't ask me to provide examples, I no longer use CAD on a daily basis ... I just write software and babysit a few thousand workstations and a couple dozen servers, all while being an awesome real estate investment guru and slum lord)
Anyway, for scalability C# might be a solution, but you should be aware that with the power of C# comes the overhead of version management. With LISP it is relatively easy to write code that will work on multiple releases, just don't expect to use (command "something" "a" 1 varB ect) copiously and expect it to work between versions. Autodesk warns us that command options can and do change between releases. You should opt for the long way of doing things like (entmod(subst (cons 10 newpoint)(assoc 10 elist) elist)) instead of (command "._move" ent "" "@" newpoint) NOTE: Syntax not guaranteed ... I have not written LISP in over 14 years ... well, ok, maybe I have written some BUT NOT MUCH!
Code:
Acest popii beti, mie imi confirma ce am trăit prin bisercii= Gravitatie pămăntului (poate doar inEuropa de Est si Rusia), ne trage in jos pe multii semeni la stadiul animalic. Doamne iarta-i pe acesti popii betii, Doamne milueste-i, eu un păcătos ultimul dintre ei. Eu ii apăr si nu este, aici Daniel Balas, greseste. Cănd după moartea fizica ajungi in stadiul animalelor, Daniel Balas ajunge sobolan, iar popii betii ajung căini, maimute. sau cai. Eu pe cine aleg, tu sau unul din ei?(ironic) |
C#/VB applications may require being rebuilt whenever AutoCAD is updated due to changing libraries. The DLLs linked to the application are generally done at design-time and are many times not allowed to be dynamically linked (yeah I know ironic right .. kinda goes against the whole idea of "dynamic link library" now doesn't it ... you should try dynamically linking a library that you don't even know the name of or where it is located >I MADE THIS< ). Anyway, if you can live with the idea of having 2 or 3 or 6 different builds of the same application based on the current versions of AutoCAD you have installed and plan on keeping installed, then it can be a huge boost for integration and scaling. On the other hand, it does require a lot more work to keep it oiled well.
Personally, with the little bit of design work that I do, I am still nursing along lisp functions that were written in 1986 without ever having been changed and I have some VBA that I will continue to use (until VBA is officially officially officially officially declared dead) because converting it at this point is really just academic and no intrinsic benefit can be derived from doing so. When it dies, I'll simply build something similar or better in C# and call it a day at that point. Or maybe I'll get lucky and it will be supported until I meet my maker and then I won't care. Either way, I win.
This + LISP proficiency serve your career magnitudes more than VBA + LISP, notwithstanding vastly increase the landscape of automation possibilities (arguably) more than any other CAD centric combination -- if limited to 2, which is probably a good strategy at the beginning. However, the fact that LISP & VBA are available for free and ostensibly available on any machine (albeit sometimes via free download / install) is also a factor, albeit VBA is no longer evolving. Look at it from the perspective of employers and the "productivity glasses" they wear, after all the bottom line is employ-ability and cost/benefit ratios etc. TLDR: Talk to mgmt, identify what they consider valuable, align yourself accordingly.
39.8KB
_______________________________________
psw: cea de la wjndowsXP gigabyte..
|
|
| pus acum 3 ani |
|
