convert from adhoc exception

[coke]

The sample here copies a chunk of the lang_setup method from the main grammar.

"use v4" prints out the error message and dies.

"use v5" couldn't create the exception. I've tried to setup the core.c resolver here but am just cargo culting, this also dies.

[vrurg]

"use v5" couldn't create the exception. I've tried to setup the core.c resolver here but am just cargo culting, this also dies.

Same problem as I explained on IRC, perhaps. CORE setting isn't loaded yet. You'd need to load it first. Guess, just CORE.c is OK for the purpose.

[vrurg]

I just've noticed that @niner has similar approach to mine: when an error exception is about to be thrown matters of inefficiency are not that important.

[coke]

"use v5" couldn't create the exception. I've tried to setup the core.c resolver here but am just cargo culting, this also dies.

Same problem as I explained on IRC, perhaps. CORE setting isn't loaded yet. You'd need to load it first. Guess, just CORE.c is OK for the purpose.

Ok, tried harder to load the v6.c language before throwing the exception.

[vrurg]

Ok, tried harder to load the v6.c language before throwing the exception.

If it works this way, I'd like to see a less hacky implementation.

[coke]

If it works this way, I'd like to see a less hacky implementation.

Sorry, wasn't clear: it's still failing.

[coke]

ok, current version now does something reasonable with -e 'use v6' and -e 'use v5' but fails when running files.

[lizmat]

Hmm... I'm wondering: why don't we load v6.c (or whatever is the basic supported version) unconditionally? And have any use v6x statement figure out that 1. there have not been any other statements, and 2. load any subsequent setting if the version indicated is higher?

[vrurg]

why don't we load v6.c (or whatever is the basic supported version) unconditionally?

Considering that loaded core settings are cached anyway, it makes even more sense.