Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign up[[ Bug 20931 ]] Bridge values in LCB assign-array and assign-list ops #6310
Conversation
This patch fixes a bug where the behavior of code built using the
[ ... ] and { ... } syntax in LCB is different from that when using
explicit code.
A new method 'Bridge' has been added to the VM's execute context.
This method performs a 'convert to optional any' on the input value
resulting in bridgeable foreign values being imported, and all other
values being retained.
This method is now called on the input values in the assign-list
and assign-array opcodes meaning that foreign values being built
into lists will bridge.
Additionally, an extra compiler check has been added to variadic
arguments (i.e. arguments to the variadic portion of a C variadic
handler). This check restricts such arguments to being variable
identifiers where the variable has an explicit type declaration.
This is necessary to ensure that code explicitly states the type
which is being passed in variadic positions as there is no other
means for the compiler or the VM to know what the type should be.
|
One possible concern (that I'm sure you've considered) is that this change may make it harder to manage collections of foreign values without paying the cost of bridging. |
|
@peter-b : Hehe - indeed! The idea here is that the VM has three kinds of slot - temporary which hold values as they are, typed which convert a value on assignment and untyped which bridge but do not convert. As lcb doesn't yet have typed lists, we take the element of type of lists as they are now as 'untyped'. In the future lists of foreign values will be managed by being able to specify list of . I.e. Foreign values only stay foreign if bring places in temporary or types slots. |
|
All apparently explicitly typed params to variadic functions now seem to be failing, eg:
|
tests/lcb/vm/assign-ops.lcb
Outdated
| put false into tVar | ||
|
|
||
| variable tValue as Pointer | ||
| put MCProperListFetchElementAtIndex([tVar], 1) into tValue |
livecodeian
May 31, 2018
Contributor
The index to MCProperListFetchElementAtIndex should be 0 no?
The index to MCProperListFetchElementAtIndex should be 0 no?
livecodeali
Jun 1, 2018
Member
Yes! Thanks, fixed.
Yes! Thanks, fixed.
|
@livecode-vulcan review ok 615a87b |
|
|
livecode-vulcan
added a commit
that referenced
this pull request
Jun 6, 2018
[[ Bug 20931 ]] Bridge values in LCB assign-array and assign-list ops
This patch fixes a bug where the behavior of code built using the
[ ... ] and { ... } syntax in LCB is different from that when using
explicit code.
A new method 'Bridge' has been added to the VM's execute context.
This method performs a 'convert to optional any' on the input value
resulting in bridgeable foreign values being imported, and all other
values being retained.
This method is now called on the input values in the assign-list
and assign-array opcodes meaning that foreign values being built
into lists will bridge.
Additionally, an extra compiler check has been added to variadic
arguments (i.e. arguments to the variadic portion of a C variadic
handler). This check restricts such arguments to being variable
identifiers where the variable has an explicit type declaration.
This is necessary to ensure that code explicitly states the type
which is being passed in variadic positions as there is no other
means for the compiler or the VM to know what the type should be.
|
07474c7
into
livecode:develop-9.0
4 checks passed
4 checks passed
continuous-integration/vulcan/cla
Contributor Agreement signed by @runrevmark
continuous-integration/vulcan/pr
The Vulcan build succeeded on 13 builders
continuous-integration/vulcan/review
Approved by reviewer @livecodeian
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
This patch fixes a bug where the behavior of code built using the
[ ... ] and { ... } syntax in LCB is different from that when using
explicit code.
A new method 'Bridge' has been added to the VM's execute context.
This method performs a 'convert to optional any' on the input value
resulting in bridgeable foreign values being imported, and all other
values being retained.
This method is now called on the input values in the assign-list
and assign-array opcodes meaning that foreign values being built
into lists will bridge.
Additionally, an extra compiler check has been added to variadic
arguments (i.e. arguments to the variadic portion of a C variadic
handler). This check restricts such arguments to being variable
identifiers where the variable has an explicit type declaration.
This is necessary to ensure that code explicitly states the type
which is being passed in variadic positions as there is no other
means for the compiler or the VM to know what the type should be.