Inconsistent behavior with custom assignment operators between interactive and script

[iolanguage]

Inconsistent behavior with custom assignment operators between interactive and script

[stevedekorte]

This is because the script is parsed before it is executed (so it doesn't see the new operator entry while parsing).

[coiscir]

So, this is by design and I'm SOL?

[stevedekorte]

How could it be designed any differently? Would you parse and eval each line separately? What if an line eval attempted to look at the message tree - it would not be able to see the rest of it and this would also lead to a SOL situation.

[stevedekorte]

You can avoid the problem by simply putting the:

OperatorTable addAssignOperator("=>", "setKey")

bit in a separate script file.

[coiscir]

To clarify, my comment of "by design" was in regard to IO having inconsistent behavior depending on the environment and/or mode of execution.

I didn't actually intend on questioning "parse before execute" -- language design and implementation isn't my realm to question. But, outside this realm, your original response was rather useless. It gave me some additional understanding of the VM, that I appreciate, but it didn't resolve the issue.

From an admittedly naive understanding, it is at least odd that a new assignment operator isn't actually known until execution when the parser is what seems to need it. So, perhaps addAssignOperator could be rethought to be a parsable message rather than an executable message? I don't know...

Nevertheless, thank you for the suggestion. However, placing it in a separate file doesn't seem to make any difference. I've tried placing it in an addon script and importing, as well as just trying to execute it with doFile. Am I missing a 3rd option?

[stevedekorte]

If you send me your email address, I can send you a zip that shows it working.

[stevedekorte]

Also, here's the code if you don't mind creating the files yourself:

FILE: map.io
map(foo => 2, bar => 3)

FILE: op.io
OperatorTable addAssignOperator("=>", "setKey")

map := method(
call message arguments foreach(arg, writeln(arg))
)

FILE: runme.io
doFile("op.io")
doFile("map.io")

[coiscir]

Ah. Didn't think to run everything through doFile.

Though, that did lead me to find Message fromString, which works just as well with a little less overhead in the setup: ;)

OperatorTable addAssignOperator("=>", "setKey")

map := method(
  call message arguments foreach(arg,
    writeln(Message fromString(arg asString))
  )
)

map(foo => 2, bar => 3)