[Oberon] NEW on POINTER TO RECORD always results in NIL (RISC Oberon) - bug?

Michael Schierl schierlm at gmx.de
Thu May 22 19:51:36 CEST 2014

Am 22.05.2014 10:14, schrieb Paul Reed:
> Dear Mr. Schierl,
>> [I tried to post this message about a month ago and never received any
>> feedback - seems that it never got approved. Now that I'm subscribed to
>> the list, I'll try again :)]
> Perhaps you can't post until you are subscribed, as an anti-spam measure.

Perhaps somebody[tm] can change the notice on the listinfo page that
tells that without being subscribed you have to wait until an
administrator approves it (which I am fine with btw, since it was not
urgent at all :D).

> Thanks very much for reporting this NEW() behaviour, we are currently
> looking into it.  Certainly at one stage I remember, local record types
> were disallowed altogether.  Would that approach work for you?

I would certainly prefer it to the current situation of silently
failing. And as most of the things I try to run in RISCOberon are from
some other Oberon compiler and need some amount of porting anyway,
changing the pointer types should not make it too much harder :)



More information about the Oberon mailing list