[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Mailing-list archive.



Hi!

This is simply to inform you that I have added a link to the "text file"
mailing-list archive on the SableCC web page.

Have a nice day!

Etienne

From: "Steffen Seufert" <ba0279@bamberg.baynet.de>
To: <sablecc-list@sable.mcgill.ca>
Subject: sablecc and JDK 1.2 Beta 4
Date: Mon, 26 Oct 1998 22:21:58 +0100
Message-ID: <01be0126$a9c2e620$0101010a@steffen>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3
Status:   

Has anyone get sableCC work with JDK 1.2 Beta 4 ?

I get the same error (code of method longer than ...) reported in this
mailing-list.
Even with java options -noverify or -Xverify:none I get the same and nothing
works.
After inspecting the source of Parser.java I think the problem are the VERY
LONG static private array variables: actionTable, gotoTable, errors. The
reduction of the datatypes from int to short doesn't help ):
I think this is a bug of sableCC that is not visible in former JDKs because
they havn't this strong comptiblity tests for VM conformity.
The error reported of the virtual machine is reported as warning when
compiling Parser.java. After modifying the source of Parser.java(splitting
the arrays in own classes),
so that it works with JDK 1.2, I get sableCC run correctly but the
Minibasic-example will not compile
anyway ...

Has anyone a WORKING solution for this problems under JDK 1.2 Beta 4?

Bye,
Steffen

X-Sender: andrew@mail.intertrader.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 
Date: Tue, 27 Oct 1998 09:11:12 +0000
To: "Steffen Seufert" <ba0279@bamberg.baynet.de>, sablecc-list@sable.mcgill.ca
From: Andrew Cooke <andrew@intertrader.com>
Subject: Re: sablecc and JDK 1.2 Beta 4
In-Reply-To: <01be0126$a9c2e620$0101010a@steffen>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <E0zY53Y-0003ln-00@droid1.intertrader.com>
Status:   


	If the static data is making a method too long then it
	would make sense to place the data in a separate file and
	read it in during initialisation.

	This is the standard solution, as far as I remember (this
	topic has been discussed on the advanced-java mailing list
	in the past - you could try looking in the archives at
	http://www.xcf.berkeley.edu/lists.html)

	(apologies if the above URL has some funny HTML associated
	with it - I cut and pasted it from somewhere and my editor
	is showing it in bright pink, which seems odd... :-)

	Andrew

At 10:21 PM 10/26/98 +0100, you wrote:
>Has anyone get sableCC work with JDK 1.2 Beta 4 ?
>
>I get the same error (code of method longer than ...) reported in this
>mailing-list.
>Even with java options -noverify or -Xverify:none I get the same and nothing
>works.
>After inspecting the source of Parser.java I think the problem are the VERY
>LONG static private array variables: actionTable, gotoTable, errors. The
>reduction of the datatypes from int to short doesn't help ):
>I think this is a bug of sableCC that is not visible in former JDKs because
>they havn't this strong comptiblity tests for VM conformity.
>The error reported of the virtual machine is reported as warning when
>compiling Parser.java. After modifying the source of Parser.java(splitting
>the arrays in own classes),
>so that it works with JDK 1.2, I get sableCC run correctly but the
>Minibasic-example will not compile
>anyway ...
>
>Has anyone a WORKING solution for this problems under JDK 1.2 Beta 4?
>
>Bye,
>Steffen
>