Bryce McKinlay ([EMAIL PROTECTED]) wrote:
gcj cannot yet compile classpath from source code, because it cannot handle
inner or anonymous classes. Work on these and other "JDK-1.1" features is in
progress. In the mean time, gcj should be able to compile most of classpath with
the aid of an
Aaron wrote:
This is interesting. When does gjc plan to support inner classes? These
are absolutely needed to implement parts of the API.
The work is going on right now. It won't be too much longer.
AG
--
Anthony Green Cygnus Solutions
[ Resending this because it got lost last time? ]
Jochen Hoenicke wrote:
If there is a code-formatting tool I don't see a reason why we
shouldn't convert. We should make sure that nobody has pending
changes to that class before converting them, though.
Great - I will experiment with the
Mark Wielaard [EMAIL PROTECTED] writes:
Yes I would very much like to see one coding style use.
It would be nice if old code could be automatically reformatted.
And it would probably help the coders if there where syntax files
for this style for popular editors.
If no one else does, Paul
"Bryce" == Bryce McKinlay [EMAIL PROTECTED] writes:
If there is a code-formatting tool I don't see a reason why we
shouldn't convert. We should make sure that nobody has pending
changes to that class before converting them, though.
Bryce Great - I will experiment with the various code
On Dec 22, Bryce McKinlay wrote:
One issue I'd like to raise is that of coding style. A nice feature of libgcj is
that the code is written fairly consistently, where as classpath varies widely
between classes and packages that were written by different authors. Although
there is no official
6 matches
Mail list logo
