> I was under the impression that now is the best time ever to get 
> needed things into the image.  The "Message eating null" and 
> namespaces are big controversial things that can't be ignored once 
> present.
But in actual fact in these two cases they CAN be ignored once present.

However I happen to think that it would be useful if they were present, 
Null in particular.

For example I use Object-#log as a handle to a ProcessLocalLog instance 
which plugs in to the logging technology of your choice (toothpick 
/simple log etc). In moving towards the kernel image ideal, all of the 
Transcript stuff in the core could be ripped out and use "self log 
kernel: message" instead, the base implementation of which can return 
Null if no logging package is loaded.

As an excercise I think that it is interesting that if you cant get two 
or three methods of the importance and usefullness of split and join 
into the image (and btw unless I am mistaken there is no existing idiom 
for split) then you cant get anything in there, unless of course you 
happen to be the one in charge.

cheers

Keith