You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
list := Polyglot eval: 'ruby' string: '[]'.
copy := list copy
This throws an Error (Foreign object does not understand "copy"), because ForeignObject>>#copy calls ForeignObject>>#'_dispatch:arguments:ifFail:' with "copy" as member, which the ruby list does not have.
The text was updated successfully, but these errors were encountered:
Thanks for the report! What's the expected behavior? If Ruby lists don't implement copy, a debugger seems reasonable. Or would you want the object to behave like a Smalltalk object (actually performing a shallow copy)?
Well, since ForeignObject offers a copy and deepCopy method respectively, it would be optimal to receive adequate (shallow) copies or deep copies of these ForeignObjects.
If there is no way to copy/deepCopy those objects language independently and the methods are only meant as a short cut to invoking "copy" members, the debugger is fine. It then reduces to raising awareness that the programmer himself needs to worry about how to copy these objects (e.g. by finding the correct members).
This throws an Error (Foreign object does not understand "copy"), because
ForeignObject>>#copy
callsForeignObject>>#'_dispatch:arguments:ifFail:'
with "copy" as member, which the ruby list does not have.The text was updated successfully, but these errors were encountered: