<<We could even write the preprocessor in CompileIt! and call the code resource from CodeWarriors example preprocessor code. What do you think about that?>> Only problem is that CompileIt! code is 68k, and also not all that well suited for writing a preprocessor (IMO). I don't think it would be worth the trouble for the novelty of doing it with CompileIt!. Not that a part of me doesn't like the idea- I just don't think it's the best choice. I'll keep you informed of my progress (or lack of). I think the egcs route is by far the most valuable, so I'll have to get off my duff and get familiar with the egcs source. Anthony, let me know if you get anywhere with that egcs Mac port. Needless to say, I'm very interested if you get it to compile. Brian
- Re: OODL: Goofball OT question Yennie
- Re: OODL: Goofball OT question DeRobertis
- Re: Re: OODL: Goofball OT question MP0werd
- Re: Re: OODL: Goofball OT question M. Uli Kusterer
- Re: Re: OODL: Goofball OT question DeRobertis
- Re: OODL: Goofball OT question Yennie
- Re: OODL: Goofball OT question DeRobertis
- Re: OODL: Goofball OT question Yennie
- Re: OODL: Goofball OT question M. Uli Kusterer
- Re: OODL: Goofball OT question DeRobertis
- Re: OODL: Goofball OT question Yennie
- Re: OODL: Goofball OT question M. Uli Kusterer
- Re: OODL: Goofball OT question DeRobertis
- Re: OODL: Goofball OT question DeRobertis
- Re: OODL: Goofball OT question Yennie
- Re: OODL: Goofball OT question Yennie
- Re: OODL: Goofball OT question M. Uli Kusterer
- Re: OODL: Goofball OT question Yennie
- Re: OODL: Goofball OT question DeRobertis
- Re: Re: OODL: Goofball OT question MP0werd
- Re: Re: OODL: Goofball OT question DeRobertis
