Memory Limit for Visual Studio 2005???

[Lucian Wischik]

I was flabbergasted by the degree of productivity that your seem to have
demonstrated here. Could you point me in the direction where I can learn this
degree of productivity in compiler construction? I want to be able to do
something comparable to what you have done, and preferably in a native code
language such as C++.

As you said, ASTs is one part of it.

Something that C# people won't like to hear is that functional
languages (F#, caml, ML) are many times better than C# for
manipulating ASTs. In a functional language you'll use about 1/5th as
many lines to accomplish the same thing. And it has far fewer bugs.
And you'll code it up at least five times as fast.

Something that you, Peter, won't like to hear is that garbage
collection is the right way to do a compiler. It increases your
productivity a lot, and it ends up performing faster than whatever
custom allocators+deallocators you've tried to write yourself in C++.

 

[Peter Olcott]

As you said, ASTs is one part of it.

Something that C# people won't like to hear is that functional
languages (F#, caml, ML) are many times better than C# for
manipulating ASTs. In a functional language you'll use about 1/5th as
many lines to accomplish the same thing. And it has far fewer bugs.
And you'll code it up at least five times as fast.

Something that you, Peter, won't like to hear is that garbage
collection is the right way to do a compiler. It increases your
productivity a lot, and it ends up performing faster than whatever
custom allocators+deallocators you've tried to write yourself in C++.

I must have the commercial project complete within a maximum of six months. This
project is currently written in Visual C++ 6.0, and I know C++ quite well. This
already assumes 90 hour work weeks. All that I need to end up with is a subset
of the "C" programming language as applied to a specific infrastructure.