Gregg Reynolds wrote:
> On 11/26/07, KHMan <[EMAIL PROTECTED]> wrote:
>> Joshua Phillips wrote:
>>> Oughtn't tcc be broken into multiple source files?
>> I tried studying the sources over the weekend, and it looks like a
>
> While you're at it, feel free to dump notes to http://tcc.wikidot.com/
A
On 11/26/07, KHMan <[EMAIL PROTECTED]> wrote:
> Joshua Phillips wrote:
> > Oughtn't tcc be broken into multiple source files?
>
> I tried studying the sources over the weekend, and it looks like a
While you're at it, feel free to dump notes to http://tcc.wikidot.com/
-gregg
changeset ac0ea0043e55 - Start breaking up tcc.c, starting with tcc.h
...oh, it's already been tried (and started)
On Monday 26 November 2007 23:53:42 Mike wrote:
> LOL. You could break it into whatever organization you want. It seems
> like tcc.c uses #include ".c" a lot. I like that usage, do
Hmm, kind of. It's slow to recompile though, after making a change.
Maybe I should speed up the build process by using tcc :)
On 26/11/2007, Mike <[EMAIL PROTECTED]> wrote:
> LOL. You could break it into whatever organization you want. It seems
> like tcc.c uses #include ".c" a lot. I like that
Joshua Phillips wrote:
> Oughtn't tcc be broken into multiple source files?
I tried studying the sources over the weekend, and it looks like a
lot of functionality is mashed together, due to its "tiny"
heritage. So I think breaking up tcc.c would be a non-trivial
task. Perhaps worth a shot, though
LOL. You could break it into whatever organization you want. It seems
like tcc.c uses #include ".c" a lot. I like that usage, don't
you?
Joshua Phillips wrote:
Oughtn't tcc be broken into multiple source files?
___
Tinycc-devel mailing list
Tiny
Oughtn't tcc be broken into multiple source files?
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
