Am 23.12.2016 um 23:30 schrieb Bernd Oppolzer:
>
> Hello FPC list,
>
> I would like to inform you, that I ported an improved version
> of the Stanford Pascal compiler (a descendant of the Wirth P4
> compiler) to Windows, OS/2 and Linux.
>
Glad to hear that FPC is not the only oss/free pascal
On 26/12/16 19:00, Bernd Oppolzer wrote:
A thought without its being a direct comment on any part of what you've
written. Programming texts from Wirth onwards tended to muddle pointers
and dynamic memory allocation together, so in effect assumed that
pointers would /only/ come out of the heap
Am 26.12.2016 um 10:31 schrieb Alexander Stohr:
Am 2016-12-25 um 21:42 schrieb Bernd Oppolzer:
Thank you for your feedback.
Thank you for your kind answers.
You're welcome; I'm happy to meet someone who is interested in my work :-)
BTW, I had to remove some sort of self check from the
On 25/12/16 10:00, Alexander Stohr wrote:
Am 2016-12-24 um 15:20 schrieb Bernd Oppolzer:
The first answer for such operators often is: use the right container
for the value you are in need and avoid all those operators.
Bear in mind that this is very old code that Bernd is maintaining, and
Am 2016-12-24 um 15:20 schrieb Bernd Oppolzer:
Am 24.12.2016 um 14:21 schrieb Mark Morgan Lloyd:
On 24/12/16 12:30, Bernd Oppolzer wrote:
Regarding ^:
"my" compiler supports different representations for the pointer
symbol,
and for other
critical symbols, too:
^ @ -> for the pointer
Am 24.12.2016 um 12:50 schrieb Mark Morgan Lloyd:
On 24/12/16 11:30, Bernd Oppolzer wrote:
chars in
the (character) P-Code file had to be converted to character
constants; all
places where character A - for example - was represented as numeric 193
(which is EBCDIC 'A') had to be found and
On 24/12/16 11:30, Bernd Oppolzer wrote:
Hello Mark,
on several occasions, I looked what FPC does, when I extended the
Stanford compiler, for example when I added support for direct write
of scalars.
At one time I recall that I decided explicitly to take another direction;
that was when I
