Hi Thorsten,
> > How did you invoke PicoLisp? Does this also happen if you invoke just as
> >
> > $ pil +
> >
> > i.e. PicoLisp alone, without Emacs?
>
> No, that works, although there are is someting strange happening too:
> some of the strings in the list are replaces by NIL, and it seems as if
You said that you call it as
(setq X (list "string1" ... "string200"))
Note that this evaluates the transient symbols "string1" etc., so if one
of them has a value NIL (or anything else), it will be included in the
list.
What you actually want to do is
(setq X '("string1" ... "string200"))
> the '\' that signals a linebreak in an Emacs buffer is somehow
> misinterpreted as an escaping backslash
A backslash at the very end of a line causes PicoLisp to continue
reading the next line, skipping possible white space:
: "abc\
def"
-> "abcdef"
A linebreak by itself has no special meaning, but will be included
into strings, of course, if not escaped in the above way.
Cheers,
- Alex
--
UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe
