Daniel Alejandro Benavides D.
dabenavidesd at yahoo.es
Thu Nov 24 22:30:35 CET 2011
in fact we need to address surely in a near future since xds Development Environment system has DEC-SRC Modula-3 infrastructure for Modula-2, Oberon-2 mixable Modules project compatibility:
This could of big help for a lot of good tools that have applied for Modula-3 type system R&D.
So instead of thinking in license mess, we would be thinking in language mixing.
About that they are thinking in releasing the source codes, perhaps, if Elego folks would show interest we could bring some of their tools.
The bottom line of this is we would have same capabilities like CM3-IDE ability to navigate sources, so to have source to source transformations seemingly navigation and code generations capabilities (like for C in XDS system).
I suggest we can make something for that, given the same structure of compilers, of course there is a lot of work, but we could do it, you are so great programmers.
Thanks in advance
--- El mié, 23/11/11, Daniel Alejandro Benavides D. <dabenavidesd at yahoo.es> escribió:
> De: Daniel Alejandro Benavides D. <dabenavidesd at yahoo.es>
> Asunto: Re: [M3devel] m2tom3
> Para: m3devel at elegosoft.com, vintagecoder at aol.com
> Fecha: miércoles, 23 de noviembre, 2011 12:16
> Hi all:
> a perfect example of compatibility is the DEC-SRC
> SRCCollector Interface inter with GNU C Boehm's Collector
> compatible interface:
> And that happened a long time before  DEC-SRC closing so
> they knew at least that it could be possible to compile (and
> inferring types)/link to interchange both collectors (fully
> capable and enough compatible interfaces to make GC-safe in
> both DEC-SRC Modula-3 and GNU C languages, where is the
> counterexample for what you say) flawlessly say in any
> Thanks in advance
>  H.-J. Boehm and Z. Shao, “Inferring Type Maps during
> Garbage Collection,” IN OOPSLA ’93 WORKSHOP ON MEMORY
> MANAGEMENT AND GARBAGE COLLECTION, 1993.
> --- El mié, 23/11/11, vintagecoder at aol.com
> <vintagecoder at aol.com>
> > De: vintagecoder at aol.com
> <vintagecoder at aol.com>
> > Asunto: Re: [M3devel] m2tom3
> > Para: m3devel at elegosoft.com
> > Fecha: miércoles, 23 de noviembre, 2011 11:19
> > > Would it be useful to
> > dual-licence new code under the LGPL(2 or later) on
> > > the remote chance that other parts of Modula 3
> > someday also be so
> > > licenced. Or, for that matter, that
> > might want to translate it
> > > to another language, by hand or otherwise?
> > would then be a derived
> > > work, also LGPL-able.
> > The Critical Mass license is perfectly fine. What is
> > sick fascination
> > with GPL? Why can't people just leave things alone and
> > try to force
> > other people to live according to their rules. LGPL is
> > a slippery
> > slope.
> > > Just trying to reduce future barriers to
> > interoperation.
> > Really? The GPL never reduced any barriers. It is
> > about* barriers.
> > You truly want to reduce future barriers? Then
> > public-domain your code or
> > use a BSD or MIT license. Or just use the Critical
> > license and stop
> > trying to turn everything into Linux.
More information about the M3devel