RE: [Oopic-compiler-devel] Hello from the new guy

[D. D. M. <dd...@mc...>]

Hi Brian,

> I'd be interested to hear Andy's/Daniel's thoughts on Python.

I guess that is my cue....

I'm personally indifferent to language choice.  My experience has led to a
somewhat jaded view of the intensity of most of the 'language wars'; and has
shown me all require a mastery of the grammar/syntax and an appreciation of the
applicability of the specific competency of the tool to the application
(remember the adage, when a carpenter has only a hammer, everything looks like a
nail).

I'll be learning a bit about compiler design & code generation whatever the
decisions.

Whatever is done, I think I'd recommend a complete toolkit as the
end-deliverable.  Something like what Eric Weddington did for the AVR
microprocessor with the WinAVR toolkit that bundles all of the required/optional
components (see www.AVRfreaks.net and http://sourceforge.net/projects/winavr).

Why I'm involved:  I am one of those that got burnt by a botched IDE
installation, but mostly am interested in the puzzle of the figuring out the
internals of the OOpic, especially the VC stuff.

Best Regards,
Daniel