From rodney.bates at gmx.com Thu Jun 9 19:46:04 2022 From: rodney.bates at gmx.com (Rodney Bates) Date: Thu, 9 Jun 2022 12:46:04 -0500 Subject: [M3devel] [modula3/cm3] Rules on modifying/updating the standard library (interface index) (Issue #1030) In-Reply-To: References: Message-ID: <54b684f0-a7f9-485c-bf8b-964824fb4e4c@gmx.com> This kind of change is welcome.? There has not been a compelling need for strong? gatekeeping here. You probably need someone to give you push access, but I don't know who controls that.??? There is now automatic running of a lot of testing, triggered by a push.? I don't know if it extends to newly created branches.? It? compiles the compiler twice by itself and runs several hundred? tests, so breakage is likely to be found quickly.? Some of the more peripheral code is not tests automatically, especially gui things, but the compiler, main libraries, etc. are. On 6/8/22 23:47, NormHarrison wrote: > > Hi, I came across this project sometime last year, but only began to actually use it over the past few months. I find the state that Critical Mass/Elegosoft left it in upon open sourcing to be quite impressive and complete, though I had a few questions regarding the rules employed on the modules that the project "ships" with. > > For example, I was looking over the interface of Uerror , trying to find if the UNIX |strerror()| function already had a binding. At the bottom of the interface definition, you can see that there is indication of it's presence: > > |<*EXTERNAL*> VAR errno: int; Extension by mjordan CONST Max = ELAST; (* should be exported from Uerror *) <*EXTERNAL*> VAR sys_nerr: int; sys_errlist: ARRAY [0..Max] OF char_star; PROCEDURE GetFrom_sys_errlist(n: INTEGER): char_star RAISES {}; returns entry n of the 'sys_errlist' array; a checked runtime error unless 0 <= n <= sys_nerr. Its safer and more portable to use this procedure than to access the array directly. | > > Though upon looking through the repository and the resulting packages installed with the distribution, it doesn't actually seem to appear (at least) on Linux in the resulting common |Uerror| interface under |pkg/m3core/src/unix/Common/Uerror.i3|. Assuming I haven't missed or misunderstood anything, would it be permitted by the main "overseers" of this repository to update/fix things like this that are part of the core libraries of the project? I assume it likely depends on whether the changes will break existing code etc. I know I can easily bind to this function myself for what I'm trying to do, but since I do care about this project, I wanted to ask how these situations were handled for possible future encounters. > > Thank you > > ? > Reply to this email directly, view it on GitHub , or unsubscribe . > You are receiving this because you are subscribed to this thread.Message ID: > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vvm at tut.by Fri Jun 10 07:45:39 2022 From: vvm at tut.by (vvm at tut.by) Date: Fri, 10 Jun 2022 08:45:39 +0300 Subject: [M3devel] [modula3/cm3] Rules on modifying/updating the standard library (interface index) (Issue #1030) In-Reply-To: <54b684f0-a7f9-485c-bf8b-964824fb4e4c@gmx.com> References: <54b684f0-a7f9-485c-bf8b-964824fb4e4c@gmx.com> Message-ID: <2079471654839610@mail.yandex.by> An HTML attachment was scrubbed... URL: