Re: auto-formatting: no more jalopy
Tom Tromey [EMAIL PROTECTED] writes: Brian == Brian Jones [EMAIL PROTECTED] writes: Brian Bug: Printer Java: GNU brace style does not indent beyond braces Brian http://sourceforge.net/tracker/index.php?func=detailaid=716393group_id=45216atid=442212 I tried adding gnu-style indent to jalopy today. Unfortunately the result dies while trying to parse our javadoc. So, I'm giving up. I can send my hack if somebody wants it. The real GNU.xml style file is attached to the above PR. Go ahead and send my way, I'm starting to play with it too. Brian -- Brian Jones [EMAIL PROTECTED] ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: auto-formatting: no more jalopy
Brian == Brian Jones [EMAIL PROTECTED] writes: Brian Bug: Printer Java: GNU brace style does not indent beyond braces Brian http://sourceforge.net/tracker/index.php?func=detailaid=716393group_id=45216atid=442212 I tried adding gnu-style indent to jalopy today. Unfortunately the result dies while trying to parse our javadoc. So, I'm giving up. I can send my hack if somebody wants it. The real GNU.xml style file is attached to the above PR. Tom ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: auto-formatting: no more jalopy
Etienne == Etienne Gagnon [EMAIL PROTECTED] writes: Etienne Jalopy seems to fill the needs, on the technical side. We could take Etienne the latest Free snapshot available before it becomes proprietary to Etienne indent the code. Actually, there are a few problems with it. We'd like a blank line before `package' (we can't use header insertion due to copyright years), and jalopy doesn't support that. Also I think it doesn't handle indentation of method bodies the way we would like. Or was it `if' statement bodies? I submitted a couple jalopy bug reports a few months ago... Of course we could just hack these features and have a classpath only fork of jalopy. I've attached the GNU.jalopy config file I made, way back. It should come pretty close to our style. But not close enough to use :-( Tom GNU.jalopy Description: GNU.jalopy ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: auto-formatting: no more jalopy
Tom Tromey [EMAIL PROTECTED] writes: Actually, there are a few problems with it. Bug: Printer Java: GNU brace style does not indent beyond braces http://sourceforge.net/tracker/index.php?func=detailaid=716393group_id=45216atid=442212 I couldn't find any more. Of course we could just hack these features and have a classpath only fork of jalopy. Maybe. -- Brian Jones [EMAIL PROTECTED] ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: auto-formatting: no more jalopy
OK. I will try to get some of my compiler course students to make a term project, out of it. It should be fun for them, and they will get a wide community of testers. ;-) Etienne Tom Tromey wrote: Actually, there are a few problems with it. We'd like a blank line before `package' (we can't use header insertion due to copyright years), and jalopy doesn't support that. Also I think it doesn't handle indentation of method bodies the way we would like. Or was it `if' statement bodies? I submitted a couple jalopy bug reports a few months ago... Of course we could just hack these features and have a classpath only fork of jalopy. I've attached the GNU.jalopy config file I made, way back. It should come pretty close to our style. But not close enough to use :-( Tom -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: auto-formatting: no more jalopy
Tom Tromey [EMAIL PROTECTED] writes: I was just looking at the jalopy lists for any sign of life, and I found out that jalopy is going proprietary. So unless someone starts a free fork, I'm afraid we're left once again without a plausible way of getting an auto-formatter. Perhaps Etienne will write his now :-) Link to the bad news: https://sourceforge.net/mailarchive/forum.php?thread_id=2526002forum_id=8775 Looking at CVS now. I don't care much about most of the editor plugins. Brian -- Brian Jones [EMAIL PROTECTED] ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: auto-formatting: no more jalopy
Etienne Gagnon [EMAIL PROTECTED] writes: Hi Tom Brian, Jalopy seems to fill the needs, on the technical side. We could take the latest Free snapshot available before it becomes proprietary to indent the code. The only worry I have is that it is not obvious to me if all the licenses of the various parts of jalopy are compatible. Have a look at: http://jalopy.sourceforge.net/dependencies.html The page incorrectly lists getopt and aelfred as GPL, instead getopt is released under the LGPL and aelfred under a license similar to BSD. This is a link to a late May message about the commercial release. August was a planned FCS but it's likely late. Nothing has been updated in available CVS since last November it appears to me. http://sourceforge.net/mailarchive/forum.php?thread_id=2463425forum_id=8775 Brian -- Brian Jones [EMAIL PROTECTED] ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: auto-formatting: no more jalopy
Hi Brian all, So, given that there seem to be no licensing problem, we should definitely consider using Jalopy to indent the Classpath Java source code, and GNU indent to indent the C source code. I do not know if any free jvm is currently able to run Jalopy, but I am sure they will quite soon. [This would be a good benchmark for SableVM. :-)] On an unrelated note: David Belanger has got SableVM to work with Classpath 0.06. His working code is in SableVM's Subversion repository (http://subversion.tigris.org/). If anybody is interested to play with it, do not hesitate to ask questions on the sablevm-developer mainling-list. Etienne Brian Jones wrote: Etienne Gagnon [EMAIL PROTECTED] writes: The only worry I have is that it is not obvious to me if all the licenses of the various parts of jalopy are compatible. Have a look at: http://jalopy.sourceforge.net/dependencies.html The page incorrectly lists getopt and aelfred as GPL, instead getopt is released under the LGPL and aelfred under a license similar to BSD. This is a link to a late May message about the commercial release. August was a planned FCS but it's likely late. Nothing has been updated in available CVS since last November it appears to me. http://sourceforge.net/mailarchive/forum.php?thread_id=2463425forum_id=8775 Brian -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
auto-formatting: no more jalopy
I was just looking at the jalopy lists for any sign of life, and I found out that jalopy is going proprietary. So unless someone starts a free fork, I'm afraid we're left once again without a plausible way of getting an auto-formatter. Perhaps Etienne will write his now :-) Link to the bad news: https://sourceforge.net/mailarchive/forum.php?thread_id=2526002forum_id=8775 Tom ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
