What is the most efficient method in converting AutoLISP legacy code to C#?
I am engaged in a project that works mainly in AutoCAD to design and manufacture prefabricated building components such as roofing trusses. One of our goals is to redesign a program that was written in LISP that functions in designing roofing trusses. We are to rewrite the LISP code in C# and incrementally implement it into the current libraries that they have set up.
Object-Oriented equivalent of LISP’s progn function?
I’m currently writing a LISP parser that iterates through some AutoLISP code and does its best to make it a little easier to read (changing prefix notation to infix notation, changing setq assignments to “=” assignments, etc.) for those that aren’t used to LISP code/only learned object oriented programming.
Object-Oriented equivalent of LISP’s progn function?
I’m currently writing a LISP parser that iterates through some AutoLISP code and does its best to make it a little easier to read (changing prefix notation to infix notation, changing setq assignments to “=” assignments, etc.) for those that aren’t used to LISP code/only learned object oriented programming.
Object-Oriented equivalent of LISP’s progn function?
I’m currently writing a LISP parser that iterates through some AutoLISP code and does its best to make it a little easier to read (changing prefix notation to infix notation, changing setq assignments to “=” assignments, etc.) for those that aren’t used to LISP code/only learned object oriented programming.
Object-Oriented equivalent of LISP’s progn function?
I’m currently writing a LISP parser that iterates through some AutoLISP code and does its best to make it a little easier to read (changing prefix notation to infix notation, changing setq assignments to “=” assignments, etc.) for those that aren’t used to LISP code/only learned object oriented programming.
Object-Oriented equivalent of LISP’s progn function?
I’m currently writing a LISP parser that iterates through some AutoLISP code and does its best to make it a little easier to read (changing prefix notation to infix notation, changing setq assignments to “=” assignments, etc.) for those that aren’t used to LISP code/only learned object oriented programming.
How do you make decorators as powerful as macros?
Quick background: I am designing a Pythonic language that I want to be as powerful as Lisp while remaining easy to use. And by “powerful”, I mean “flexible and expressive”.
Reference counting & GC in LISP [closed]
Closed 9 years ago.
Reference counting & GC in LISP [closed]
Closed 9 years ago.
`values` vs `list` for returning multiple values from Lisp form
What’s the difference between using (values …) versus (list …) (or literally '(one two three …)) to return multiple values from a lambda (or other implicit progn)? Does it create some special glue to multiple-value-bind? Superficially, I can’t see any difference and am curious whether it’s merely a convention for multiple return values.