From 9103784 at gmx.de Tue Nov 1 11:13:27 2016 From: 9103784 at gmx.de (Wolfgang Keller) Date: Tue, 1 Nov 2016 11:13:27 +0100 Subject: [M3devel] Rants about an improbable release In-Reply-To: <581363DE.9060401@lcwb.coop> References: <581363DE.9060401@lcwb.coop> Message-ID: I welcome your initiative and send you some of the thoughts for it. Modula-3 Release Endeavour = Desirables = -- Documentation - overview of public executables and what they can do - compiler application guide - module package guide - setup guide - up-to-date language definition (text) - implementation status report - license, legal and project reference material -- Structuring - add a "doc" folder and populate it with documents - does it make sense to structure the "lib" module library? - package categories: core, io, nearer, further, services = Progressing = - think about what goes into the release and what it should do - define a structure for the release - define a set of files that go into the release - define the configuration context and make a document for it - create a "digest all = complete+verifying" configuration program (if feasible) - make all release content also available in the CM3 git - define an automated translation from CM3 repository to release build (perhaps Ant is sufficient for this, perhaps you need a program in particular if some files need transformation for the transition) - live happy ever after = Policy = - only include into release what provenly is working [wk - 01.11.2016] Am 28.10.2016 um 16:42 schrieb Rodney M. Bates: > I agree, we very much need to make a new release. There has been a lot > of development since the last one, especially for having a small > developer > community. > > I have often thought I would be willing to do the work to do it, but > every > time, I get stuck not having any idea what needs to be done. For one > thing, I presume it entails verifying that things build and work on all > the various targets, which would further entail having access to one > of each of them. > > Are such machines available? Any advice on how to proceed? > > On a related topic, we need to make some changes to the compiler IR, > as defined > in M3CG.i3 and M3CG_Ops.i3. I have been collecting a list of my own for > some time. This is a lot of (mostly rather mundane) work, and it creates > front/back end compatibility issues. It would be best to do as many > as possible at one time and get them in before a release, so those not > doing compiler development could just use the release without being > bothered. > > Anybody have any changes to propose? > > On 10/21/2016 12:56 PM, dirk muysers wrote: >> If you want to improve your home you go to the builders market and >> acquire a drill, a hammer and so on. I you have taken a fancy to a >> programming language, you download and install --or pay for-- a >> compiler and start to program in it. Not so for Modula-3. Its source >> code is in the hands of a small community of dedicated people for >> which its maintenance has become an endeavour by itself. This is >> laudable and great, but what about the simple potential Modula 3 USER >> ? One cannot hope that he (or she, let's remain PC) will clone the >> whole shebang from Github and begin to dabble in configuration files, >> Python and Shell scripts to build his version of what represents only >> a tool after all. All he wants is to have a compiler and begin to >> work on his apps and favorite software projects. So keeping alive a >> language is not enough, it has also to be made easily available to >> those wanting to use it as their tool and who are not interested in >> compiler building or simply have more urgent >> things to do. So when will there be the next Modula 3 release? >> >> >> _______________________________________________ >> M3devel mailing list >> M3devel at elegosoft.com >> https://m3lists.elegosoft.com/mailman/listinfo/m3devel >> > From dmuysers at hotmail.com Tue Nov 1 11:19:50 2016 From: dmuysers at hotmail.com (dirk muysers) Date: Tue, 1 Nov 2016 10:19:50 +0000 Subject: [M3devel] Rants about an improbable release In-Reply-To: References: <581363DE.9060401@lcwb.coop> Message-ID: Some useful ideas how to to that could be borrowed from the golang documentation. Have at least a look at it. On 01/11/2016 11:13:37, Wolfgang Keller <9103784 at gmx.de> wrote: I welcome your initiative and send you some of the thoughts for it. Modula-3 Release Endeavour = Desirables = -- Documentation - overview of public executables and what they can do - compiler application guide - module package guide - setup guide - up-to-date language definition (text) - implementation status report - license, legal and project reference material -- Structuring - add a "doc" folder and populate it with documents - does it make sense to structure the "lib" module library? - package categories: core, io, nearer, further, services = Progressing = - think about what goes into the release and what it should do - define a structure for the release - define a set of files that go into the release - define the configuration context and make a document for it - create a "digest all = complete+verifying" configuration program (if feasible) - make all release content also available in the CM3 git - define an automated translation from CM3 repository to release build (perhaps Ant is sufficient for this, perhaps you need a program in particular if some files need transformation for the transition) - live happy ever after = Policy = - only include into release what provenly is working [wk - 01.11.2016] Am 28.10.2016 um 16:42 schrieb Rodney M. Bates: > I agree, we very much need to make a new release. There has been a lot > of development since the last one, especially for having a small > developer > community. > > I have often thought I would be willing to do the work to do it, but > every > time, I get stuck not having any idea what needs to be done. For one > thing, I presume it entails verifying that things build and work on all > the various targets, which would further entail having access to one > of each of them. > > Are such machines available? Any advice on how to proceed? > > On a related topic, we need to make some changes to the compiler IR, > as defined > in M3CG.i3 and M3CG_Ops.i3. I have been collecting a list of my own for > some time. This is a lot of (mostly rather mundane) work, and it creates > front/back end compatibility issues. It would be best to do as many > as possible at one time and get them in before a release, so those not > doing compiler development could just use the release without being > bothered. > > Anybody have any changes to propose? > > On 10/21/2016 12:56 PM, dirk muysers wrote: >> If you want to improve your home you go to the builders market and >> acquire a drill, a hammer and so on. I you have taken a fancy to a >> programming language, you download and install --or pay for-- a >> compiler and start to program in it. Not so for Modula-3. Its source >> code is in the hands of a small community of dedicated people for >> which its maintenance has become an endeavour by itself. This is >> laudable and great, but what about the simple potential Modula 3 USER >> ? One cannot hope that he (or she, let's remain PC) will clone the >> whole shebang from Github and begin to dabble in configuration files, >> Python and Shell scripts to build his version of what represents only >> a tool after all. All he wants is to have a compiler and begin to >> work on his apps and favorite software projects. So keeping alive a >> language is not enough, it has also to be made easily available to >> those wanting to use it as their tool and who are not interested in >> compiler building or simply have more urgent >> things to do. So when will there be the next Modula 3 release? >> >> >> _______________________________________________ >> M3devel mailing list >> M3devel at elegosoft.com >> https://m3lists.elegosoft.com/mailman/listinfo/m3devel >> > _______________________________________________ M3devel mailing list M3devel at elegosoft.com https://m3lists.elegosoft.com/mailman/listinfo/m3devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From dabenavidesd at yahoo.es Fri Nov 4 03:14:12 2016 From: dabenavidesd at yahoo.es (Daniel Alejandro Benavides D.) Date: Fri, 4 Nov 2016 02:14:12 +0000 (UTC) Subject: [M3devel] Rants about an improbable release In-Reply-To: <58161C78.2080101@lcwb.coop> References: <581363DE.9060401@lcwb.coop> <20161028174401.406875f4bf526b8967680b8a@elegosoft.com> <5815093A.4080907@lcwb.coop> <759940168.749551.1477791290613@mail.yahoo.com> <58161C78.2080101@lcwb.coop> Message-ID: <1278502851.1630517.1478225652196@mail.yahoo.com> Hello Rodney and everyone else:yes, I got your point; and I have had a hard time thinking about it ; but it's simple: What else can we ask if cm3 has 'sort' of cloud development environment; everyone could (if they want) else we, better to say, set up an environment, and make it available to others, so everyone can compile their examples and if they like the environment, join our community and we will give they commercial support (elego folks and specialists).I tried to ideate a front-middle-back end distributed environment so we could just just have one big middle end server and reuse Java-based eclipse-plugin frontend and gcc-based m3cg or Scale Java-based backend to make long compilations more pleasant too.I have to make a proof of this idea, if it's useful at the end or not, i.e make faster compilations than in standalone mode. Thanks in advance? El Domingo 30 de octubre de 2016 11:16, Rodney M. Bates escribi?: On 10/29/2016 08:34 PM, Daniel Alejandro Benavides D. wrote: > Hello all: > contrary to most of you think; I still see cvsup update efficiency by file and compiler recompile only updated sources method as the most advanced build/update system of what I have seen in this world. Please keep it that way > But this does not address what we need for a release.? A release needs to provide a way for somebody who has no Modula3 compiler at all to download and install already-compiled binaries, not only for the compiler itself, but probably much of the other stuff as well, though not all in a single package. > Thanks in advance > > > El S?bado 29 de octubre de 2016 15:42, Rodney M. Bates escribi?: > > > > > On 10/28/2016 10:44 AM, Olaf Wagner wrote: >? > On Fri, 28 Oct 2016 09:42:38 -0500 >? > "Rodney M. Bates" > wrote: >? > >? >> I agree, we very much need to make a new release.? There has been a lot >? >> of development since the last one, especially for having a small developer >? >> community. >? >> >? >> I have often thought I would be willing to do the work to do it, but every >? >> time, I get stuck not having any idea what needs to be done.? For one >? >> thing, I presume it entails verifying that things build and work on all >? >> the various targets, which would further entail having access to one >? >> of each of them. >? >> >? >> Are such machines available?? Any advice on how to proceed? >? > >? > I think the most important thing would be to have an agreement on >? > - which platforms will be part of the release >? > - how the release will be packaged and deployed. >? > >? > I'd advise to concentrate on a small number of important platforms, > > OK, let's hear some nominations for important platforms. > > I need AMD64_LINUX and LINUXLIBC6.? For the future, I would probably want > a Windows version, and there are some others using Windows regularly, I think. > > Jay, where can we look for the latest more-aptly-renamed platform names? > > or >? > to have a simple standard procedure for all platforms (for example >? > cross-compiled bootstrap archives) > > Are these just tar files of /usr/local/cm3?? Do we want to keep using > cminstall? > > We are still requiring several static libraries (that are not part of CM3). > These present installation problems, as most distros now do not include them > by default, and, worse, it is quite a detective job to track from a name > like "libmumble.a not found" to what package needs to be installed.? We > probably want to configure to use mostly dynamic libraries.? Or maybe > be able to use either? > > and more convenient support for some >? > of them (for example Debian packages). >? > > > Yes, this would be very good.? Then they could go in package archives, and > installation would be much easier.? But we would also need to decide how > to break things up into packages.? E.g., would the stuff in groups like > do-cm3-comm and do-cm3-ui be separate?? Just matching what is in the various > do-cm3-* scripts or the named groups in pkginfo.txt won't work, because they > are highly non-disjoint.? We need a partition. > > Also, my understanding about packages is that, while putting together a > package that will work is not too difficult, some Linux distros have > stringent requirements about package contents that are a lot more work > to create. > > >? > Olaf >? > > > -- > Rodney Bates > rodney.m.bates at acm.org > > _______________________________________________ > M3devel mailing list > M3devel at elegosoft.com > https://m3lists.elegosoft.com/mailman/listinfo/m3devel > > > > > _______________________________________________ > M3devel mailing list > M3devel at elegosoft.com > https://m3lists.elegosoft.com/mailman/listinfo/m3devel > -- Rodney Bates rodney.m.bates at acm.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From rodney_bates at lcwb.coop Sun Nov 20 02:52:26 2016 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Sat, 19 Nov 2016 19:52:26 -0600 Subject: [M3devel] [modula3/cm3] f7036f: Fixed overflow bug In-Reply-To: <582ce61d2233a_54683ffa8ff6713c1366a2@hookshot-fe2-cp1-prd.iad.github.net.mail> References: <582ce61d2233a_54683ffa8ff6713c1366a2@hookshot-fe2-cp1-prd.iad.github.net.mail> Message-ID: <583101DA.9020905@lcwb.coop> On 11/16/2016 05:05 PM, GitHub wrote: > Branch: refs/heads/master > Home: https://github.com/modula3/cm3 > Commit: f7036fd9cb25680d85c31967b7f772c151469043 > https://github.com/modula3/cm3/commit/f7036fd9cb25680d85c31967b7f772c151469043 > Author: peter mckinna > Date: 2016-11-17 (Thu, 17 Nov 2016) > > Changed paths: > M m3-libs/m3core/src/float/Common/grisu/Grisu.m3 > > Log Message: > ----------- > Fixed overflow bug > > > Commit: ea3e1978b6fa08e12e2fbbce7184389d061b585a > https://github.com/modula3/cm3/commit/ea3e1978b6fa08e12e2fbbce7184389d061b585a > Author: peter mckinna > Date: 2016-11-17 (Thu, 17 Nov 2016) > > Changed paths: > M m3-libs/m3core/src/float/Common/DragonInt.m3 > > Log Message: > ----------- > Allocation should be minimum 4 words for 128 bit quads > (* assume the allocator zeros this array, min size 128 bytes for quads *) ----------------------------------------------------------^ bits? out := NEW(RefInt32,MAX(a.s, 4)); > > Commit: e4b419ae09d819675265f41fc9c354ee645c2c94 > https://github.com/modula3/cm3/commit/e4b419ae09d819675265f41fc9c354ee645c2c94 > Author: peter mckinna > Date: 2016-11-17 (Thu, 17 Nov 2016) > > Changed paths: > A m3-libs/m3core/src/float/Common/FloatUtils.i3 > A m3-libs/m3core/src/float/Common/FloatUtils.m3 > A m3-libs/m3core/src/float/Common/TextToFloat.i3 > A m3-libs/m3core/src/float/Common/TextToFloat.m3 > M m3-libs/m3core/src/float/Common/m3makefile > > Log Message: > ----------- > Added floating point conversion functions for 128 quads > > > Compare: https://github.com/modula3/cm3/compare/be8184edff3c...e4b419ae09d8 > -- Rodney Bates rodney.m.bates at acm.org From peter.mckinna at gmail.com Mon Nov 21 03:14:48 2016 From: peter.mckinna at gmail.com (Peter McKinna) Date: Mon, 21 Nov 2016 13:14:48 +1100 Subject: [M3devel] [modula3/cm3] f7036f: Fixed overflow bug In-Reply-To: <583101DA.9020905@lcwb.coop> References: <582ce61d2233a_54683ffa8ff6713c1366a2@hookshot-fe2-cp1-prd.iad.github.net.mail> <583101DA.9020905@lcwb.coop> Message-ID: Oops, Yes bits. More haste less speed. Will fix. On Sun, Nov 20, 2016 at 12:52 PM, Rodney M. Bates wrote: > > > On 11/16/2016 05:05 PM, GitHub wrote: > >> Branch: refs/heads/master >> Home: https://github.com/modula3/cm3 >> Commit: f7036fd9cb25680d85c31967b7f772c151469043 >> https://github.com/modula3/cm3/commit/f7036fd9cb25680d85c31 >> 967b7f772c151469043 >> Author: peter mckinna >> Date: 2016-11-17 (Thu, 17 Nov 2016) >> >> Changed paths: >> M m3-libs/m3core/src/float/Common/grisu/Grisu.m3 >> >> Log Message: >> ----------- >> Fixed overflow bug >> >> >> Commit: ea3e1978b6fa08e12e2fbbce7184389d061b585a >> https://github.com/modula3/cm3/commit/ea3e1978b6fa08e12e2fb >> bce7184389d061b585a >> Author: peter mckinna >> Date: 2016-11-17 (Thu, 17 Nov 2016) >> >> Changed paths: >> M m3-libs/m3core/src/float/Common/DragonInt.m3 >> >> Log Message: >> ----------- >> Allocation should be minimum 4 words for 128 bit quads >> >> > (* assume the allocator zeros this array, min size 128 bytes for quads > *) > ----------------------------------------------------------^ bits? > out := NEW(RefInt32,MAX(a.s, 4)); > > > > > > >> Commit: e4b419ae09d819675265f41fc9c354ee645c2c94 >> https://github.com/modula3/cm3/commit/e4b419ae09d819675265f >> 41fc9c354ee645c2c94 >> Author: peter mckinna >> Date: 2016-11-17 (Thu, 17 Nov 2016) >> >> Changed paths: >> A m3-libs/m3core/src/float/Common/FloatUtils.i3 >> A m3-libs/m3core/src/float/Common/FloatUtils.m3 >> A m3-libs/m3core/src/float/Common/TextToFloat.i3 >> A m3-libs/m3core/src/float/Common/TextToFloat.m3 >> M m3-libs/m3core/src/float/Common/m3makefile >> >> Log Message: >> ----------- >> Added floating point conversion functions for 128 quads >> >> >> Compare: https://github.com/modula3/cm3/compare/be8184edff3c...e4b419 >> ae09d8 >> >> > -- > Rodney Bates > rodney.m.bates at acm.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dragisha at m3w.org Wed Nov 23 16:43:48 2016 From: dragisha at m3w.org (=?utf-8?B?RHJhZ2nFoWEgRHVyacSH?=) Date: Wed, 23 Nov 2016 16:43:48 +0100 Subject: [M3devel] Pre-release archives for Raspbian, OSX El Capitan, AMD64 Linux Message-ID: https://github.com/modula3/cm3/releases/tag/d5.10.0-20161121 Hope this helps to people trying to start using cm3. dd -- Dragi?a Duri? dragisha at m3w.org -------------- next part -------------- An HTML attachment was scrubbed... URL: