[Nickle] Artificial distinction between import and autoimport

[Keith Packard]

On Fri, 2008-02-01 at 19:41 -0800, Bart Massey wrote:

> In a Nickle program intended to be invoked externally, you'd
> typically just say
> 
>   autoimport Socket, File, Process;

Sure, but why 'autoimport' instead of just 'import'? There's no reason
to make the user know what is included in the base system and which
parts are external. We should be able to uniformly replace 'autoimport'
with 'import' and have things 'just work'. Similarly, it would be nice
to have 'load' have the same trick of looking for the conventional file
for a specific namespace.

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : /pipermail/nickle/attachments/20080202/753d5390/attachment.pgp