Hi List,
I deal in PicoLisp with keyword symbols imported from Emacs Lisp that
look like
,-
| :keyword
`-
They probably should be uppercase due to PicoLisp naming conventions.
However, isn't the ':' at the beginning enough to avoid conflicts with
other global symbols? If that would be
Hi Thorsten,
> I deal in PicoLisp with keyword symbols imported from Emacs Lisp that
> look like
>
> ,-
> | :keyword
> `-
>
> They probably should be uppercase due to PicoLisp naming conventions.
> However, isn't the ':' at the beginning enough to avoid conflicts with
> other global symb
Alexander Burger writes:
Hi Alex,
> The ':' shouldn't conflict. You can find that out (after 'load'ing all
> relevant files in debug mode) with
>
>: (what ":@")
>-> (: ::)
ok, I see, thanks for both answers (other post too).
--
cheers,
Thorsten
--
UNSUBSCRIBE: mailto:picolisp@softwa
Hi Thorsten,
> > The ':' shouldn't conflict. You can find that out (after 'load'ing all
> > relevant files in debug mode) with
> >
> >: (what ":@")
> >-> (: ::)
BTW, will there be any conflict at all?
An internal symbol pre se will never conflict. It is its binding (value
or function def
Alexander Burger writes:
Hi Alex,
>> > The ':' shouldn't conflict. You can find that out (after 'load'ing all
>> > relevant files in debug mode) with
>> >
>> >: (what ":@")
>> >-> (: ::)
>
> BTW, will there be any conflict at all?
>
> An internal symbol pre se will never conflict. It is
Hi Thorsten,
> > An internal symbol pre se will never conflict. It is its binding (value
> > or function definition) or properties that may conflict.
> >
> > As I understand it, those :keywords have no special value bindings (?)
>
> Hmm ... they come along as a 'free' property list in Emacs Lisp
