[Oberon] undefined record field when compiling in NO.

[Bob Walkden]

You have to export individually the fields of ConfigInput.Frame if you want to use them in other modules, so it should be x*, y: INTEGER;

B

> On 3 Jan 2014, at 08:21, <peasthope at shaw.ca> wrote:
> 
> In the alpha release of NO, the compiler applied to 
> 
> MODULE Test;
> IMPORT  ConfigInput;
> PROCEDURE Frame(F: ConfigInput.Frame);
> VAR x: INTEGER;
> BEGIN
>    x := F.x
> END Frame;
> BEGIN END Test.
> 
> reports
> compiling Test
>        pos    105  err  83    undefined record field
> .
> This is in ConfigInput.
> TYPE
>    Frame* = POINTER TO RECORD (Display.Frame)
>        keys: SET;
>        x, y: INTEGER;
>        text: Texts.Text
>    END;
> 
> So F.x in Test should be legitimate.
> Can anyone explain why the compiler complained?
> 
> Thanks,             ... Peter E.
> 
> 
> 
> 
> -- 
> 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
> Tel +13606390202  Bcc: peasthope at shaw.ca  http://carnot.yi.org/  
> "http://members.shaw.ca/peasthope/index.html#Itinerary "
> 
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon