> > > - The source looked ugly to me (I reformatted it a little bit)
> > I am the only person in the world who formats C++ code in that
particular
> > way (lining
> > up left and right curly braces)
>
> Don't know how it should have looked (I can live with nearly anything,
since
> one of our developers in the czech republic uses something he call
"kernigan
> and ritchie"-style (don't even know if I have got the names right) while
> programming in Java :-(
K&R is kinduva dinosaur way of doing C function declarations as in:
somefunction(x,y,z)
(
int x;
char y;
char *z;
)
{
}
Or something like that anyways.
>
> > > - It didn't worked for me without passing any argument (it passed
"null"
> > to
> > > main() instead of an empty array)
> > I guess it should probably spit out a usage message.
>
> That was mainly a problem of Ant - it simply didn't expect to *not* get a
> String[] passed to main() (I don't think something like this can happen
> normally).
I don't know either. I seem to remember encountering both null and
zero-length String[] objects
being passed. Should probably be changed to pass zero-length String[] array
to main
>
> > > Some problems remain:
> > > - Doesn't work with JDK 1.1 (Don't know how to start a VM?)
> >
> > The invocation API is entirely different with 1.1 JVMs. Is it worth
> > supporting 1.1 JVM's?
> >
>
> I have just mentioned it for completeness - personally I don't have a
> problem with running Ant under JDK 1.3/1.4, even if the Application I'm
> building is based mainly on MS's VM. It's just that current Ant versions
> state that they are mostly compatible with JDK 1.1.
The new invocation API works with 1.2/1.3/1.4 it's just 1.1 that it doesn't
work with.
Of course Microsoft's 1.1 JVM is invoked differently again from
Sun/IBM/Blackdown's JVMs.
>
> > > - You can't pass any arguments to the VM (to specify memory sizes)
> >
> > How do we differentiate between arguments meant for the VM and arguments
> > meant for ANT?
> >
>
> I don't know - maybe just pass anything that starts with a "-"-sign to the
> JVM or start VM-Parameters with -J-realarg like some other apps are doing
> it.
If ANT itself takes no "-" parameters I like that idea better. Or maybe the
VM params can be read
from a file in the same directory as ant.exe? The whole point of ant.exe is
to replace the .bat file
which presumably a user would have to modify to pass parameters to the JVM.
So maybe an jvm.options
file or something like that?
-Mike
>
> Nico
>
>
>
