Re: Re: hierarchical packaging (was: Java API)

Hi Ralf,

> Package helps with my most pressing concerns. But since you
> asked, let me add a few suggestions for possible improvements:
> 
> o You want to document the public interface a module provides.
>    So using package you should need to state what you want to
>    be public not what you want be private. The syntax could
>    look like this:
>    (package <package-name>
>             (<symbol1> ... <symboln>) ;; public defs
> 
>      (de there (goes) (your-code))
>      ...
>    )
> 

Actually, the access specification is implementation dependent. In the Lush case,
it follows the Common Lisp standard. This public first orientation is similar to 
Java (or C structs), but opposite to C++ classes.

What's really missing are functions to manage and interrogate packages after
they are loaded.

Raymond




__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642