On Sat, Jan 25, 2014 at 7:39 PM, Alexander Burger wrote:
> Hi Christophe,
Hi Alex.
> I'm not sure if I exactly understand what your problem is, but let me
> try to explain a bit.
> …
I think I'm now OK with PicoLisp returning "read'able" transients.
But understanding the mechanism doesn't solve
Hi Christophe,
I'm not sure if I exactly understand what your problem is, but let me
try to explain a bit.
The backslash character is a meta-character in PicoLisp symbols (like in
many other languages). So, to get the backslash itself, you have to
escape it with another backslash.
Other meta-ch
On Sat, Jan 25, 2014 at 3:01 PM, Thorsten Jolitz wrote:
> what about this (although no slash at all remains):
>
> ,---
> | : (pipe (out (prin "(This 'is (not) \"\\code\" ..)")) (setq X (read)))
> | -> (This 'is (not) "code" ..)
>
Christophe Gragnic
writes:
> On Fri, Jan 24, 2014 at 10:54 PM, Axel Svensson
> wrote:
>> If you need to output something that isn't 'read' readable, then you're
>> trying to output something that isn't lisp code. If that is the case, use
>> the functions to output text rather than code.
>>
>> (p
On Fri, Jan 24, 2014 at 10:54 PM, Axel Svensson wrote:
> If you need to output something that isn't 'read' readable, then you're
> trying to output something that isn't lisp code. If that is the case, use
> the functions to output text rather than code.
>
> (prin "(This 'is (not) \"\\code\" ..)")
Hi,
If you need to output something that isn't 'read' readable, then you're
trying to output something that isn't lisp code. If that is the case, use
the functions to output text rather than code.
(prin "(This 'is (not) \"\\code\" ...)")
/Axel
On Fri, Jan 24, 2014 at 10:27 PM, Christophe Grag
