[bug #59775] "error: mark_as_constructed: invalid object" when constructor returns classdef array

Thomas <[email protected]>
Newsgroups gmane.comp.gnu.octave.bugs
Message-ID <[email protected]>
Please use the bug tracker to post updates to a bug report.  The mailing list is intended as a read-only notification stream.  Info posted to this mailing list address won't appear in the tracker database where it is most useful.

Follow-up Comment #5, bug #59775 (group octave):

I've attached a patch that should fix this issue. `cdef_object_array` didn't
have implementations of `mark_as_constructed`, while `cdef_object_scalar` did.
The patch passes `make check` on my machine.

Mark, thanks for your help in bringing this to my attention. I used your mre
classdefs in the test suite (with slight modifications to prevent overlap from
bug #68108 + coding conventions + renaming changes). Did you want to be
credited for your contributions in the patch? I will add it if you give me the
green light.

(file #58306)

    _______________________________________________________

Additional Item Attachment:

Name: bug59775.patch                 Size: 3.4KiB
    <https://file.savannah.gnu.org/file/bug59775.patch?file_id=58306>


    AGPL NOTICE

These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://savannah.gnu.org/source/savane-2a2ecc185bd672dd377a2efbb667431a4b30acc3.tar.gz


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59775>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc (application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCaam0tAAKCRCqLAuaBUf3
TidTAQCOAjPjax5p8LV22b7WlJ09Y1LkAfmmEJCzpQNgZbcCFAEA7op/w8f2obZ6
VihpshYPpp6dC8HrISrANhT99yMY+A8=
=W9sX
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.