[M3devel] missing libm3/src/types

Daniel Alejandro Benavides D. dabenavidesd at yahoo.es
Thu May 19 18:18:20 CEST 2011


Hi all:
if it could affect the compiler usage if in fact such usage why would one give such types inside cm3 or m3build process aside of m3core, I mean the top hierarchy must be primitive types at bottom then refs, objects, etc or reverse, and its type rules besides modules and interfaces, perhaps a good example would be to see the interfaces of Modula-2+ Vulcan system, since it had everything compiled cached and managed to survive even crashes and bridge everything to the Vesta CM system, quick large compilations, see:
http://www-cs-faculty.stanford.edu/~eroberts/cv.html

An advanced system to type check may require quick timely access to large nodes since type inference is something very dependent on its size, a bigger tree a bigger problem, even if ever get to compile type inferencing (an Obliq prototype already done), but many modules around would be like dancing in hard feet over sized.
 
Thanks in advance

--- El jue, 19/5/11, Tony Hosking <hosking at cs.purdue.edu> escribió:

> De: Tony Hosking <hosking at cs.purdue.edu>
> Asunto: Re: [M3devel] missing libm3/src/types
> Para: "Rodney M. Bates" <rodney_bates at lcwb.coop>
> CC: "m3devel" <m3devel at elegosoft.com>
> Fecha: jueves, 19 de mayo, 2011 10:45
> Moved to m3core.  There
> shouldn't be anything in libm3/types.
> 
> On May 19, 2011, at 11:41 AM, Rodney M. Bates wrote:
> 
> > What happened to cm3/m3-libs/libm3/src/types and its
> contents in the head?
> > They all are gone, but
> cm3/m3-libs/libm3/src/m3makefile contains
> > include_dir ("types"), and libm3 won't build:
> > 
> > 
> > rodney at allegheny:~/proj/m3/cm3-new/cm3/scripts$
> ./do-pkg.sh build libm3
> > /home/rodney/proj/m3/cm3-new/cm3/scripts/pkgmap.sh -c
> "cm3 -build -override $RARGS
> -DROOT='/home/rodney/proj/m3/cm3-new/cm3' " libm3
> > === package
> /home/rodney/proj/m3/cm3-new/cm3/m3-libs/libm3 ===
> > +++ cm3 -build -override $RARGS
> -DROOT='/home/rodney/proj/m3/cm3-new/cm3'  +++
> > --- building in AMD64_LINUX ---
> > 
> >
> "/home/rodney/proj/m3/cm3-new/cm3/m3-libs/libm3/src/m3makefile",
> line 27: quake runtime error: unable to open
> "/home/rodney/proj/m3/cm3-new/cm3/m3-libs/libm3/src/types/m3makefile"
> for reading
> > 
> > --procedure--  -line-  -file---
> > include_dir        -- 
> <builtin>
> > include_dir        27 
> /home/rodney/proj/m3/cm3-new/cm3/m3-libs/libm3/src/m3makefile
> >               
>     6 
> /home/rodney/proj/m3/cm3-new/cm3/m3-libs/libm3/AMD64_LINUX/m3make.args
> > 
> > Fatal Error: package build failed
> > ==> /home/rodney/proj/m3/cm3-new/cm3/m3-libs/libm3
> done
> > 
> > rodney at allegheny:~/proj/m3/cm3-new/cm3/scripts$
> > 
> > It looks like either types needs to come back, or
> include_dir ("types") needs to go away,
> > but which?  If somebody knows, it would save a
> lot of time poking around.
> 
> 



More information about the M3devel mailing list