Hi Thorsten,
When I already have property list like
,--
| ((key1 . value1) (key2 . value2) ... (keyn . valuen))
`--
Note that the list has the cons pair elements reversed:
((value1
Hi Jon,
OK, so for now I moved -lcrypt flag to a Makefile variable LCRYPT, and
assigned -lcrypto for Darwin and the BSD family.
Though it doesn't give strong encryption at the moment, at least it
compiles and is better than nothing ;-)
♪♫ Alex
--
UNSUBSCRIBE:
Alexander Burger a...@software-lab.de writes:
Hi Alex,
When I already have property list like
,--
| ((key1 . value1) (key2 . value2) ... (keyn . valuen))
`--
Note that the list has
Hi List, when I write a library with its own namespace, and want
a 'global variable' in that namespace that stores 'vital
information' for the library - do I use the '*Var' syntax or is
that reserved for variables that are really global in PicoLisp?
I could of course just name it 'Var',
Hi Thorsten,
Hi List, when I write a library with its own namespace, and want a
'global variable' in that namespace that stores 'vital information'
for the library - do I use the '*Var' syntax or is that reserved for
variables that are really global in PicoLisp?
I would say that '*Var' is
Alexander Burger a...@software-lab.de writes:
Hi Alex,
I would say that '*Var' is all right.
Yes. Also, 'Var' is meant to denote symbols which are bound
locally/dynamically.
BTW Are constants in uppercase (like 'MYCONST')
acceptable in PicoLisp?
Yes. I haven't seen or used many