Re: #;

Alan Crowe wrote:

If you are are interested in helping

http://www.cawtech.demon.co.uk/lisp/symbols-and-packages.html

is half done and in need of criticism.


Well, one minor thought - I get what you're saying with "hierarchical",
but there might be a tiny opportunity for confusion with the dotted
hierarchical/relative package _naming_
(i.e. "com.example.foo.bar:baz") extension that several lisp
implementations support (as something a bit more than a mere package
naming convention due to meaning attached to relative paths
e.g. "...stuff.impl.x:y")

http://common-lisp.net/project/cmucl/doc/cmu-user/extensions.html#toc21

But dunno whether it would be in keeping with the style of the doc to
note that some implementations provide support for hierarchically
structured package naming and that's a separate issue and not at all
what you mean.





.

Relevant Pages

  • Re: Tablelist under 8.5
    ... than it won't collide with the current naming of the original ... IMO it's worth thinking of changing the package names to be ... suggestion is not about to change the syntax of tcl, ... What are the drawbacks of case sensitivity? ...
    (comp.lang.tcl)
  • Re: [kde] rc1 advice needed
    ... On Wednesday 23 Jul 2008 7:54:56 pm Anne Wilson wrote: ... There was a change in naming of that package within the kde repository. ...
    (KDE)
  • Package nicknaming at :use time or reader time
    ... package by a nickname defined in the using package? ... means that I am back to having to worry about global symbol naming ... 0xE9758B7D or 'Peter Schuller ' ...
    (comp.lang.lisp)
  • Re: help with python-devel!!!
    ... April 2005 20:54 schrieb John Ridley: ... > The OP mentioned that urpmi couldn't find a package by that name. ... Naming makes getting at devel-packages a guessing-game at best. ...
    (comp.lang.python)