From mint-bounce@lists.fishpool.fi Thu Jan 7 18:02:13 2010 X-SourceIP: 77.249.76.7 Message-ID: <4B46676B.7020001@chello.nl> Date: Thu, 07 Jan 2010 23:59:55 +0100 From: Henk Robbers User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] QED References: <201001072153.54168.oak@helsinkinet.fi> <4B463D08.9000101@online.no> <201001072249.46830.oak@helsinkinet.fi> In-Reply-To: <201001072249.46830.oak@helsinkinet.fi> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: h.robbers@chello.nl Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Hello. Eero Tamminen wrote: > Hi, > > On Thursday 07 January 2010, Jo Even Skarstein wrote: > >>>>>c) Don't integrate everything into one binary, but create several >>>>>tools and tie them together with a clever protocol. >>>>> >>>>>Personally I'd prefer (c). >>> >>>I like (c) too, but what about extending AHCC instead of QED? >> >>That is a great idea, but those who prefer other compilers might not >>agree. Personally I would love to see the AHCC IDE extended. I still >>have to get used to the toolbox-concept, but other than that AHCC is a >>really good IDE. If it had some tools to visualize the code structure >>(to aid navigation) it would be almost perfect for my needs. > On my todo list for a long time is to extend the help database with a representation of the call & function graph. Implementing the Coldfire target is again something that will postpone the idee. > > I guess extending the AHCC IDE would mean making it more configurable, > also in regards to what compiler and text editor it uses... > Hmmm, without the editor and the compiler there remains only a very simple shell. Too simple to be of interest to you. > But that of course depends on what Henk Robbers thinks about this idea. ;-) > I like it small and simple as it is now. AHCC is primarily written for my own pleasure. If 1 or 2 of you like it as it is, I am happy. This means that I will be the only maintainer of AHCC as long as I want to work on it. My advice for a modern powerfull IDE is to build a graphical interface around Bash and Make. Such a system could run GCC as well as the AHCC compiler proper (AHCC_T.TTP) and linker (AHCL.TTP) as they are. If you would like to benefit from the help database, you can run AHHC_P.TTP with option -h. -- Groeten; Regards. Henk Robbers. http://members.chello.nl/h.robbers Interactive disassembler: TT-Digger; http://digger.atari.org A Home Cooked C compiler: AHCC; http://ahcc.atari.org