[Oberon] FPGA - Pictures.Mod composition

[Jörg]

Wojtek

You are right: Oberon-2 offers type-bound procedures not immediately available in Oberon-07.
However, it should be possible to reach a comparable functionality in Oberon-07.
I will write the scheme one could use to reach that goal in a separate mail.

br
Jörg

Am 27.09.17, 02:24 schrieb "Oberon im Auftrag von Skulski, Wojciech" <oberon-bounces at lists.inf.ethz.ch im Auftrag von skulski at pas.rochester.edu>:

    In addition to data fields, there are also methods like Store and Read. These are polymorphic if the internal format can vary.
    
    Do not we need Oberon-2 for handling this in an elegant way? What do you think?
    
    Thanks,
    Wojtek
    ________________________________________
    From: Oberon [oberon-bounces at lists.inf.ethz.ch] on behalf of Jörg [joerg.straube at iaeth.ch]
    Sent: Tuesday, September 26, 2017 2:55 PM
    To: ETH Oberon and related systems
    Subject: Re: [Oberon] FPGA - Pictures.Mod composition
    
    indeed, we could. With your propsal Pictures are supersets of Bitmaps and hence type compatible (meaning PROCEDUREs accepting Bitmaps could accept Pictures as well, not the otherway around)
    With the existing separate type definitions, types are not compatible.
    
    Jörg
    
    > Am 26.09.2017 um 20:25 schrieb Tomas Kral <thomas.kral at email.cz>:
    >
    > Hi,
    >
    > Looking at these two structures, I am scratching my head, is a
    > picture `kind of' bitmap, or `makes use of' bitmap, as we repeat
    > fields: width, height, depth, and base, while only adding colour table?
    >
    > TYPE
    >  Bitmap* = POINTER TO BitmapDesc;
    >  BitmapDesc* = RECORD
    >    width*, height*, depth*: INTEGER;
    >    base*: INTEGER;
    >    size*: INTEGER
    >  END;
    >
    > TYPE
    > Picture* = POINTER TO PictureDesc;
    >    PictureDesc* = RECORD
    >      width*, height*, depth*: INTEGER;
    >      bitmap: Bitmaps.Bitmap;
    >      base: INTEGER;
    >      ct: ColorTable
    >    END;
    >
    > Should we not just extend it?
    >
    > TYPE
    > PictureDesc* = RECORD (Bitmaps)
    >     ct: ColorTable
    >   END;
    >
    > --
    > Tomas Kral <thomas.kral at email.cz>
    > --
    > Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
    > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.inf.ethz.ch_mailman_listinfo_oberon&d=DwIGaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=uUiA_zLpwaGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=lf3f95699TDTtIaSR9TteVkb8JSr0wJ4E7Ydf2SnaZ0&s=ZblJxe0ydVXW_id9bDw_jScQa_uGPuw-o6UfYxRwRzs&e=
    
    --
    Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
    https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.inf.ethz.ch_mailman_listinfo_oberon&d=DwIGaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=uUiA_zLpwaGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=lf3f95699TDTtIaSR9TteVkb8JSr0wJ4E7Ydf2SnaZ0&s=ZblJxe0ydVXW_id9bDw_jScQa_uGPuw-o6UfYxRwRzs&e=
    --
    Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
    https://lists.inf.ethz.ch/mailman/listinfo/oberon