<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div id="__MailbirdStyleContent" style="font-size: 8pt;font-family: arial;color: #000000">
Some useful ideas how to to that could be borrowed from the <a href="https://golang.org/doc/"><span style="font-size: 8pt;color: rgb(0, 0, 0)">golang documentation</span></a>. Have at least a look at it.
<div class="mb_sig"></div>
<blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">On 01/11/2016 11:13:37, Wolfgang Keller <9103784@gmx.de> wrote:</p>
I welcome your initiative and send you some of the thoughts for it. <br>
<br>
Modula-3 Release Endeavour <br>
<br>
= Desirables = <br>
<br>
-- Documentation <br>
- overview of public executables and what they can do <br>
- compiler application guide <br>
- module package guide <br>
- setup guide <br>
- up-to-date language definition (text) <br>
- implementation status report <br>
- license, legal and project reference material <br>
<br>
-- Structuring <br>
- add a "doc" folder and populate it with documents <br>
- does it make sense to structure the "lib" module library? <br>
- package categories: core, io, nearer, further, services <br>
<br>
= Progressing = <br>
<br>
- think about what goes into the release and what it should do <br>
- define a structure for the release <br>
- define a set of files that go into the release <br>
- define the configuration context and make a document for it <br>
- create a "digest all = complete+verifying" configuration program (if <br>
feasible) <br>
- make all release content also available in the CM3 git <br>
- define an automated translation from CM3 repository to release build <br>
(perhaps Ant is sufficient for this, perhaps you need a program <br>
in particular if some files need transformation for the transition) <br>
- live happy ever after <br>
<br>
= Policy = <br>
<br>
- only include into release what provenly is working <br>
<br>
[wk - 01.11.2016] <br>
<br>
Am 28.10.2016 um 16:42 schrieb Rodney M. Bates: <br>
> I agree, we very much need to make a new release. There has been a lot <br>
> of development since the last one, especially for having a small <br>
> developer <br>
> community. <br>
> <br>
> I have often thought I would be willing to do the work to do it, but <br>
> every <br>
> time, I get stuck not having any idea what needs to be done. For one <br>
> thing, I presume it entails verifying that things build and work on all <br>
> the various targets, which would further entail having access to one <br>
> of each of them. <br>
> <br>
> Are such machines available? Any advice on how to proceed? <br>
> <br>
> On a related topic, we need to make some changes to the compiler IR, <br>
> as defined <br>
> in M3CG.i3 and M3CG_Ops.i3. I have been collecting a list of my own for <br>
> some time. This is a lot of (mostly rather mundane) work, and it creates <br>
> front/back end compatibility issues. It would be best to do as many <br>
> as possible at one time and get them in before a release, so those not <br>
> doing compiler development could just use the release without being <br>
> bothered. <br>
> <br>
> Anybody have any changes to propose? <br>
> <br>
> On 10/21/2016 12:56 PM, dirk muysers wrote: <br>
>> If you want to improve your home you go to the builders market and <br>
>> acquire a drill, a hammer and so on. I you have taken a fancy to a <br>
>> programming language, you download and install --or pay for-- a <br>
>> compiler and start to program in it. Not so for Modula-3. Its source <br>
>> code is in the hands of a small community of dedicated people for <br>
>> which its maintenance has become an endeavour by itself. This is <br>
>> laudable and great, but what about the simple potential Modula 3 USER <br>
>> ? One cannot hope that he (or she, let's remain PC) will clone the <br>
>> whole shebang from Github and begin to dabble in configuration files, <br>
>> Python and Shell scripts to build his version of what represents only <br>
>> a tool after all. All he wants is to have a compiler and begin to <br>
>> work on his apps and favorite software projects. So keeping alive a <br>
>> language is not enough, it has also to be made easily available to <br>
>> those wanting to use it as their tool and who are not interested in <br>
>> compiler building or simply have more urgent <br>
>> things to do. So when will there be the next Modula 3 release? <br>
>> <br>
>> <br>
>> _______________________________________________ <br>
>> M3devel mailing list <br>
>> M3devel@elegosoft.com <br>
>> https://m3lists.elegosoft.com/mailman/listinfo/m3devel <br>
>> <br>
> <br>
<br>
_______________________________________________ <br>
M3devel mailing list <br>
M3devel@elegosoft.com <br>
https://m3lists.elegosoft.com/mailman/listinfo/m3devel <br>
</blockquote>
</div>
</body>
</html>