-
Notifications
You must be signed in to change notification settings - Fork 44
Limit arrays #3828
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
base: master
Are you sure you want to change the base?
Limit arrays #3828
Changes from all commits
6a0b19e
94e7ea3
02fc331
54dd6b4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -833,7 +833,7 @@ \section{Built-in Functions}\label{built-in-functions} | |
|
|
||
| \section{Record Constructor Functions}\label{record-constructor-functions} | ||
|
|
||
| Whenever a record is defined, a record constructor function with the same name and in the same scope as the record class is implicitly defined according to the following rules: | ||
| Whenever a scalar record is defined, a record constructor function with the same name and in the same scope as the record class is implicitly defined according to the following rules: | ||
|
|
||
| % Warning: 'partial flatteing' doesn't seem to be defined. See 'partial instantitation'. | ||
| The declaration of the record is partially flattened including inheritance, modifications, redeclarations, and expansion of all names referring to declarations outside of the scope of the record to their fully qualified names. | ||
|
|
@@ -856,6 +856,7 @@ \section{Record Constructor Functions}\label{record-constructor-functions} | |
| In the modification, all input parameters are used to set the corresponding record variables. | ||
|
|
||
| A record constructor can only be called if the referenced record class is found in the global scope, and thus cannot be modified. | ||
| The record constructor can be used in vectorized form according to \cref{scalar-functions-applied-to-array-arguments}. | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We need to address the record constructor of operator record. Since nothing is said of the conflict it could create.
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. An operator record shouldn't have an automatically generated record constructor, as that would cause conflicts with the defined operator record constructors, so their shouldn't be any conflict. |
||
|
|
||
| \begin{nonnormative} | ||
| This allows constructing an instance of a record, with an optional modification, at all places where a function call is allowed. | ||
|
|
@@ -981,6 +982,8 @@ \section{Record Constructor Functions}\label{record-constructor-functions} | |
| Demo.Record2(1, 2, 2, 3, 1, 2, 5, 5, {1, 2}, {1, 2, 3}); | ||
| parameter Demo.Record2 r3 = | ||
| Demo.Record2(c2 = 2, n2 = 1, r1 = 1, r4 = 4, r6 = 1 : 5, r7 = {1}); | ||
| parameter Demo.Record2 r4[2] = | ||
| Demo.Record2(c2 = 2, n2 = {1, 2}, r1 = 1, r4 = {4, 5}, r6 = 1 : 5, r7 = {1}); | ||
| \end{lstlisting} | ||
|
|
||
| The above example is only used to show the different variants appearing with prefixes, but it is not very meaningful, because it is simpler to just use a direct modifier. | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.