newlispfanclub.alh.net

I've tested again using other source strings, and the error occurs again. It seems that this error is not caused by the `string' command, but the representation of long string with quotes. That is, we have to represent long string in the format [text] long string [/text] or {long string} instead of ...

I just found that it directly captures the ouput of newlisp from stdout, I will search for some other ways to solve. Anyway, I encountered another problem, maybe a bug? it's that read-expr and eval-string will report ERR: string token too long : ...(some string)... if the length token is greater tha...

Normally, functions string will wrap the contents with quotes, just like: (string '(a b c)) => "(a b c)" but when the text becomes too long, then it will wrap it with [text][/text] markup instead of quotes("). Is there a way to keep using quotes? (string (symbols)) => "(...)" instead of (string (sym...

Thanks Lutz.

It's very nice to feel that the tool in hand becomes much more powerful.

Works all right under Linux for now.

This trick works!

And I think we should always use this trick when using a context as a data
container inside a module.

Thanks again for being so patient. And surely I will stay with newlisp, it is
just amazing.

Thank you very much Lutz. Now I have more confidence in using dynamic scope. And understand that we can avoid variable capture by putting macros(fexprs) into a seperate context, and use it inside another context. Without interactions, no variable caputure will ever happen to macros(fexprs). Just for...

Use only one context per module file. Different programmers maintain different contexts. The MAIN context is the only place where other contexts should be loaded and controls the main organization of the program and is maintained by a lead programmer. No context should redefine functions during run...

I am new to newLISP, and just can't find out how to solve this problem. As we know, we can surround a macro to avoid variable capture. But if we write two diffierent modules without knowing the other one, we might encounter a context collision, i.e. useing the same name for context. here is an examp...