Hi Tomas,
Personally I am not a fan of namespaces in picolisp.
Yes. As you know, I am neither.
However, the current implementation won't do any harm, as long as it is
not actually used (and I won't probably use it ;-)
It is a simple extension of the general principles underlying PicoLisp
Importing symbol from another namespace can be done with
(intern 'myNames~Foo)
- Foo
This will make the symbol 'Foo' from 'myNames' available as an internal
symbol in the current namespace.
This is imo a must have feature, it has to be up to the programmer to avoid
clashes as it is
On Mon, Sep 19, 2011 at 02:51:32PM +0700, Henrik Sarvell wrote:
Having to write the full name all the time could easily become comical, as in
my above Clojure example. This is also one of the reasons I have leaned
towards
+1
Imagine all the rants which could be made about code full of both
Jakob Eriksson ja...@vmlinux.org writes:
On Mon, Sep 19, 2011 at 02:51:32PM +0700, Henrik Sarvell wrote:
Having to write the full name all the time could easily become
comical, as in my above Clojure example. This is also one of the
reasons I have leaned towards
+1
Imagine all the rants
Henrik Sarvell hsarv...@gmail.com
writes:
I can understand both your arguments Thorsten but in the end there
must've been a reason why you found PicoLisp interesting enough that
you wanted to try it out as opposed to using elisp/common lisp for
everything.
Perhaps it was the brevity and
(func '+Kadabra arg1 arg2)
is shorter than:
(foo.bar.blabla.abra.kadabra.func arg1 arg2)
no, it's similar to (Kadabra.func arg1 arg2).
(func '+Foo.bar.blabla.abra.kadabra arg1 arg2) is similar to
(foo.bar.blabla.abra.kadabra.func arg1 arg2).
Cheers,
Tomas
--
UNSUBSCRIBE:
