newlispfanclub.alh.net

On newLISP FAQs page, section 6 Does newLISP have hash tables? , "better for key acces" should be "better for key accessing" (I think accessing is better than access since we're talking about the act, not the capability, right?) The link to "Problems with hash tables" is dead. Please fix them.

How about implementing newLISP inside ANSI Common Lisp? I'm (slowly) doing one with Emacs Lisp.

I see. I just want to write functions with functional programming style. In my oppinion, it's a disadvantage of newLISP not to have tail call optimization.

I have done some search in the forum but yet I haven't found the answer for a just-out-of-curiosity question: Does newLISP do tail call optimization?

I discovered some small errors on the page " Differences to Other LISPs "[1], a couple of lines before section " Implicit Indexing ": "readong/translation" should be "reading/translating" "This wayte h overhead" should be "This way, the overhead" Please fix them. [1]: http://www.newlisp.org/index.cg...

Thank you very much! I'm using ROXTerm in Gentoo GNU/Linux with Zsh and it works beautifully :-).

Now I understand. ASCII's 033 in octal is equivalent to 27 in decimal. (Somehow) newLISP uses decimal system to describe escape codes instead of octal.

Hi guys, I'm developing a console application which makes use of VT-100 compatible terminals. Usually, to produce text color, I use the escaped phrase `\\033$COLOR_CODE`. For example, to output the world "Hello world" in red, I use echo "\\033[41mHello world!" In newLISP, I tried to do the same thin...

Should these notes be available on newLISP Code Patterns or newLISP Manual and Reference, guys? I think extra cautions, especially cautions about memory, are never redundant. Right?

Thank you, Lutz. That makes sense. Let me summarize a little bit to see if I really understand it right. Please correct me if I'm wrong: Any allocation performed by foreign functions (functions which are imported from shared libraries) has to be deallocated manually if there's no call to do so . In ...

Hi newLISPers, I have a question about memory management when loading shared library. In C/C++, after finishing using a library, one needs to unload it to ensure that: memory is properly deallocated, and the system could do some clean-up, like closing file handlers, ... In newLISP, should/must we us...