On 5/1/06, Archie Cobbs [EMAIL PROTECTED] wrote:
Weldon Washburn wrote:
There was an unexpected and surprising parsing problem when running
_209_db on JCHEVM. The procedure called, _jc_parse_classfile(), does
some basic verification of a class file. In specific, it verifies
that a class
Ok - so this is an aspect of modularization, rather than some deranged
bending of package implementation? :D
So if a module has public packages A, B and C would it be :
org.apache.harmony.module.A
org.apache.harmony.module.B
org.apache.harmony.module.C
org.apache.harmony.module.internal
not
Weldon Washburn wrote:
Good idea. I will try to look at mauve soon. I don't know anything
about it. Do you know if there there any Apache license compatibility
issues?
Not unless you're planning to resell it or something... :-)
-Archie
Geir Magnusson Jr wrote:
We have 9 votes in favor, none against, and one reasonable question
about destination.
I think that we should let Archie bring it into SVN. :) It was
suggested as
enhanced/gnuclasspathadapter/trunk/
but I'd suggest
Archie,
Thanks for getting this entered into SVN so quickly. I did a quick
check and it looks like you grabbed the most recent version. By the
way, the directory structure is still somewhat ambiguous. I keep
thinking we may want to put .../gnu.../... in the tree to distinguish
this specific
Weldon Washburn wrote:
Thanks for getting this entered into SVN so quickly. I did a quick
check and it looks like you grabbed the most recent version. By the
way, the directory structure is still somewhat ambiguous. I keep
thinking we may want to put .../gnu.../... in the tree to distinguish
Archie Cobbs wrote:
Weldon Washburn wrote:
Thanks for getting this entered into SVN so quickly. I did a quick
check and it looks like you grabbed the most recent version. By the
way, the directory structure is still somewhat ambiguous. I keep
thinking we may want to put .../gnu.../... in
Geir Magnusson Jr wrote:
I agree. How about classlibadapter/trunk - adapter/gnu/trunk?
I'd keep it specific to classlib yet simple and mimic the classlib
structure with
classlibadapter/trunk/module/gnu
or something.
OK... although I'm not sure what purpose the module part serves.
We
Archie Cobbs wrote:
Classpath? The assumption here is that you don't need to have GNU
Classpath, right?
Argh, my apologies, for some reason I was thinking completely backwards.
Ignore most of what I said :-)
OK now I remember why I thought that before: if you're going to be using
JVM X