Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sysflag [1] for arrays other than open array value parameter #1

Closed
Oleg-N-Cher opened this issue May 16, 2016 · 1 comment
Closed
Labels

Comments

@Oleg-N-Cher
Copy link
Owner

Currently, an array type declaration of the form

ARRAY[1] OF CHAR

is defined only for open array value parameters and means that the array is not
copied. Specifying the array sysflag, however, is allowed at other places as
well, where it is silently ignored by ofront.
While only the open array value parameter usage is defined in the
OfronUserGuide, it is a potential source for an error or misunderstanding.

Either the other usages should be marked by ofront as an error or they should
be supported. A possible semantics would be similar to RECORD[1], which means
untracked by the Garbage Collector. For this semantics a possible usage would
be in Module Args, where the argument vector argv is an untracked ARRAY OF
POINTER TO ARRAY OF CHAR.

Original issue reported on code.google.com by Josef Templ on 11 Oct 2013 at 11:35
jtempl/ofront#1

@Oleg-N-Cher
Copy link
Owner Author

The system flag [1] for RECORDs does nothing now. Desirable it will allows to define the RECORDs without additional type checks - no genering __TDESC, __INITYP and TypeIdent__typ definitions.

Oleg-N-Cher added a commit that referenced this issue May 19, 2018
…checks - no genering __TDESC, __INITYP and TypeIdent__typ definitions.
Oleg-N-Cher added a commit that referenced this issue May 22, 2018
Oleg-N-Cher added a commit that referenced this issue Sep 12, 2019
…checks - no genering __TDESC, __INITYP and TypeIdent__typ definitions.
Oleg-N-Cher added a commit that referenced this issue Sep 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant