Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mcvax!enea!tut!santra!clinet!msa
From: msa@clinet.FI (Markku Savela)
Newsgroups: comp.lang.pascal
Subject: Odd behaviour of Microsoft Pascal 3.31
Message-ID: <473@clinet.FI>
Date: Wed, 5-Aug-87 18:40:52 EDT
Article-I.D.: clinet.473
Posted: Wed Aug  5 18:40:52 1987
Date-Received: Sun, 9-Aug-87 13:31:56 EDT
Reply-To: msa@clinet.UUCP (Markku Savela)
Distribution: world
Organization: City Lines Oy, Helsinki, Finland
Lines: 33


	I have been using Microsoft Pascal (version 3.31) for a program
	which consists of several (25-40) modules. I'm using the
	INTERFACE/IMPLEMENTATION sections. The final code takes about
	200-300Kb.

	Occasionally I run into very disturbing behaviour in the compiler.
	After some minor changes into modules, compiler suddenly decides,
	that one or another module won't compile. Some final error messages
	are:
		"Error: Compiler Invalid Pointer Range"
		(and usually followed by "Null Pointer Assignment")
	or
		"Error: Compile Pointer To Disposed Var"

	The above are often preceded by several reports of non-existent
	syntax errors.

	The funny thing is that I may get the compilation to succeed
	without errors using some of the following tricks:

	- move all files to another PC/AT and compile them there
	- ask pascal listing file (xxx.LST)
	- add dummy "CONST"-declarations to the module (e.g. dummy1 = 123;)
	  (this is the most sure way, but it takes time to hit the right
	  combination -- does anyone have an algorithm for the combination?)

	Is this a feature of my special brand of PC/AT "clone" (NOKIA ASC,
	MS-DOS 3.1, Phoenix Bios) or is Microsoft Pascal broken in some way?
--------------
Markku Savela
Nokia Information Systems
P.O.BOX 780 SF-00101 HELSINKI, FINLAND         uucp: msa@clinet.UUCP