[M3devel] Think we need a new release.

[Daniel Alejandro Benavides D.]

Hi all:
Modula-2+ distributed compiler didn't require languages changes but extensive testing and some distributed setting, which is why you need some sort of engineering process, at least is what I think that happens.
If you don't want dynamic compilation/interpretation that's up to one's needs, but currently most compilers do have some sort of dynamic interpretation capabilities, and being Modula-3 and innovative platform, it must have one. That's again what I think. I guess the way of not interrupting is just is m3-obliq stuff (since it's the scripting expression of Modula-3 RT) and prepare for the needed changes in the next big release. So for me would be like v 5.10 < 6.0
Thanks in advance

--- El vie, 10/2/12, m3 at sol42.com <m3 at sol42.com> escribió:

> De: m3 at sol42.com <m3 at sol42.com>
> Asunto: Re: [M3devel] Think we need a new release.
> Para: "m3devel" <m3devel at elegosoft.com>
> Fecha: viernes, 10 de febrero, 2012 16:50
> On 10 Feb 2012, at 15:14, Vintage
> Coder wrote:
> > What is the purpose of a new release? A compiler and
> runtime that work presumably only need fixes.
> 
> Agreed.  I can think of two reasons: adding "must have"
> stuff to the standard library, and fixing bugs or improving
> library, compiler, or runtime.  Note that "must have"
> should probably be evaluated in the context of systems
> programming, which is what Modula-3 is for.
> 
> Even adding new platforms should not require bumping the
> version number if it is the existing infrastructure that is
> being ported.
> 
> There are loads of "greatest next thing" languages out there
> that you have to re-learn every few releases.  Modula-3
> is thankfully not one of them.  Want new stuff in the
> language?  Then you want Modula-3+ or Modula-4.
> 
> Regards.
> -Daniel
> 
> 
>