On Sun, Dec 17, 2000 at 07:40:02AM +0900, Ing. Roman Fischer wrote:
> A jar-file just contains the classes and other files of your application.
> This concept still expects a Java-VM at the target machine and a call of a
> method inside of the jar. So you cannot deliver a self-installing
> application by just putting all your classing into a jar.

all true.  what i meant was, assuming target machines have a ruby 
interpreter installed, it would be nice to have a utility along the lines 
of 'jar' which allowed for many distint class files to be archived 
together.  perhaps then the whole shebang could be run with:

ruby AllMyClasses.rbar

as you point out, this isn't the same as having an executable to 
distribute to computers which don't already have ruby installed.  it only 
helps those of us who like to have separate files for each class (as in 
Java) but don't want to distribute more than one file.

`m