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

[Neil D. <nd...@us...>]

Interesting idea.  This would also encourage people to join in with the
development effort, if the 'toolkit' they download contains everything, any
extra tools, all documentation, known bugs (if any!), new features for each
release etc.

The question of whether we ship tools we don't maintain (eg Python if we go
down that route, *lex, yacc/bison etc) is a tricky one.  If someone's
installing our stuff and already has some of those tools installed, do they
use ours or their existing ones?  Plus, how completely would we support
platforms?  If we're shipping platform dependent tools (the Python
interpreter for example, if we use Python) then we could potentially be
shipping a dozen different ones (for different Linux distributions,
FreeBSD, etc etc).

You're right about the maintenance effort, but it shouldn't be problematic
if we're using version control (CVS or whatever).

D. Daniel McGlothin wrote:
> What I had in mind was:
> 
> 	a. The tools the project generates
> 	b. The tools the project uses to construct (a).
> 	c. The support environment stuff required for (b).
> 
> Thus, given recent discussion, it would include compiler, downloader, IDE (if
> generated), source for the previous, Python (for Win, Max, Un*x), *lex, *yac,
> etc.  Don't forget to include documentation for all.
> 
> The thinking is that the easier it is for a relative novice to acquire/use, the
> more wide-spread our toolchain may become.
> 
> Of course, there is a maintenance effort to keep track of current releases of
> the above.
> 
> Best Regards,
> Daniel
> 
> > -----Original Message-----
> > From: oop...@li...
> > [mailto:oop...@li...]On Behalf Of
> > Neil Durant
> > Sent: Friday, May 28, 2004 4:40 PM
> > To: oop...@li...
> > Subject: Re: [Oopic-compiler-devel] Hello from the new guy
> >
> >
> > D. Daniel McGlothin wrote:
> > > 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).
> >
> > What tools did you have in mind, besides a compiler and possible IDE ?
> >
> > I guess the cross-platform OOPic code uploader would be one tool.
> >
> > And one thing I think could be useful would be an assembler that assembles
> > the Forth-like OOPic op-codes into hex.  It would be trivial to do, and it
> > could be useful to test ideas before implementing new language features,
> > and testing out optimisation techniques etc.
> >
> > Any other ideas?
> >
> > Neil
> > --
> > Neil Durant
> > <nd...@us...>
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: Oracle 10g
> > Get certified on the hottest thing ever to hit the market... Oracle 10g.
> > Take an Oracle 10g class now, and we'll give you the exam FREE.
> > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> > _______________________________________________
> > Oopic-compiler-devel mailing list
> > Oop...@li...
> > https://lists.sourceforge.net/lists/listinfo/oopic-compiler-devel
> >
> >
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g. 
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Oopic-compiler-devel mailing list
> Oop...@li...
> https://lists.sourceforge.net/lists/listinfo/oopic-compiler-devel
> 

-- 
Neil Durant
<nd...@us...>