@icedquinn its not just about halting or size. For example how would you define a functions visibility which would be external, internal, private or public... or other function modifiers like view or pure if the language doesnt have mechnisms for this. what about defining fallbacks with their extremely small gas price where you can only do real basic single operations, or how would you invoke EIPs like the proxy eip that use storage addresses that dont actually exist.

@icedquinn 1) the evm itself wont tell you if a symbol is available to call. You must know before hand and if your wrong it errors. This has issues for both visibilitya nd fallback calls.

2) visibility does exist at the assembly level. If you are writing a contract you must specify visibility which as it is enforced at runtime not compile time like most languages.

3) if you are writing a contract not sure how a host API would help, these things need to be encoded directly into your contract, its not like other languages where you can delegate calls to a standard library. Everything is compiled into your contract.

@icedquinn If the code needs a special virtual machine to run, and it isnt running the EVM, then it cant be used ont he ethereum blockchain in the first place as the miners are running EVM.. When you write a smart contract you arent the one who gets to dictate the computer that will run it, and therefore dont get to dictate the virtual machine used.

@icedquinn ok then you arent really talking about ethereum but rather a new cryptocurrency that is a fork of the eth codebase.. thats fine, but wasnt clear thats what you meant.