tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] TinyC++


From: Basile Starynkevitch
Subject: Re: [Tinycc-devel] TinyC++
Date: Tue, 19 Oct 2010 09:03:14 +0200

On Tue, 19 Oct 2010 01:56:47 -0500
"Rick C. Hodgin" <address@hidden> wrote:
> 
> I have been looking at TinyCC's source code and I think I'm going to
> continue developing my own compiler from the ground up as I have been.
> What I have is quite small, fast, and although it is not optimizing in
> any way, it looks to provide usable logic, processing, and the ability
> to do what my primary goal is:  be able to launch the debugger, make
> changes to my source, recompile them on-the-fly, and update the binary
> image running in memory, as is seen in Microsoft's Visual Studio and
> Debugger, with their "edit-and-continue" mode.
> 
> I am also working on my own debugger for this, as I find GDB to be way
> antiquated and/or bloaty (probably due to its antiquity roots).
> 
> It's all still a way-pre-alpha work, but I'm heading toward it.

I hope it will be soon published = "released" (even in alpha stage)
under an opensource license (e.g. GPLv3). Please publish your work very
early!

Did you look at nwcc, http://nwcc.sourceforge.net/

Did you consider putting (or using) a full garbage collector inside
your compiler (e.g. Boehm's one, or perhaps make your own)? Putting a
GC in a compiler is IMHO (or perhaps IMNSHO) a wise decision to be made
very early, because compilers deal with complex circular data
structures, and garbage collection / memory management is a *global*
property of your software. I believe that if you don't add a GC in your
compiler you could be sorry years after.

Cheers.
-- 
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mine, sont seulement les miennes} ***



reply via email to

[Prev in Thread] Current Thread [Next in Thread]