Continuation of a topic

[helicoptur]

Continuation of this topic because it's closed:
Uhh...


(Bignums set to on for both images)

@bh

I don't think it's doing a type check; it's the Javascript SPLIT method throwing an error.

The problem isn't within the split block, the problem is that the return value isn't a text OR a number. It's some weird non-native object created by the bignums library that looks like a text.

[snapenilk]

@helicoptur

because it's closed

I'm sure there is a good reason Brian closed it, so I don't think it is a good idea to make a new thread about it.

[programmer_user]

@snapenilk

I'm sure there is a good reason Brian closed it

@bh

I don't think it's doing a type check; it's the Javascript SPLIT method throwing an error. The trouble with having bignums as a library rather than built into Snap*!* is that it's fragile; there are probably many cases of user errors (which this is) that give rise to unexpected error message texts. It's bad enough having to override the arithmetic functions without also having to override text functions!

[helicoptur]

It's not undefined, it's just

@helicoptur

some weird non-native object created by the bignums library that looks like a text.

By undefined, it means it's not an object recognizable by Snap!.

[snapenilk]

It looks like a text because Snap! invokes its toString() method, which it does for these "undefined" or unrecognized types.

[helicoptur]

I know how that works.