Typo in __get_symbol_table__ how can this work?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Typo in __get_symbol_table__ how can this work?

Andreas Weber-6
While looking though load/save I stumbled over this in

./libinterp/corefcn/load-save.cc 148

  octave::symbol_table& symtab
    = octave::__get_symbol_table__ ("install_loaded_varaible");

  octave::symbol_scope *scope
    = symtab.require_current_scope ("install_loaded_variable");

Please note the typo "varaible" in the first part. How can this work
with this typo? Is there some "fuzzy search" for symbols?

Thanks, Andy

Reply | Threaded
Open this post in threaded view
|

Re: Typo in __get_symbol_table__ how can this work?

John W. Eaton
Administrator
On 11/18/2017 04:27 AM, Andreas Weber wrote:

> While looking though load/save I stumbled over this in
>
> ./libinterp/corefcn/load-save.cc 148
>
>    octave::symbol_table& symtab
>      = octave::__get_symbol_table__ ("install_loaded_varaible");
>
>    octave::symbol_scope *scope
>      = symtab.require_current_scope ("install_loaded_variable");
>
> Please note the typo "varaible" in the first part. How can this work
> with this typo? Is there some "fuzzy search" for symbols?

That string is just used for error messages, not for looking up
anything.  I'll fix it, but it shouldn't affect whether finding the
current symbol scope will succeed (or not).

jwe



Reply | Threaded
Open this post in threaded view
|

Re: Typo in __get_symbol_table__ how can this work?

Andreas Weber-6
Am 18.11.2017 um 19:04 schrieb John W. Eaton:
> That string is just used for error messages, not for looking up
> anything.  I'll fix it, but it shouldn't affect whether finding the
> current symbol scope will succeed (or not).

Ah okay, thank you for the explanation.
-- Andy