Skip to content

Conversation

@edhay
Copy link

@edhay edhay commented Sep 8, 2025

Restriction on Package in Package() data structure is removed accommodating it to contain nested packages

See issue #29 for more details.

Restriction on Package in Package() data structure is removed accommodating
it to contain nested packages
Additional clarification added

See issue UEFI#29 for more details.
* a Package consisting entirely of Integer, String, or Reference objects
(and specifically not containing a nested Package).
* a Reference (but not referencing a Package which in turn contains nested Package references), or
* a Package (but not containing a reference to another Package).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"A reference to a Package" is not particularly well defined as far as I can say. If the name (or generally a namepath) of an object appears in the source code, which is regarded as a "reference" to that object, there are two cases. If it is possible to evaluate it, it will be evaluated and the return value (whatever it is) will be used where the name has appeared. If it cannot be evaluated, it will be held as a "reference object" (this happens if the target object is a device, for example). Objects that evaluate to Packages are in the first category, so they are evaluated in that case and the Package appears where the name has been used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants