international character string works as string argument but not in parser
Jaroslav Hajek
highegg at gmail.com
Thu Nov 13 00:50:05 CST 2008
On Tue, Nov 11, 2008 at 3:01 PM, Willem J. Atsma
<willem.atsma at victhom.com> wrote:
> Hi all,
>
> This may be specific to the installation I have: windows XP, version 3.0.1 (fr octave-forge)
>
> I get the following error:
>
>
> --------------------------------------------------------------------------
> octave:40>data_index.Québec
> error: invalid character `é' (ASCII 233) near line 40, column 26
> parse error:
>
>>>> data_index.Québec
> ^
> --------------------------------------------------------------------------
>
> When I use the field name like a list index it works:
>
> --------------------------------------------------------------------------
> octave:41>data_index.('Québec')
> --------------------------------------------------------------------------
>
> Assuming that the string is handled elsewhere in the code depending on how it is passed, I guess
> the parser does not support characters outside the 0-127 range?
>
> cheers,
>
> Willem
I thought structure field names were intended to be regular Octave
variable names.
You only can create a Québec field because the interpreter doesn't
check for it.
If field names are not variable names, some functions may have
problems, like save -struct, or accessing fields using eval.
--
RNDr. Jaroslav Hajek
computing expert
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz
More information about the Bug-octave
mailing list