Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!gatech!ncar!tank!oddjob!mimsy!aplcen!jhunix!ins_adjb
From: ins_adjb@jhunix.HCF.JHU.EDU (Daniel Jay Barrett)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Manx bug
Message-ID: <7128@jhunix.HCF.JHU.EDU>
Date: 1 Oct 88 13:35:12 GMT
References: <220@snll-arpagw.UUCP>
Reply-To: ins_adjb@jhunix.UUCP (Daniel Jay Barrett)
Organization: Johns Hopkins Univ. Computing Ctr.
Lines: 25

In article <220@snll-arpagw.UUCP> paolucci@snll-arpagw.UUCP (Sam Paolucci) writes:
>I was compiling a sizable code and I got the following error from the
>assembler (it got through the compiler fine :-)):
>
>	"Line 802 #Pc relative out of range, -130."

	I found this bug almost immediately after V3.6 was released.
I took a few hours, narrowed it down to a minimal code example, and
sent it to Manx.  About a month later, I received a nice letter that
the bug had been fixed.
	I don't know if this means that we will see a bugfix released,
though.  Maybe not until the next version?  :-(

	The bug is REALLY weird.  My minimal code example was basically
a large switch statement.  If you changed ONE CHARACTER CONSTANT from
'x' to 'y', the program compiled and assembled fine.  Otherwise, 
assembler error.
	My friend theorized that somehow the 'x' was being interpreted
as part of a hexadecimal number...???
	Anyway, if anyone wants so see my program, let me know.

-- 
Dan Barrett	ins_adjb@jhunix.UUCP			UUCP
		barrett@cs.jhu.edu	(128.220.13.4)	ARPA
Dept. of Computer Science, Johns Hopkins University, Baltimore, MD  21218