Another excellent idea.
I have often wondered whether it would be a good idea to compile all the
pl parts of Rosettacode into a single document!
Thank you very much.
On Fri, 2012-07-20 at 14:45 +0200, Alexander Burger wrote:
> On Fri, Jul 20, 2012 at 02:32:00PM +0200, Thorsten Jolitz wrote:
> >
Hi List,
related to the nice idea of publishing the Rosettacode examples (which
would actually be nicer _with_ the task descriptions included) I have a
few (probably rather newbie) technical questions about manipulating the
file-system and processing text in PicoLisp:
1. How to make, concat, an
Hi Thorsten,
> 1. How to make, concat, and kill files (and directories) on Linux with
>PicoLisp? Using the system functions?
For making files where you will usually use 'out', and write directly to
the file.
To concat two files, you could do:
(out "c" (in "a" (echo)) (in "b" (echo)))
Er
Hi Thorsten.
Below I've pasted links to descriptions of functions that might or might
not be what you want based on a quick glance on your questions:
1.) http://software-lab.de/doc/refC.html#call
2.) http://software-lab.de/doc/refM.html#match
3.) I don't really get this one, isn't it possible f
Alexander Burger writes:
Hi Alex,
thanks a lot, thats what I needed to know, now I have to give it a try.
>> 3. Is it possible to use 'prog' or 'let' with 'apply', i.e. apply a
>>whole sequence of functions instead of only one to the 'lst argument?
>
> I'm not sure what you mean here. Perh
Hi Alex,
For quite some time I've felt that the ref. documentation for the 'for'
forms could need some improvements. The 'for' function is a very
important function, and for most people who are new to PicoLisp, it will
be one of the first functions they will have to learn. At the same time,
t
Henrik Sarvell
writes:
Hi Henrik,
> Below I've pasted links to descriptions of functions that might or
> might not be what you want based on a quick glance on your questions:
>
> 1.) http://software-lab.de/doc/refC.html#call
>
> 2.) http://software-lab.de/doc/refM.html#match
Thanks, I will loo
Hi Jon,
> For quite some time I've felt that the ref. documentation for the
> 'for' forms could need some improvements. The 'for' function is a
Very true!
> What I've done is (a) inserted a few line breaks so that the
> descriptions of the three forms are separated, and so that it will
> be a
Hi List,
I have a rather strange problem:
I want to (from within Emacs)
,--
| (setq X (list "string1" ... "string200"))
`--
and it seems PicoLisp just freezes - no error messages, but no output
either, and the proc
Hi Thorsten,
> Is there something like an upper limit for how many Strings can be in a
> list in PicoLisp? Or might that be Emacs related?
No, there is no limit. Neither to the length of the command line (if you
use the built-in line editor).
How did you invoke PicoLisp? Does this also happen if
Alexander Burger writes:
Hi Alex,
>> Is there something like an upper limit for how many Strings can be in a
>> list in PicoLisp? Or might that be Emacs related?
>
> No, there is no limit. Neither to the length of the command line (if you
> use the built-in line editor).
>
> How did you invoke P
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
Alexander Burger writes:
> For making files where you will usually use 'out', and write directly to
> the file.
>
> To concat two files, you could do:
>
>(out "c" (in "a" (echo)) (in "b" (echo)))
>
> Erasing a file is not implemented as a PicoLisp function. You can simply
> call 'rm'
>
>(
Alexander Burger writes:
Hi Alex,
> 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 wa
AFAIK out doesn't do auto dir creation or any dir creation for that matter.
Looks good but the cd thing should not be necessary, just use the absolute
path in the last call.
Note that you can use info to check stuff, could possibly be used in a
function that checks a certain path from top to bott
Henrik Sarvell
writes:
> AFAIK out doesn't do auto dir creation or any dir creation for that
> matter.
ok
> Note that you can use info to check stuff, could possibly be used in a
> function that checks a certain path from top to bottom and creates any
> missing dirs on the way. Ie if new exists
Hi Thorsten,
> Is there a way to make 'out' write directories too?
No, 'out' just creates or opens a file for writing.
> Or do I have to use something like
>
> ,--
> | (call 'mkdir "/new/dir/")
> `--
Yes. But this works only if "/new/" already e
17 matches
Mail list logo
