#433 CYCLIC support for ALPHIC DATIONs

[Rainer Müller]

The runtime system complains currently that there is no support for CYCLIC in ALPHIC DATIONs..

Analysis:

The attribute CYCLIC may be used in DATIONs with a fixed size. It defines a behavior that the access operations loops at the end of the dimensions automatically the the beginning. This is useful for e.g. logging with a fixed number of messages on a limited storage device like an I2C-eeprom. ALPHIC DATION are commonly used with STREAM, which allows the longer lines than the dation limits.
In ALPHIC DATIONS with NOSTREAM the cyclic attribute makes sense.

Decision

1) The language report should be precised that ALPHIC DATIONs with CYCLIC may not be used together with STREAM.
2) The compiler should emit an error message if CYCLIC is used on ALPHIC STREAM dations (CYCLIC may not used together with STREAM dation)
3) The compiler should emit an error message if CYCLIC is used in ALPHIC NOSTREAM dations (CYCLIC not supported for NOSTREAM dation)
4) The warning in the runtime system should become removed

[Rainer Müller]

the decision items 2+3 may be combined towards OpenPEARL supports no CYCLIC on ALPHIC DATIONS

[Rainer Müller]

Userdations of type BASIC are used with TAKE and SEND.
For these DATIONS the AccessAttribute and Typology makes no sense.

The compiler should emit a warning like Typology and AccessAttributes make no sense for dation of type BASIC

[Anonymous]

remark: ALPHIC dations with

• STREAM need an end-of-record marker like '\n'
• NOSTREAM have no end-of-record marker, but the record becomes filled with spaces

ALPHIC DATIONs with fixed record size are very unfamiliar since the end of life of punge cards

Thats the reason why OpenPEARL suppords no CYCLIC on ALPHIC dations