Oh and a /debug to debug a program!
That is kind of what /run is for.
Done.
Full tracebacks:
# Python
>>> rbgviwegvune = 'sigufisdhf' / 'sidfb'
Traceback (most recent call last):
File "<pyshell#1>", line 1, in <module>
rbgviwegvune = 'sigufisdhf' / 'sidfb'
TypeError: unsupported operand type(s) for /: 'str' and 'str'
Did you not see the update?
/run:
Error in syntax at line 1! No possible commands found for 'say [moew]'
/debug:
Error in syntax at line 1! No possible commands found for 'say [moew]'
+ some extended info about the error
The only error you can get in my software right now is if no such command exists.
We're talking about when you've got things like, say, subtracting nonnumbers erroring.
That'l come when those types of blocks are added.
Anyways I stayed up late making this. It's kind of a good start.
# Python
>>> 'str' - (lambda: 2 * 4)
Traceback (most recent call last):
File "<pyshell#0>", line 1, in <module>
'str' - (lambda: 2 * 4)
TypeError: unsupported operand type(s) for -: 'str' and 'function'
I think I know what your trying to say. Your saying, that Snap! wont error when it gets text instead of a number in math. I plan to detect that NaN and convert it into an error.
I can also use the built-in operation detecting in my custom block that runs the script.
0/0 = NaN, shouldn't error.
should error.
I said:
Oh and how should it have grey rings syntactically?
{ and }
And the variadic input? And the block input to the ring?
I don't remember what that is.
({ and })
The right arrow. 