[M3devel] Package dependencies.

Daniel Alejandro Benavides D. dabenavidesd at yahoo.es
Thu May 17 03:58:50 CEST 2012


Hi all:
correct but since 70's anybody could use a CG machine to reproduce the language in any environment and then port it from there to any other machine of similar characteristics.
I think most of M3CG was inspired by Titan RISC DEC chip, but it came first by an effort to emulate the VAX on a RISC and if Modula-3 ever succeeded by running a VAX instruction it doesn't need to be such, so don't raise a concern on the language it was born and so, but in the language it had to be arise in.
That said, Modula-3 or anything is much compact in a RISC machine than in any other CISC-like machine, which is for what C was created in first place as Macro-package then used as a Programming language on its own. Modula-3 was a ready Programming environment for the VAX native back-end for a RISC. This was an  environment in for which you could see the benefits of a good small language enough powerful to run a native system in and so.
Thanks in advance


 

--- El mié, 16/5/12, Jay K <jay.krell at cornell.edu> escribió:

De: Jay K <jay.krell at cornell.edu>
Asunto: Re: [M3devel] Package dependencies.
Para: hendrik at topoi.pooq.com, "m3devel" <m3devel at elegosoft.com>
Fecha: miércoles, 16 de mayo, 2012 19:03




 >> I don't know how this works with bootstrapping self-hosting languages
 
 
  I think you hit the nail on the head -- "bootstrapping self-hosting languages". Good!  
  Keep using that phrase if you email folks asking about this, and make sure they understand it.  
 
 
     Meanwhile, I still want to generate fairly portable C or C++ to get around the problem. :)   
     First I'm going to upgrade to gcc 4.6 backend, and then maybe 4.7..stalling... :)    
 
 
   >  What do they do with stuff written in Haskell, C#, etc.?  
   > They'd be happy with it provided they have Haskel, C#, etc.     

 
Right: I should have said a C# compiler written in C#, a Haskell compiler written in Haskell, etc.
 
 
 - Jay
 
> Date: Wed, 16 May 2012 17:07:06 -0400
> From: hendrik at topoi.pooq.com
> To: m3devel at elegosoft.com
> Subject: [M3devel] Package dependencies.
> 
> On Wed, May 16, 2012 at 08:40:51PM +0000, Jay K wrote:
> > 
> >  >  And is there also a source package built?
> > 
> > 
> >  No. It would be C code anyway, so not source from most 
> > people's point of view.
> > 
> >  
> > > Because the source package is what's needed for uploading to 
> > > Debian.
> > 
> > 
> > They wouldn't like it anyway.
> >  What do they do with stuff written in Haskell, C#, etc.?
> > 
> 
> They'd be happy with it provided they have Haskel, C#, etc. 
> implementations already in the system.  A Debian package 
> can have build-dependencies, which is other packages that 
> have to be installed to builld it.  I don't know how this works 
> with bootstrapping self-hosting languages.  Maybe it takes 
> ad-hockery.  Maybe a new release build-depends on the 
> previous one.  Or on anything aat least as up-to-date as 
> the previous one.
> 
> -- hendrik
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20120517/cb176be8/attachment-0002.html>


More information about the M3devel mailing list