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
Thanks for your note. You’ve found a good little bug here. I’m not clear whether it’s a bug in cmd_ls() or whether the function definition is broken, but something is definitely wrong. Unfortulately, I’m away from my workbench this week so I can’t debug it first-hand. Can you please send the results of a “peep” at the eeprom after you create that situation?
-br
On Jun 15, 2015, at 1:04 PM, Timo A. Hummel [email protected] wrote:
When one accidentally declares an empty function, additional functions don't show up in the list.
function foo {}
saved
function bar { print "foo"; }
saved
ls
function foo {};
function print "foo"; {};
—
Reply to this email directly or view it on GitHub #46.
It doesn't seem to be the cmd_ls() function, because I'm not able to call the function "bar" in that example:
> function foo {}
saved
> function bar { print "foo"; }
saved
> bar()
-----^
unexpected number
> ls
function foo {};
function print "foo"; {};
> rm foo
> ls
function bar { print "foo"; };
> bar
foo
As soon as I remove the empty function foo, the call to bar works again.
When one accidentally declares an empty function, additional functions don't show up in the list.
The text was updated successfully, but these errors were encountered: