IMHO a better test would be write it ASAP get the language out , then see how hard it is to re-factor when you self host. I bet that will change the whole way its structured and force language changes to make it easier.
Sorry to be blunt but It smacks of perfectionism. None of the cases are particularly strong , "*ad hoc* parse rules and/or parse ambiguities." are common in nearly all languages - with good reason they have taken short cuts to get something out the door. Javascript and Linux are a great examples -our world is filled with second rate products because the better ones never get finished. The whole purpose of modern languages / techniques is to be able to re-factor and improve it ( which is the main reason the parser and tokeniser are split - while its worse / less efficient than a combined custom implementation it does allow better / simpler code ). I kind of like Test Driven Development for this - do the smallest amount to satisfy the test , since we are always lazy writing tests it allows less over engineering in the wrong place. Regards, Ben
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
