|
From: | Guillaume |
Subject: | [Octave-bug-tracker] [bug #61537] mxAddField too strict on field validation |
Date: | Wed, 24 Nov 2021 07:35:26 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 |
Follow-up Comment #2, bug #61537 (project octave): Matlab also allows any character when using the MEX interface. The restriction only occurs when adding a new field from M code (but accessing any field still work with the .('') syntax). >> mxstruct field number = 1 ans = struct with fields: _a: [] _b: [] >> ans.('_a') ans = [] >> a.('_a') = [] Invalid field name: '_a'. I would therefore remove any restriction on field names in Octave. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?61537> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |