Path: utzoo!utgpu!attcan!uunet!pdn!alan
From: alan@pdn.nm.paradyne.com (Alan Lovejoy)
Newsgroups: comp.lang.modula2
Subject: Re: Portable Oberon compiler
Keywords: Oberon portable compiler ETH Wirth
Message-ID: <5533@pdn.nm.paradyne.com>
Date: 7 Feb 89 15:38:27 GMT
References: <INFO-M2%89012710550179@DB0TUI11< <772@jungfrau.UUCP>
Reply-To: alan@pdn.nm.paradyne.com (0000-Alan Lovejoy)
Organization: Paradyne Corporation, Largo, Florida
Lines: 27

In article <772@jungfrau.UUCP< marvin@jungfrau.UUCP writes:
<introduces serious problems for the compiler. If the public projection
<(i.e. the declaration in the definition part) has a size smaller than
<the actual declaration in the implementation part, the compiler looks at
<the symbol file, and __patches__ it in order to have the size of the
<record fixed ! To avoid this, the portable Oberon compiler will have a
<slight modification to the language: you have to add a compiler hint in
<the definition part. It will then look like this (referring to the
<example in the paper): 
<
<TYPE	Viewer = RECORD
<		   width, height : INTEGER;
<		   [8]
<		 END;
<
<The number indicates the size of the record as it will be in the
<implementation part. It's not quite clear to me if it is possible to
<give any size, even if it is bigger then the actual size in the
<implementation part. I hope It will be clear in their report.

Why couldn't this be handled by the linker instead of the compiler?

-- 
Alan Lovejoy; alan@pdn; 813-530-2211; ATT-Paradyne: 8550 Ulmerton, Largo, FL.
Disclaimer: I do not speak for ATT-Paradyne.  They do not speak for me. 
___________ This Month's Slogan: Reach out and BUY someone (tm). ___________
Motto: If nanomachines will be able to reconstruct you, YOU AREN'T DEAD YET.