[M3devel] naming convention unix vs. grumpyunix?

[Jay K]

i.e.:








diff --git a/m3-sys/m3quake/src/M3Path.m3 b/m3-sys/m3quake/src/M3Path.m3
index b3e0f27..1b3ac2c 100644
--- a/m3-sys/m3quake/src/M3Path.m3
+++ b/m3-sys/m3quake/src/M3Path.m3
@@ -22,8 +22,8 @@ TYPE
 
 CONST
   Suffix = ARRAY OSKind OF SMap {
-  (* Unix *)       SMap { "", ".i3", ".ib", ".ic", ".is", ".io",
-                          ".m3", ".mb", ".mc", ".ms", ".mo",
+  (* Unix *)       SMap { "", ".i3", ".ib", ".ic", "_i.s", "_i.o",
+                          ".m3", ".mb", ".mc", "_m.s", "_m.o",
                           ".ig", ".mg", ".c", ".h", ".bc", ".s",
                           ".o", ".a", ".a", ".m3x", "", ".mx", ".tmpl" },
   (* GrumpyUnix *) SMap { "", ".i3", ".ib", ".ic", "_i.s", "_i.o",

full system built on Darwin no problem as I expected.
 - Jay


From: jay.krell at cornell.edu
To: m3devel at elegosoft.com
Subject: naming convention unix vs. grumpyunix?
Date: Mon, 20 Jun 2016 01:40:21 +0000




I propose making unix match grumpyunix and removing grumpyunix.
There is slight upside and should be no downside.
The upside is that various tools -- make and automake -- know that .s is assembly and will assemble it.
Is it a downside for base name to change foo.m3 => foo_m.s/foo_m.o vs. foo.m3 => foo.ms/foo.mo?
I expect everything will just work.
 - Jay



 		 	   		   		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20160620/6b8d52e3/attachment-0002.html>