Re: Speed advantage of language written in itself?



On Aug 22, 6:08 pm, defn noob <circularf...@xxxxxxxx> wrote:
If you have a language written in itself the advantages are?

1. Bug source reduction: Once the implementation runs or compiles
itself, you don't need to worry about bugs in a separate compiler
causing problems in yours.
2. Testing efficiency: The implementation itself effectively becomes a
component of its own test suite. There's also a simple probabilistic
argument that when applied to a given test suite, a bug is more likely
to be found in a system that runs or compiles itself than in one that
doesn't.
3. Positive reinforcement: There is immediate reward as you implement
optimizations: your own build/test cycles go faster!
.



Relevant Pages

  • Re: VS2005 major development bug
    ... Which Bug, haven't found one in your example only an access exception? ... If you had used the project which was in the .zip file you would have seen that it was compiled with Managed C++ and not C++/CLI, and that it compiles fine. ... To get detailed information by the compiler define your "pimpl" class outside the form. ... The pimpl class is a nested class of my ref class so that it can access all of the members of my ref class ...
    (microsoft.public.dotnet.languages.vc)
  • Re: top-level const-ness inhibits override
    ... compatibility switches for the EDG front end, since I'd be quite surprised if EDG had this bug in their ISO compliant mode. ... Comeau C++ compiles it fine. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: What makes a good C/C++ programmer?
    ... > it compiles and runs without complaint. ... > and the candidate is familiar with smart pointers, ... > because the programmer cannot depend upon the compiler or testing ... > we would expect that this bug would manifest itself eventually. ...
    (comp.lang.c)
  • Re: What makes a good C/C++ programmer?
    ... > it compiles and runs without complaint. ... > and the candidate is familiar with smart pointers, ... > because the programmer cannot depend upon the compiler or testing ... > we would expect that this bug would manifest itself eventually. ...
    (comp.lang.cpp)
  • Re: Failing unittest Test cases
    ... > the test suite should be runnable and silent at every checkin. ... failing unit test and then 6 months later when an apparently unrelated bug ... This shifts the act of accepting a bug from putting it onto some ... realise that every broken test should have an associated tracker entry), ...
    (comp.lang.python)