Article View: comp.lang.modula2
Article #2401Re: JPI Compiler bug?
From: Tim Channon
Date: Thu, 21 Jan 1993 00:05
Date: Thu, 21 Jan 1993 00:05
24 lines
1267 bytes
1267 bytes
> Same here. I imported a my own ALLOCATE but NEW did not use it.
> May be it is a bug after all?
Well, I am not sure what I did, you got a different effect so over to tech
support... what is the correct usage?
BTW V3.1 is still working fine. The only noticable change is the code
generation leading to a small speed gain. On examining some code I was
surprised at the efficiency of the thing, handcoded assembler wouldn't have
gained much. Well done Clarion.
There is an oddity with VID (which hasn't crashed so far, it wasn't common but
it did occasionally) involves incorrect breakpoint handling, for example:
IF x THEN
a y;
b ELSE
A breakpoint at (a) will not do anything, so it must be put at (b)!
TC.
E-mail: tchannon@black.demon.co.uk or tchannon@cix.compulink.co.uk
Technical Details
Message-ID:
<727599924snx@black.demon.co.uk>Path:
arc1-ca.pugleaf.net!sparky!uunet!pipex!demon!black.demon.co.uk!tchannonShow Full Headers
Complete Article Headers
Newsgroups: comp.lang.modula2 From: tchannon@black.demon.co.uk (Tim Channon) Path: arc1-ca.pugleaf.net!sparky!uunet!pipex!demon!black.demon.co.uk!tchannon Subject: Re: JPI Compiler bug? Reply-To: tchannon@black.demon.co.uk Distribution: world X-Mailer: cppnews $Revision: 1.20 $ Organization: null Lines: 23 Date: Thu, 21 Jan 1993 00:05:24 +0000 Message-ID: <727599924snx@black.demon.co.uk> Sender: usenet@demon.co.uk