From mika at async.caltech.edu Sun Nov 16 11:24:53 2014 From: mika at async.caltech.edu (mika at async.caltech.edu) Date: Sun, 16 Nov 2014 02:24:53 -0800 Subject: [M3devel] bug in Fmt.F Message-ID: <20141116102453.1EAE81A208F@async.async.caltech.edu> Fmt.F("%s","X") produces "X" (right) Fmt.F("% %s", "X") produces "% X" (right) Fmt.F("%%s", "X") does not terminate (wrong)--should produce "%X" to produce "%X" workaround is Fmt.F("%s%s", "%", "X") but it really is a bug. Mika From rodney_bates at lcwb.coop Sun Nov 16 20:13:57 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Sun, 16 Nov 2014 13:13:57 -0600 Subject: [M3devel] bug in Fmt.F In-Reply-To: <20141116102453.1EAE81A208F@async.async.caltech.edu> References: <20141116102453.1EAE81A208F@async.async.caltech.edu> Message-ID: <5468F775.1060605@lcwb.coop> By my reading, I can see how this fails. There is an inconsistent invariant in Fmt.ReadSpec. However, by reading, and confirmed by experiment, it should raise Convert.Failed. Is your loop happening outside the call on Fmt.F? On 11/16/2014 04:24 AM, mika at async.caltech.edu wrote: > Fmt.F("%s","X") > > produces "X" (right) > > Fmt.F("% %s", "X") > > produces "% X" (right) > > Fmt.F("%%s", "X") > > does not terminate (wrong)--should produce "%X" > > to produce "%X" workaround is > > Fmt.F("%s%s", "%", "X") > > but it really is a bug. > > Mika > > -- Rodney Bates rodney.m.bates at acm.org From mika at async.caltech.edu Sun Nov 16 20:59:41 2014 From: mika at async.caltech.edu (mika at async.caltech.edu) Date: Sun, 16 Nov 2014 11:59:41 -0800 Subject: [M3devel] bug in Fmt.F In-Reply-To: <5468F775.1060605@lcwb.coop> References: <20141116102453.1EAE81A208F@async.async.caltech.edu> <5468F775.1060605@lcwb.coop> Message-ID: <20141116195941.1C0871A208F@async.async.caltech.edu> Ah, sorry, my choice of words was imprecise. By "does not terminate" I do indeed mean that it raises the exception. I should have written "does not terminate normally, raises an exception" (My runtime turns the uncaught exception into abort, that is, non-termination of the F procedure.) Mika "Rodney M. Bates" writes: >By my reading, I can see how this fails. There is an inconsistent >invariant in Fmt.ReadSpec. However, by reading, and confirmed by experiment, >it should raise Convert.Failed. Is your loop happening outside the call on >Fmt.F? > >On 11/16/2014 04:24 AM, mika at async.caltech.edu wrote: >> Fmt.F("%s","X") >> >> produces "X" (right) >> >> Fmt.F("% %s", "X") >> >> produces "% X" (right) >> >> Fmt.F("%%s", "X") >> >> does not terminate (wrong)--should produce "%X" >> >> to produce "%X" workaround is >> >> Fmt.F("%s%s", "%", "X") >> >> but it really is a bug. >> >> Mika >> >> > >-- >Rodney Bates >rodney.m.bates at acm.org From rodney_bates at lcwb.coop Tue Nov 18 20:00:21 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Tue, 18 Nov 2014 13:00:21 -0600 Subject: [M3devel] Fwd: Re: bug in Fmt.F In-Reply-To: <546A51F7.2000708@lcwb.coop> References: <546A51F7.2000708@lcwb.coop> Message-ID: <546B9745.9010900@lcwb.coop> -------- Original Message -------- Subject: Re: [M3devel] bug in Fmt.F Date: Mon, 17 Nov 2014 13:52:23 -0600 From: Rodney M. Bates Reply-To: rodney.m.bates at acm.org To: m3devel at elegosoft.com Fixed by github commit 53d4f9ad2a63c5dc5df217523bb92bb635a3f17b Also, added a comment in Fmt.i3, which said nothing about incomplete format specifiers. The implementation already attempted to treat them as ordinary characters, but this was incomplete. On 11/16/2014 04:24 AM, mika at async.caltech.edu wrote: > Fmt.F("%s","X") > > produces "X" (right) > > Fmt.F("% %s", "X") > > produces "% X" (right) > > Fmt.F("%%s", "X") > > does not terminate (wrong)--should produce "%X" > > to produce "%X" workaround is > > Fmt.F("%s%s", "%", "X") > > but it really is a bug. > > Mika > > -- Rodney Bates rodney.m.bates at acm.org From rodney_bates at lcwb.coop Tue Nov 18 20:00:59 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Tue, 18 Nov 2014 13:00:59 -0600 Subject: [M3devel] Fwd: Re: bug in Fmt.F -- fixed. In-Reply-To: <546A51F7.2000708@lcwb.coop> References: <546A51F7.2000708@lcwb.coop> Message-ID: <546B976B.7070804@lcwb.coop> -------- Original Message -------- Subject: Re: [M3devel] bug in Fmt.F Date: Mon, 17 Nov 2014 13:52:23 -0600 From: Rodney M. Bates Reply-To: rodney.m.bates at acm.org To: m3devel at elegosoft.com Fixed by github commit 53d4f9ad2a63c5dc5df217523bb92bb635a3f17b Also, added a comment in Fmt.i3, which said nothing about incomplete format specifiers. The implementation already attempted to treat them as ordinary characters, but this was incomplete. On 11/16/2014 04:24 AM, mika at async.caltech.edu wrote: > Fmt.F("%s","X") > > produces "X" (right) > > Fmt.F("% %s", "X") > > produces "% X" (right) > > Fmt.F("%%s", "X") > > does not terminate (wrong)--should produce "%X" > > to produce "%X" workaround is > > Fmt.F("%s%s", "%", "X") > > but it really is a bug. > > Mika > > -- Rodney Bates rodney.m.bates at acm.org From rodney_bates at lcwb.coop Tue Nov 18 20:06:48 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Tue, 18 Nov 2014 13:06:48 -0600 Subject: [M3devel] Fwd: github rename question In-Reply-To: <546A54A2.20305@lcwb.coop> References: <546A54A2.20305@lcwb.coop> Message-ID: <546B98C8.60400@lcwb.coop> Is https://github.com/modula3/cm3 just a rename of https://github.com/dragisha/cm3? Or a different repository? I seem to have the latter name stored somewhere in my local repository, as its origin, and am seeing worrisome messages about the different names. I did a fetch and merge in my local repo, which appeared to work as expected, but said it was merging from dragisha. Then at the end, it told me the name had changed. Later, I did a push, with several local commits waiting. Now, github shows _my_ merge as a commit in _its_ repo, which seems very odd. Could this have backdated things to an outdated repo? -- Rodney Bates rodney.m.bates at acm.org From rodney_bates at lcwb.coop Wed Nov 19 19:28:07 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Wed, 19 Nov 2014 12:28:07 -0600 Subject: [M3devel] Fwd: Re: github rename question In-Reply-To: <546CB72C.5020800@lcwb.coop> References: <546CB72C.5020800@lcwb.coop> Message-ID: <546CE137.1060200@lcwb.coop> -------- Original Message -------- Subject: Re: [M3devel] github rename question Date: Wed, 19 Nov 2014 09:28:44 -0600 From: Rodney M. Bates Reply-To: rodney.m.bates at acm.org To: Antony Hosking CC: m3devel , Dragi?a Duri? On 11/18/2014 01:57 PM, Antony Hosking wrote: > Scratch that. > It looks like the right code is there. > I think you did the same as I was doing before I got a fresh clone, in which a merge event ends up in the history. > I?m hoping Dragisha or someone can let us know how to fix it. This seems very confusing to me. I have only cloned once, and it would have been github.com/dragisha/cm3. This is apparently stored locally, though I don't know how to find and change it: ------------------------------------------------------------------------------------- rodney at allegheny:~/proj/m3/git/cm3$ git config -l user.name=Rodney Bates user.email=rodney.m.bates at acm.org credential.helper=cache --timeout=40000 core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true remote.origin.url=https://github.com/dragisha/cm3.git ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* branch.master.remote=origin branch.master.merge=refs/heads/master rodney at allegheny:~/proj/m3/git/cm3$ ------------------------------------------------------------------------------------- My pull command didn't name the repository explicitly, and it tells me it did the pull from what I had cloned: ------------------------------------------------------------------------------------- rodney at allegheny:~/proj/m3/git/cm3$ git pull From https://github.com/dragisha/cm3 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + d97d794...554adee master -> origin/master (forced update) fab06be..626f74c trunk -> origin/trunk * [new tag] verification-release-mavericks -> verification-release-mavericks Merge made by the 'recursive' strategy. .gitignore | 1 + m3-libs/m3core/src/Csupport/m3makefile | 4 ---- m3-libs/m3core/src/m3core.h | 4 ++++ m3-libs/m3core/src/thread/PTHREAD/ThreadApple.c | 6 +++--- m3-libs/m3core/src/thread/PTHREAD/ThreadPThread.i3 | 2 +- m3-libs/m3core/src/thread/PTHREAD/ThreadPThread.m3 | 58 ++++++++++++++++++++++++++-------------------------------- m3-libs/m3core/src/thread/PTHREAD/ThreadPThreadC.c | 24 +++++++++++++++++++++++- m3-sys/cminstall/src/config-no-install/AMD64_DARWIN | 4 ++++ m3-sys/cminstall/src/config-no-install/Darwin.common | 2 +- m3-sys/m3cc/gcc/gcc/m3cg/parse.c | 6 +++--- scripts/make-bin-dist-min.sh | 8 +++++--- 11 files changed, 71 insertions(+), 48 deletions(-) create mode 100644 .gitignore ------------------------------------------------------------------------------------- But when I did my push, it somehow knew that github.com/modula3/cm3 was involved in some way. But what did it actually do? And when should I add the ".git" at the end of the URL and when not? ------------------------------------------------------------------------------------- rodney at allegheny:~/proj/m3/git/cm3$ git push origin master Username for 'https://github.com': RodneyBates Password for 'https://RodneyBates at github.com': Counting objects: 3327, done. Delta compression using up to 4 threads. Compressing objects: 100% (677/677), done. Writing objects: 100% (2524/2524), 342.06 KiB | 0 bytes/s, done. Total 2524 (delta 2065), reused 2244 (delta 1820) remote: This repository moved. Please use the new location: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ remote: https://github.com/modula3/cm3.git ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ To https://github.com/dragisha/cm3.git ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 554adee..7a2dd48 master -> master rodney at allegheny:~/proj/m3/git/cm3$ ------------------------------------------------------------------------------------- If I do a fresh clone of github.com/modula3/cm3, I will no doubt have to manually locate and copy my not-yet-added/committed edits into it. ------------------------------------------------------------------------------------- rodney at allegheny:~/proj/m3/git/cm3$ git status # On branch master # Your branch is ahead of 'origin/master' by 8543 commits. # (use "git push" to publish your local commits) # # Changes not staged for commit: # (use "git add/rm ..." to update what will be committed) # (use "git checkout -- ..." to discard changes in working directory) # # modified: m3-libs/libm3/src/rw/Wr.i3 # modified: m3-libs/libm3/tests/fmtlex/fmt/src/Makefile # modified: m3-libs/libm3/tests/fmtlex/fmt/src/m3makefile # modified: m3-libs/libm3/tests/fmtlex/fmt/src/run-tests # modified: m3-libs/libunicode/src/UniWr.m3 # modified: m3-libs/libunicode/src/UnsafeUniWr.m3 # modified: m3-libs/m3core/src/text/Text.i3 # modified: m3-libs/ordsets/ordsets/src/OrdSets.mg # modified: m3-sys/cm3/src/Builder.m3 # deleted: m3-sys/m3gdb/gdb/bfd/doc/bfd.info # modified: scripts/pkginfo.txt # # Untracked files: # (use "git add ..." to include in what will be committed) # (snip: ...... Lots of irrelevant stuff, including build directories, etc. ) # It took 2.29 seconds to enumerate untracked files. 'status -uno' # may speed it up, but you have to be careful not to forget to add # new files yourself (see 'git help status'). no changes added to commit (use "git add" and/or "git commit -a") rodney at allegheny:~/proj/m3/git/cm3$ ------------------------------------------------------------------------------------- > >> On Nov 18, 2014, at 2:42 PM, Antony Hosking wrote: >> >> It looks like your commit backdated to old code. >> I see reversions of the thread fixes I made a few months back. >> >> Can anyone help Rodney undo? >> I?d try, but my git foo is pretty weak. >> >>> On Nov 18, 2014, at 2:35 PM, Antony Hosking wrote: >>> >>> I had a similar problem because I was using an outdated clone. >>> I don?t recall what the fix was. Can someone out there help? >>> >>> But what you need to do is to reclone form https://github.com/modula3/cm3 and make sure to use that in future. >>> >>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>> 305 N. University Street | West Lafayette | IN 47907 | USA >>> Mobile +1 765 427 5484 >>> >>> >>> >>>> On Nov 18, 2014, at 2:30 PM, Antony Hosking wrote: >>>> >>>> PS https://github.com/modula3/cm3 >>>> >>>> dragisha is a different repo! >>>> >>>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>>> 305 N. University Street | West Lafayette | IN 47907 | USA >>>> Mobile +1 765 427 5484 >>>> >>>> >>>> >>>>> On Nov 18, 2014, at 2:06 PM, Rodney M. Bates wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Is https://github.com/modula3/cm3 just a rename of https://github.com/dragisha/cm3? >>>>> Or a different repository? I seem to have the latter name stored somewhere in my local >>>>> repository, as its origin, and am seeing worrisome messages about the different names. >>>>> >>>>> I did a fetch and merge in my local repo, which appeared to work as expected, but said >>>>> it was merging from dragisha. Then at the end, it told me the name had changed. Later, >>>>> I did a push, with several local commits waiting. Now, github shows _my_ merge as a >>>>> commit in _its_ repo, which seems very odd. Could this have backdated things to >>>>> an outdated repo? >>>>> >>>>> >>>>> >>>>> -- >>>>> Rodney Bates >>>>> rodney.m.bates at acm.org >>>>> >>>>> >>>> >>> >> > > -- Rodney Bates rodney.m.bates at acm.org From dragisha at m3w.org Thu Nov 27 21:59:36 2014 From: dragisha at m3w.org (=?utf-8?Q?Dragi=C5=A1a_Duri=C4=87?=) Date: Thu, 27 Nov 2014 21:59:36 +0100 Subject: [M3devel] github rename question In-Reply-To: <1D721A55-5B88-4DC8-910A-956986BA65BF@purdue.edu> References: <546A54A2.20305@lcwb.coop> <546B98C8.60400@lcwb.coop> <5E7FECCE-4BE0-4C9E-AA7E-36AC60804B42@purdue.edu> <41383B6E-F532-4FA7-BE5D-A44712E7CADA@purdue.edu> <1D721A55-5B88-4DC8-910A-956986BA65BF@purdue.edu> Message-ID: <8F3CEEE0-475E-46BA-85B9-8FE5F4FA663C@m3w.org> Hi, I am reading through repo but I don?t see a problem (end of day and all?). Can somebody point me in right direction? I had problem accessing to repo, 403 Forbidden something. Somehow, my 2010 MBP had git binary 1.6.1 from Jan 2009 in /usr/local/bin :). OSX Yosemite git is 1.9.x, though. Access works. (just a hint to anybody else meeting similar 403 problem:) dd > On 18 Nov 2014, at 20:57, Antony Hosking wrote: > > Scratch that. > It looks like the right code is there. > I think you did the same as I was doing before I got a fresh clone, in which a merge event ends up in the history. > I?m hoping Dragisha or someone can let us know how to fix it. > >> On Nov 18, 2014, at 2:42 PM, Antony Hosking wrote: >> >> It looks like your commit backdated to old code. >> I see reversions of the thread fixes I made a few months back. >> >> Can anyone help Rodney undo? >> I?d try, but my git foo is pretty weak. >> >>> On Nov 18, 2014, at 2:35 PM, Antony Hosking wrote: >>> >>> I had a similar problem because I was using an outdated clone. >>> I don?t recall what the fix was. Can someone out there help? >>> >>> But what you need to do is to reclone form https://github.com/modula3/cm3 and make sure to use that in future. >>> >>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>> 305 N. University Street | West Lafayette | IN 47907 | USA >>> Mobile +1 765 427 5484 >>> >>> >>> >>>> On Nov 18, 2014, at 2:30 PM, Antony Hosking wrote: >>>> >>>> PS https://github.com/modula3/cm3 >>>> >>>> dragisha is a different repo! >>>> >>>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>>> 305 N. University Street | West Lafayette | IN 47907 | USA >>>> Mobile +1 765 427 5484 >>>> >>>> >>>> >>>>> On Nov 18, 2014, at 2:06 PM, Rodney M. Bates wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Is https://github.com/modula3/cm3 just a rename of https://github.com/dragisha/cm3? >>>>> Or a different repository? I seem to have the latter name stored somewhere in my local >>>>> repository, as its origin, and am seeing worrisome messages about the different names. >>>>> >>>>> I did a fetch and merge in my local repo, which appeared to work as expected, but said >>>>> it was merging from dragisha. Then at the end, it told me the name had changed. Later, >>>>> I did a push, with several local commits waiting. Now, github shows _my_ merge as a >>>>> commit in _its_ repo, which seems very odd. Could this have backdated things to >>>>> an outdated repo? >>>>> >>>>> >>>>> >>>>> -- >>>>> Rodney Bates >>>>> rodney.m.bates at acm.org >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 495 bytes Desc: Message signed with OpenPGP using GPGMail URL: From rodney_bates at lcwb.coop Sat Nov 29 00:27:40 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Fri, 28 Nov 2014 17:27:40 -0600 Subject: [M3devel] github rename question In-Reply-To: <8F3CEEE0-475E-46BA-85B9-8FE5F4FA663C@m3w.org> References: <546A54A2.20305@lcwb.coop> <546B98C8.60400@lcwb.coop> <5E7FECCE-4BE0-4C9E-AA7E-36AC60804B42@purdue.edu> <41383B6E-F532-4FA7-BE5D-A44712E7CADA@purdue.edu> <1D721A55-5B88-4DC8-910A-956986BA65BF@purdue.edu> <8F3CEEE0-475E-46BA-85B9-8FE5F4FA663C@m3w.org> Message-ID: <547904EC.4020807@lcwb.coop> From a combination of reading github documentation pages and a couple of experiments, I am pretty well convinced that the two github repository URLs I was worried about are just pointers to the same repo. I also successfully changed the URL my local repo has stored as the 'origin' repo to the new one, so now it doesn't nag or worry me when I do pulls or pushes. I still can't supply an explicit URL to any git command to name the remote repo. They all either give error messages or do apparently nothing. On 11/27/2014 02:59 PM, Dragi?a Duri? wrote: > Hi, > > I am reading through repo but I don?t see a problem (end of day and all?). Can somebody point me in right direction? > > I had problem accessing to repo, 403 Forbidden something. Somehow, my 2010 MBP had git binary 1.6.1 from Jan 2009 in /usr/local/bin :). OSX Yosemite git is 1.9.x, though. Access works. (just a hint to anybody else meeting similar 403 problem:) > > dd > >> On 18 Nov 2014, at 20:57, Antony Hosking wrote: >> >> Scratch that. >> It looks like the right code is there. >> I think you did the same as I was doing before I got a fresh clone, in which a merge event ends up in the history. >> I?m hoping Dragisha or someone can let us know how to fix it. >> >>> On Nov 18, 2014, at 2:42 PM, Antony Hosking wrote: >>> >>> It looks like your commit backdated to old code. >>> I see reversions of the thread fixes I made a few months back. >>> >>> Can anyone help Rodney undo? >>> I?d try, but my git foo is pretty weak. >>> >>>> On Nov 18, 2014, at 2:35 PM, Antony Hosking wrote: >>>> >>>> I had a similar problem because I was using an outdated clone. >>>> I don?t recall what the fix was. Can someone out there help? >>>> >>>> But what you need to do is to reclone form https://github.com/modula3/cm3 and make sure to use that in future. >>>> >>>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>>> 305 N. University Street | West Lafayette | IN 47907 | USA >>>> Mobile +1 765 427 5484 >>>> >>>> >>>> >>>>> On Nov 18, 2014, at 2:30 PM, Antony Hosking wrote: >>>>> >>>>> PS https://github.com/modula3/cm3 >>>>> >>>>> dragisha is a different repo! >>>>> >>>>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>>>> 305 N. University Street | West Lafayette | IN 47907 | USA >>>>> Mobile +1 765 427 5484 >>>>> >>>>> >>>>> >>>>>> On Nov 18, 2014, at 2:06 PM, Rodney M. Bates wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Is https://github.com/modula3/cm3 just a rename of https://github.com/dragisha/cm3? >>>>>> Or a different repository? I seem to have the latter name stored somewhere in my local >>>>>> repository, as its origin, and am seeing worrisome messages about the different names. >>>>>> >>>>>> I did a fetch and merge in my local repo, which appeared to work as expected, but said >>>>>> it was merging from dragisha. Then at the end, it told me the name had changed. Later, >>>>>> I did a push, with several local commits waiting. Now, github shows _my_ merge as a >>>>>> commit in _its_ repo, which seems very odd. Could this have backdated things to >>>>>> an outdated repo? >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Rodney Bates >>>>>> rodney.m.bates at acm.org >>>>>> >>>>>> >>>>> >>>> >>> >> > -- Rodney Bates rodney.m.bates at acm.org From mika at async.caltech.edu Sun Nov 16 11:24:53 2014 From: mika at async.caltech.edu (mika at async.caltech.edu) Date: Sun, 16 Nov 2014 02:24:53 -0800 Subject: [M3devel] bug in Fmt.F Message-ID: <20141116102453.1EAE81A208F@async.async.caltech.edu> Fmt.F("%s","X") produces "X" (right) Fmt.F("% %s", "X") produces "% X" (right) Fmt.F("%%s", "X") does not terminate (wrong)--should produce "%X" to produce "%X" workaround is Fmt.F("%s%s", "%", "X") but it really is a bug. Mika From rodney_bates at lcwb.coop Sun Nov 16 20:13:57 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Sun, 16 Nov 2014 13:13:57 -0600 Subject: [M3devel] bug in Fmt.F In-Reply-To: <20141116102453.1EAE81A208F@async.async.caltech.edu> References: <20141116102453.1EAE81A208F@async.async.caltech.edu> Message-ID: <5468F775.1060605@lcwb.coop> By my reading, I can see how this fails. There is an inconsistent invariant in Fmt.ReadSpec. However, by reading, and confirmed by experiment, it should raise Convert.Failed. Is your loop happening outside the call on Fmt.F? On 11/16/2014 04:24 AM, mika at async.caltech.edu wrote: > Fmt.F("%s","X") > > produces "X" (right) > > Fmt.F("% %s", "X") > > produces "% X" (right) > > Fmt.F("%%s", "X") > > does not terminate (wrong)--should produce "%X" > > to produce "%X" workaround is > > Fmt.F("%s%s", "%", "X") > > but it really is a bug. > > Mika > > -- Rodney Bates rodney.m.bates at acm.org From mika at async.caltech.edu Sun Nov 16 20:59:41 2014 From: mika at async.caltech.edu (mika at async.caltech.edu) Date: Sun, 16 Nov 2014 11:59:41 -0800 Subject: [M3devel] bug in Fmt.F In-Reply-To: <5468F775.1060605@lcwb.coop> References: <20141116102453.1EAE81A208F@async.async.caltech.edu> <5468F775.1060605@lcwb.coop> Message-ID: <20141116195941.1C0871A208F@async.async.caltech.edu> Ah, sorry, my choice of words was imprecise. By "does not terminate" I do indeed mean that it raises the exception. I should have written "does not terminate normally, raises an exception" (My runtime turns the uncaught exception into abort, that is, non-termination of the F procedure.) Mika "Rodney M. Bates" writes: >By my reading, I can see how this fails. There is an inconsistent >invariant in Fmt.ReadSpec. However, by reading, and confirmed by experiment, >it should raise Convert.Failed. Is your loop happening outside the call on >Fmt.F? > >On 11/16/2014 04:24 AM, mika at async.caltech.edu wrote: >> Fmt.F("%s","X") >> >> produces "X" (right) >> >> Fmt.F("% %s", "X") >> >> produces "% X" (right) >> >> Fmt.F("%%s", "X") >> >> does not terminate (wrong)--should produce "%X" >> >> to produce "%X" workaround is >> >> Fmt.F("%s%s", "%", "X") >> >> but it really is a bug. >> >> Mika >> >> > >-- >Rodney Bates >rodney.m.bates at acm.org From rodney_bates at lcwb.coop Tue Nov 18 20:00:21 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Tue, 18 Nov 2014 13:00:21 -0600 Subject: [M3devel] Fwd: Re: bug in Fmt.F In-Reply-To: <546A51F7.2000708@lcwb.coop> References: <546A51F7.2000708@lcwb.coop> Message-ID: <546B9745.9010900@lcwb.coop> -------- Original Message -------- Subject: Re: [M3devel] bug in Fmt.F Date: Mon, 17 Nov 2014 13:52:23 -0600 From: Rodney M. Bates Reply-To: rodney.m.bates at acm.org To: m3devel at elegosoft.com Fixed by github commit 53d4f9ad2a63c5dc5df217523bb92bb635a3f17b Also, added a comment in Fmt.i3, which said nothing about incomplete format specifiers. The implementation already attempted to treat them as ordinary characters, but this was incomplete. On 11/16/2014 04:24 AM, mika at async.caltech.edu wrote: > Fmt.F("%s","X") > > produces "X" (right) > > Fmt.F("% %s", "X") > > produces "% X" (right) > > Fmt.F("%%s", "X") > > does not terminate (wrong)--should produce "%X" > > to produce "%X" workaround is > > Fmt.F("%s%s", "%", "X") > > but it really is a bug. > > Mika > > -- Rodney Bates rodney.m.bates at acm.org From rodney_bates at lcwb.coop Tue Nov 18 20:00:59 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Tue, 18 Nov 2014 13:00:59 -0600 Subject: [M3devel] Fwd: Re: bug in Fmt.F -- fixed. In-Reply-To: <546A51F7.2000708@lcwb.coop> References: <546A51F7.2000708@lcwb.coop> Message-ID: <546B976B.7070804@lcwb.coop> -------- Original Message -------- Subject: Re: [M3devel] bug in Fmt.F Date: Mon, 17 Nov 2014 13:52:23 -0600 From: Rodney M. Bates Reply-To: rodney.m.bates at acm.org To: m3devel at elegosoft.com Fixed by github commit 53d4f9ad2a63c5dc5df217523bb92bb635a3f17b Also, added a comment in Fmt.i3, which said nothing about incomplete format specifiers. The implementation already attempted to treat them as ordinary characters, but this was incomplete. On 11/16/2014 04:24 AM, mika at async.caltech.edu wrote: > Fmt.F("%s","X") > > produces "X" (right) > > Fmt.F("% %s", "X") > > produces "% X" (right) > > Fmt.F("%%s", "X") > > does not terminate (wrong)--should produce "%X" > > to produce "%X" workaround is > > Fmt.F("%s%s", "%", "X") > > but it really is a bug. > > Mika > > -- Rodney Bates rodney.m.bates at acm.org From rodney_bates at lcwb.coop Tue Nov 18 20:06:48 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Tue, 18 Nov 2014 13:06:48 -0600 Subject: [M3devel] Fwd: github rename question In-Reply-To: <546A54A2.20305@lcwb.coop> References: <546A54A2.20305@lcwb.coop> Message-ID: <546B98C8.60400@lcwb.coop> Is https://github.com/modula3/cm3 just a rename of https://github.com/dragisha/cm3? Or a different repository? I seem to have the latter name stored somewhere in my local repository, as its origin, and am seeing worrisome messages about the different names. I did a fetch and merge in my local repo, which appeared to work as expected, but said it was merging from dragisha. Then at the end, it told me the name had changed. Later, I did a push, with several local commits waiting. Now, github shows _my_ merge as a commit in _its_ repo, which seems very odd. Could this have backdated things to an outdated repo? -- Rodney Bates rodney.m.bates at acm.org From rodney_bates at lcwb.coop Wed Nov 19 19:28:07 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Wed, 19 Nov 2014 12:28:07 -0600 Subject: [M3devel] Fwd: Re: github rename question In-Reply-To: <546CB72C.5020800@lcwb.coop> References: <546CB72C.5020800@lcwb.coop> Message-ID: <546CE137.1060200@lcwb.coop> -------- Original Message -------- Subject: Re: [M3devel] github rename question Date: Wed, 19 Nov 2014 09:28:44 -0600 From: Rodney M. Bates Reply-To: rodney.m.bates at acm.org To: Antony Hosking CC: m3devel , Dragi?a Duri? On 11/18/2014 01:57 PM, Antony Hosking wrote: > Scratch that. > It looks like the right code is there. > I think you did the same as I was doing before I got a fresh clone, in which a merge event ends up in the history. > I?m hoping Dragisha or someone can let us know how to fix it. This seems very confusing to me. I have only cloned once, and it would have been github.com/dragisha/cm3. This is apparently stored locally, though I don't know how to find and change it: ------------------------------------------------------------------------------------- rodney at allegheny:~/proj/m3/git/cm3$ git config -l user.name=Rodney Bates user.email=rodney.m.bates at acm.org credential.helper=cache --timeout=40000 core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true remote.origin.url=https://github.com/dragisha/cm3.git ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* branch.master.remote=origin branch.master.merge=refs/heads/master rodney at allegheny:~/proj/m3/git/cm3$ ------------------------------------------------------------------------------------- My pull command didn't name the repository explicitly, and it tells me it did the pull from what I had cloned: ------------------------------------------------------------------------------------- rodney at allegheny:~/proj/m3/git/cm3$ git pull From https://github.com/dragisha/cm3 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + d97d794...554adee master -> origin/master (forced update) fab06be..626f74c trunk -> origin/trunk * [new tag] verification-release-mavericks -> verification-release-mavericks Merge made by the 'recursive' strategy. .gitignore | 1 + m3-libs/m3core/src/Csupport/m3makefile | 4 ---- m3-libs/m3core/src/m3core.h | 4 ++++ m3-libs/m3core/src/thread/PTHREAD/ThreadApple.c | 6 +++--- m3-libs/m3core/src/thread/PTHREAD/ThreadPThread.i3 | 2 +- m3-libs/m3core/src/thread/PTHREAD/ThreadPThread.m3 | 58 ++++++++++++++++++++++++++-------------------------------- m3-libs/m3core/src/thread/PTHREAD/ThreadPThreadC.c | 24 +++++++++++++++++++++++- m3-sys/cminstall/src/config-no-install/AMD64_DARWIN | 4 ++++ m3-sys/cminstall/src/config-no-install/Darwin.common | 2 +- m3-sys/m3cc/gcc/gcc/m3cg/parse.c | 6 +++--- scripts/make-bin-dist-min.sh | 8 +++++--- 11 files changed, 71 insertions(+), 48 deletions(-) create mode 100644 .gitignore ------------------------------------------------------------------------------------- But when I did my push, it somehow knew that github.com/modula3/cm3 was involved in some way. But what did it actually do? And when should I add the ".git" at the end of the URL and when not? ------------------------------------------------------------------------------------- rodney at allegheny:~/proj/m3/git/cm3$ git push origin master Username for 'https://github.com': RodneyBates Password for 'https://RodneyBates at github.com': Counting objects: 3327, done. Delta compression using up to 4 threads. Compressing objects: 100% (677/677), done. Writing objects: 100% (2524/2524), 342.06 KiB | 0 bytes/s, done. Total 2524 (delta 2065), reused 2244 (delta 1820) remote: This repository moved. Please use the new location: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ remote: https://github.com/modula3/cm3.git ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ To https://github.com/dragisha/cm3.git ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 554adee..7a2dd48 master -> master rodney at allegheny:~/proj/m3/git/cm3$ ------------------------------------------------------------------------------------- If I do a fresh clone of github.com/modula3/cm3, I will no doubt have to manually locate and copy my not-yet-added/committed edits into it. ------------------------------------------------------------------------------------- rodney at allegheny:~/proj/m3/git/cm3$ git status # On branch master # Your branch is ahead of 'origin/master' by 8543 commits. # (use "git push" to publish your local commits) # # Changes not staged for commit: # (use "git add/rm ..." to update what will be committed) # (use "git checkout -- ..." to discard changes in working directory) # # modified: m3-libs/libm3/src/rw/Wr.i3 # modified: m3-libs/libm3/tests/fmtlex/fmt/src/Makefile # modified: m3-libs/libm3/tests/fmtlex/fmt/src/m3makefile # modified: m3-libs/libm3/tests/fmtlex/fmt/src/run-tests # modified: m3-libs/libunicode/src/UniWr.m3 # modified: m3-libs/libunicode/src/UnsafeUniWr.m3 # modified: m3-libs/m3core/src/text/Text.i3 # modified: m3-libs/ordsets/ordsets/src/OrdSets.mg # modified: m3-sys/cm3/src/Builder.m3 # deleted: m3-sys/m3gdb/gdb/bfd/doc/bfd.info # modified: scripts/pkginfo.txt # # Untracked files: # (use "git add ..." to include in what will be committed) # (snip: ...... Lots of irrelevant stuff, including build directories, etc. ) # It took 2.29 seconds to enumerate untracked files. 'status -uno' # may speed it up, but you have to be careful not to forget to add # new files yourself (see 'git help status'). no changes added to commit (use "git add" and/or "git commit -a") rodney at allegheny:~/proj/m3/git/cm3$ ------------------------------------------------------------------------------------- > >> On Nov 18, 2014, at 2:42 PM, Antony Hosking wrote: >> >> It looks like your commit backdated to old code. >> I see reversions of the thread fixes I made a few months back. >> >> Can anyone help Rodney undo? >> I?d try, but my git foo is pretty weak. >> >>> On Nov 18, 2014, at 2:35 PM, Antony Hosking wrote: >>> >>> I had a similar problem because I was using an outdated clone. >>> I don?t recall what the fix was. Can someone out there help? >>> >>> But what you need to do is to reclone form https://github.com/modula3/cm3 and make sure to use that in future. >>> >>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>> 305 N. University Street | West Lafayette | IN 47907 | USA >>> Mobile +1 765 427 5484 >>> >>> >>> >>>> On Nov 18, 2014, at 2:30 PM, Antony Hosking wrote: >>>> >>>> PS https://github.com/modula3/cm3 >>>> >>>> dragisha is a different repo! >>>> >>>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>>> 305 N. University Street | West Lafayette | IN 47907 | USA >>>> Mobile +1 765 427 5484 >>>> >>>> >>>> >>>>> On Nov 18, 2014, at 2:06 PM, Rodney M. Bates wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Is https://github.com/modula3/cm3 just a rename of https://github.com/dragisha/cm3? >>>>> Or a different repository? I seem to have the latter name stored somewhere in my local >>>>> repository, as its origin, and am seeing worrisome messages about the different names. >>>>> >>>>> I did a fetch and merge in my local repo, which appeared to work as expected, but said >>>>> it was merging from dragisha. Then at the end, it told me the name had changed. Later, >>>>> I did a push, with several local commits waiting. Now, github shows _my_ merge as a >>>>> commit in _its_ repo, which seems very odd. Could this have backdated things to >>>>> an outdated repo? >>>>> >>>>> >>>>> >>>>> -- >>>>> Rodney Bates >>>>> rodney.m.bates at acm.org >>>>> >>>>> >>>> >>> >> > > -- Rodney Bates rodney.m.bates at acm.org From dragisha at m3w.org Thu Nov 27 21:59:36 2014 From: dragisha at m3w.org (=?utf-8?Q?Dragi=C5=A1a_Duri=C4=87?=) Date: Thu, 27 Nov 2014 21:59:36 +0100 Subject: [M3devel] github rename question In-Reply-To: <1D721A55-5B88-4DC8-910A-956986BA65BF@purdue.edu> References: <546A54A2.20305@lcwb.coop> <546B98C8.60400@lcwb.coop> <5E7FECCE-4BE0-4C9E-AA7E-36AC60804B42@purdue.edu> <41383B6E-F532-4FA7-BE5D-A44712E7CADA@purdue.edu> <1D721A55-5B88-4DC8-910A-956986BA65BF@purdue.edu> Message-ID: <8F3CEEE0-475E-46BA-85B9-8FE5F4FA663C@m3w.org> Hi, I am reading through repo but I don?t see a problem (end of day and all?). Can somebody point me in right direction? I had problem accessing to repo, 403 Forbidden something. Somehow, my 2010 MBP had git binary 1.6.1 from Jan 2009 in /usr/local/bin :). OSX Yosemite git is 1.9.x, though. Access works. (just a hint to anybody else meeting similar 403 problem:) dd > On 18 Nov 2014, at 20:57, Antony Hosking wrote: > > Scratch that. > It looks like the right code is there. > I think you did the same as I was doing before I got a fresh clone, in which a merge event ends up in the history. > I?m hoping Dragisha or someone can let us know how to fix it. > >> On Nov 18, 2014, at 2:42 PM, Antony Hosking wrote: >> >> It looks like your commit backdated to old code. >> I see reversions of the thread fixes I made a few months back. >> >> Can anyone help Rodney undo? >> I?d try, but my git foo is pretty weak. >> >>> On Nov 18, 2014, at 2:35 PM, Antony Hosking wrote: >>> >>> I had a similar problem because I was using an outdated clone. >>> I don?t recall what the fix was. Can someone out there help? >>> >>> But what you need to do is to reclone form https://github.com/modula3/cm3 and make sure to use that in future. >>> >>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>> 305 N. University Street | West Lafayette | IN 47907 | USA >>> Mobile +1 765 427 5484 >>> >>> >>> >>>> On Nov 18, 2014, at 2:30 PM, Antony Hosking wrote: >>>> >>>> PS https://github.com/modula3/cm3 >>>> >>>> dragisha is a different repo! >>>> >>>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>>> 305 N. University Street | West Lafayette | IN 47907 | USA >>>> Mobile +1 765 427 5484 >>>> >>>> >>>> >>>>> On Nov 18, 2014, at 2:06 PM, Rodney M. Bates wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Is https://github.com/modula3/cm3 just a rename of https://github.com/dragisha/cm3? >>>>> Or a different repository? I seem to have the latter name stored somewhere in my local >>>>> repository, as its origin, and am seeing worrisome messages about the different names. >>>>> >>>>> I did a fetch and merge in my local repo, which appeared to work as expected, but said >>>>> it was merging from dragisha. Then at the end, it told me the name had changed. Later, >>>>> I did a push, with several local commits waiting. Now, github shows _my_ merge as a >>>>> commit in _its_ repo, which seems very odd. Could this have backdated things to >>>>> an outdated repo? >>>>> >>>>> >>>>> >>>>> -- >>>>> Rodney Bates >>>>> rodney.m.bates at acm.org >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 495 bytes Desc: Message signed with OpenPGP using GPGMail URL: From rodney_bates at lcwb.coop Sat Nov 29 00:27:40 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Fri, 28 Nov 2014 17:27:40 -0600 Subject: [M3devel] github rename question In-Reply-To: <8F3CEEE0-475E-46BA-85B9-8FE5F4FA663C@m3w.org> References: <546A54A2.20305@lcwb.coop> <546B98C8.60400@lcwb.coop> <5E7FECCE-4BE0-4C9E-AA7E-36AC60804B42@purdue.edu> <41383B6E-F532-4FA7-BE5D-A44712E7CADA@purdue.edu> <1D721A55-5B88-4DC8-910A-956986BA65BF@purdue.edu> <8F3CEEE0-475E-46BA-85B9-8FE5F4FA663C@m3w.org> Message-ID: <547904EC.4020807@lcwb.coop> From a combination of reading github documentation pages and a couple of experiments, I am pretty well convinced that the two github repository URLs I was worried about are just pointers to the same repo. I also successfully changed the URL my local repo has stored as the 'origin' repo to the new one, so now it doesn't nag or worry me when I do pulls or pushes. I still can't supply an explicit URL to any git command to name the remote repo. They all either give error messages or do apparently nothing. On 11/27/2014 02:59 PM, Dragi?a Duri? wrote: > Hi, > > I am reading through repo but I don?t see a problem (end of day and all?). Can somebody point me in right direction? > > I had problem accessing to repo, 403 Forbidden something. Somehow, my 2010 MBP had git binary 1.6.1 from Jan 2009 in /usr/local/bin :). OSX Yosemite git is 1.9.x, though. Access works. (just a hint to anybody else meeting similar 403 problem:) > > dd > >> On 18 Nov 2014, at 20:57, Antony Hosking wrote: >> >> Scratch that. >> It looks like the right code is there. >> I think you did the same as I was doing before I got a fresh clone, in which a merge event ends up in the history. >> I?m hoping Dragisha or someone can let us know how to fix it. >> >>> On Nov 18, 2014, at 2:42 PM, Antony Hosking wrote: >>> >>> It looks like your commit backdated to old code. >>> I see reversions of the thread fixes I made a few months back. >>> >>> Can anyone help Rodney undo? >>> I?d try, but my git foo is pretty weak. >>> >>>> On Nov 18, 2014, at 2:35 PM, Antony Hosking wrote: >>>> >>>> I had a similar problem because I was using an outdated clone. >>>> I don?t recall what the fix was. Can someone out there help? >>>> >>>> But what you need to do is to reclone form https://github.com/modula3/cm3 and make sure to use that in future. >>>> >>>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>>> 305 N. University Street | West Lafayette | IN 47907 | USA >>>> Mobile +1 765 427 5484 >>>> >>>> >>>> >>>>> On Nov 18, 2014, at 2:30 PM, Antony Hosking wrote: >>>>> >>>>> PS https://github.com/modula3/cm3 >>>>> >>>>> dragisha is a different repo! >>>>> >>>>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>>>> 305 N. University Street | West Lafayette | IN 47907 | USA >>>>> Mobile +1 765 427 5484 >>>>> >>>>> >>>>> >>>>>> On Nov 18, 2014, at 2:06 PM, Rodney M. Bates wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Is https://github.com/modula3/cm3 just a rename of https://github.com/dragisha/cm3? >>>>>> Or a different repository? I seem to have the latter name stored somewhere in my local >>>>>> repository, as its origin, and am seeing worrisome messages about the different names. >>>>>> >>>>>> I did a fetch and merge in my local repo, which appeared to work as expected, but said >>>>>> it was merging from dragisha. Then at the end, it told me the name had changed. Later, >>>>>> I did a push, with several local commits waiting. Now, github shows _my_ merge as a >>>>>> commit in _its_ repo, which seems very odd. Could this have backdated things to >>>>>> an outdated repo? >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Rodney Bates >>>>>> rodney.m.bates at acm.org >>>>>> >>>>>> >>>>> >>>> >>> >> > -- Rodney Bates rodney.m.bates at acm.org From mika at async.caltech.edu Sun Nov 16 11:24:53 2014 From: mika at async.caltech.edu (mika at async.caltech.edu) Date: Sun, 16 Nov 2014 02:24:53 -0800 Subject: [M3devel] bug in Fmt.F Message-ID: <20141116102453.1EAE81A208F@async.async.caltech.edu> Fmt.F("%s","X") produces "X" (right) Fmt.F("% %s", "X") produces "% X" (right) Fmt.F("%%s", "X") does not terminate (wrong)--should produce "%X" to produce "%X" workaround is Fmt.F("%s%s", "%", "X") but it really is a bug. Mika From rodney_bates at lcwb.coop Sun Nov 16 20:13:57 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Sun, 16 Nov 2014 13:13:57 -0600 Subject: [M3devel] bug in Fmt.F In-Reply-To: <20141116102453.1EAE81A208F@async.async.caltech.edu> References: <20141116102453.1EAE81A208F@async.async.caltech.edu> Message-ID: <5468F775.1060605@lcwb.coop> By my reading, I can see how this fails. There is an inconsistent invariant in Fmt.ReadSpec. However, by reading, and confirmed by experiment, it should raise Convert.Failed. Is your loop happening outside the call on Fmt.F? On 11/16/2014 04:24 AM, mika at async.caltech.edu wrote: > Fmt.F("%s","X") > > produces "X" (right) > > Fmt.F("% %s", "X") > > produces "% X" (right) > > Fmt.F("%%s", "X") > > does not terminate (wrong)--should produce "%X" > > to produce "%X" workaround is > > Fmt.F("%s%s", "%", "X") > > but it really is a bug. > > Mika > > -- Rodney Bates rodney.m.bates at acm.org From mika at async.caltech.edu Sun Nov 16 20:59:41 2014 From: mika at async.caltech.edu (mika at async.caltech.edu) Date: Sun, 16 Nov 2014 11:59:41 -0800 Subject: [M3devel] bug in Fmt.F In-Reply-To: <5468F775.1060605@lcwb.coop> References: <20141116102453.1EAE81A208F@async.async.caltech.edu> <5468F775.1060605@lcwb.coop> Message-ID: <20141116195941.1C0871A208F@async.async.caltech.edu> Ah, sorry, my choice of words was imprecise. By "does not terminate" I do indeed mean that it raises the exception. I should have written "does not terminate normally, raises an exception" (My runtime turns the uncaught exception into abort, that is, non-termination of the F procedure.) Mika "Rodney M. Bates" writes: >By my reading, I can see how this fails. There is an inconsistent >invariant in Fmt.ReadSpec. However, by reading, and confirmed by experiment, >it should raise Convert.Failed. Is your loop happening outside the call on >Fmt.F? > >On 11/16/2014 04:24 AM, mika at async.caltech.edu wrote: >> Fmt.F("%s","X") >> >> produces "X" (right) >> >> Fmt.F("% %s", "X") >> >> produces "% X" (right) >> >> Fmt.F("%%s", "X") >> >> does not terminate (wrong)--should produce "%X" >> >> to produce "%X" workaround is >> >> Fmt.F("%s%s", "%", "X") >> >> but it really is a bug. >> >> Mika >> >> > >-- >Rodney Bates >rodney.m.bates at acm.org From rodney_bates at lcwb.coop Tue Nov 18 20:00:21 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Tue, 18 Nov 2014 13:00:21 -0600 Subject: [M3devel] Fwd: Re: bug in Fmt.F In-Reply-To: <546A51F7.2000708@lcwb.coop> References: <546A51F7.2000708@lcwb.coop> Message-ID: <546B9745.9010900@lcwb.coop> -------- Original Message -------- Subject: Re: [M3devel] bug in Fmt.F Date: Mon, 17 Nov 2014 13:52:23 -0600 From: Rodney M. Bates Reply-To: rodney.m.bates at acm.org To: m3devel at elegosoft.com Fixed by github commit 53d4f9ad2a63c5dc5df217523bb92bb635a3f17b Also, added a comment in Fmt.i3, which said nothing about incomplete format specifiers. The implementation already attempted to treat them as ordinary characters, but this was incomplete. On 11/16/2014 04:24 AM, mika at async.caltech.edu wrote: > Fmt.F("%s","X") > > produces "X" (right) > > Fmt.F("% %s", "X") > > produces "% X" (right) > > Fmt.F("%%s", "X") > > does not terminate (wrong)--should produce "%X" > > to produce "%X" workaround is > > Fmt.F("%s%s", "%", "X") > > but it really is a bug. > > Mika > > -- Rodney Bates rodney.m.bates at acm.org From rodney_bates at lcwb.coop Tue Nov 18 20:00:59 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Tue, 18 Nov 2014 13:00:59 -0600 Subject: [M3devel] Fwd: Re: bug in Fmt.F -- fixed. In-Reply-To: <546A51F7.2000708@lcwb.coop> References: <546A51F7.2000708@lcwb.coop> Message-ID: <546B976B.7070804@lcwb.coop> -------- Original Message -------- Subject: Re: [M3devel] bug in Fmt.F Date: Mon, 17 Nov 2014 13:52:23 -0600 From: Rodney M. Bates Reply-To: rodney.m.bates at acm.org To: m3devel at elegosoft.com Fixed by github commit 53d4f9ad2a63c5dc5df217523bb92bb635a3f17b Also, added a comment in Fmt.i3, which said nothing about incomplete format specifiers. The implementation already attempted to treat them as ordinary characters, but this was incomplete. On 11/16/2014 04:24 AM, mika at async.caltech.edu wrote: > Fmt.F("%s","X") > > produces "X" (right) > > Fmt.F("% %s", "X") > > produces "% X" (right) > > Fmt.F("%%s", "X") > > does not terminate (wrong)--should produce "%X" > > to produce "%X" workaround is > > Fmt.F("%s%s", "%", "X") > > but it really is a bug. > > Mika > > -- Rodney Bates rodney.m.bates at acm.org From rodney_bates at lcwb.coop Tue Nov 18 20:06:48 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Tue, 18 Nov 2014 13:06:48 -0600 Subject: [M3devel] Fwd: github rename question In-Reply-To: <546A54A2.20305@lcwb.coop> References: <546A54A2.20305@lcwb.coop> Message-ID: <546B98C8.60400@lcwb.coop> Is https://github.com/modula3/cm3 just a rename of https://github.com/dragisha/cm3? Or a different repository? I seem to have the latter name stored somewhere in my local repository, as its origin, and am seeing worrisome messages about the different names. I did a fetch and merge in my local repo, which appeared to work as expected, but said it was merging from dragisha. Then at the end, it told me the name had changed. Later, I did a push, with several local commits waiting. Now, github shows _my_ merge as a commit in _its_ repo, which seems very odd. Could this have backdated things to an outdated repo? -- Rodney Bates rodney.m.bates at acm.org From rodney_bates at lcwb.coop Wed Nov 19 19:28:07 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Wed, 19 Nov 2014 12:28:07 -0600 Subject: [M3devel] Fwd: Re: github rename question In-Reply-To: <546CB72C.5020800@lcwb.coop> References: <546CB72C.5020800@lcwb.coop> Message-ID: <546CE137.1060200@lcwb.coop> -------- Original Message -------- Subject: Re: [M3devel] github rename question Date: Wed, 19 Nov 2014 09:28:44 -0600 From: Rodney M. Bates Reply-To: rodney.m.bates at acm.org To: Antony Hosking CC: m3devel , Dragi?a Duri? On 11/18/2014 01:57 PM, Antony Hosking wrote: > Scratch that. > It looks like the right code is there. > I think you did the same as I was doing before I got a fresh clone, in which a merge event ends up in the history. > I?m hoping Dragisha or someone can let us know how to fix it. This seems very confusing to me. I have only cloned once, and it would have been github.com/dragisha/cm3. This is apparently stored locally, though I don't know how to find and change it: ------------------------------------------------------------------------------------- rodney at allegheny:~/proj/m3/git/cm3$ git config -l user.name=Rodney Bates user.email=rodney.m.bates at acm.org credential.helper=cache --timeout=40000 core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true remote.origin.url=https://github.com/dragisha/cm3.git ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* branch.master.remote=origin branch.master.merge=refs/heads/master rodney at allegheny:~/proj/m3/git/cm3$ ------------------------------------------------------------------------------------- My pull command didn't name the repository explicitly, and it tells me it did the pull from what I had cloned: ------------------------------------------------------------------------------------- rodney at allegheny:~/proj/m3/git/cm3$ git pull From https://github.com/dragisha/cm3 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + d97d794...554adee master -> origin/master (forced update) fab06be..626f74c trunk -> origin/trunk * [new tag] verification-release-mavericks -> verification-release-mavericks Merge made by the 'recursive' strategy. .gitignore | 1 + m3-libs/m3core/src/Csupport/m3makefile | 4 ---- m3-libs/m3core/src/m3core.h | 4 ++++ m3-libs/m3core/src/thread/PTHREAD/ThreadApple.c | 6 +++--- m3-libs/m3core/src/thread/PTHREAD/ThreadPThread.i3 | 2 +- m3-libs/m3core/src/thread/PTHREAD/ThreadPThread.m3 | 58 ++++++++++++++++++++++++++-------------------------------- m3-libs/m3core/src/thread/PTHREAD/ThreadPThreadC.c | 24 +++++++++++++++++++++++- m3-sys/cminstall/src/config-no-install/AMD64_DARWIN | 4 ++++ m3-sys/cminstall/src/config-no-install/Darwin.common | 2 +- m3-sys/m3cc/gcc/gcc/m3cg/parse.c | 6 +++--- scripts/make-bin-dist-min.sh | 8 +++++--- 11 files changed, 71 insertions(+), 48 deletions(-) create mode 100644 .gitignore ------------------------------------------------------------------------------------- But when I did my push, it somehow knew that github.com/modula3/cm3 was involved in some way. But what did it actually do? And when should I add the ".git" at the end of the URL and when not? ------------------------------------------------------------------------------------- rodney at allegheny:~/proj/m3/git/cm3$ git push origin master Username for 'https://github.com': RodneyBates Password for 'https://RodneyBates at github.com': Counting objects: 3327, done. Delta compression using up to 4 threads. Compressing objects: 100% (677/677), done. Writing objects: 100% (2524/2524), 342.06 KiB | 0 bytes/s, done. Total 2524 (delta 2065), reused 2244 (delta 1820) remote: This repository moved. Please use the new location: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ remote: https://github.com/modula3/cm3.git ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ To https://github.com/dragisha/cm3.git ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 554adee..7a2dd48 master -> master rodney at allegheny:~/proj/m3/git/cm3$ ------------------------------------------------------------------------------------- If I do a fresh clone of github.com/modula3/cm3, I will no doubt have to manually locate and copy my not-yet-added/committed edits into it. ------------------------------------------------------------------------------------- rodney at allegheny:~/proj/m3/git/cm3$ git status # On branch master # Your branch is ahead of 'origin/master' by 8543 commits. # (use "git push" to publish your local commits) # # Changes not staged for commit: # (use "git add/rm ..." to update what will be committed) # (use "git checkout -- ..." to discard changes in working directory) # # modified: m3-libs/libm3/src/rw/Wr.i3 # modified: m3-libs/libm3/tests/fmtlex/fmt/src/Makefile # modified: m3-libs/libm3/tests/fmtlex/fmt/src/m3makefile # modified: m3-libs/libm3/tests/fmtlex/fmt/src/run-tests # modified: m3-libs/libunicode/src/UniWr.m3 # modified: m3-libs/libunicode/src/UnsafeUniWr.m3 # modified: m3-libs/m3core/src/text/Text.i3 # modified: m3-libs/ordsets/ordsets/src/OrdSets.mg # modified: m3-sys/cm3/src/Builder.m3 # deleted: m3-sys/m3gdb/gdb/bfd/doc/bfd.info # modified: scripts/pkginfo.txt # # Untracked files: # (use "git add ..." to include in what will be committed) # (snip: ...... Lots of irrelevant stuff, including build directories, etc. ) # It took 2.29 seconds to enumerate untracked files. 'status -uno' # may speed it up, but you have to be careful not to forget to add # new files yourself (see 'git help status'). no changes added to commit (use "git add" and/or "git commit -a") rodney at allegheny:~/proj/m3/git/cm3$ ------------------------------------------------------------------------------------- > >> On Nov 18, 2014, at 2:42 PM, Antony Hosking wrote: >> >> It looks like your commit backdated to old code. >> I see reversions of the thread fixes I made a few months back. >> >> Can anyone help Rodney undo? >> I?d try, but my git foo is pretty weak. >> >>> On Nov 18, 2014, at 2:35 PM, Antony Hosking wrote: >>> >>> I had a similar problem because I was using an outdated clone. >>> I don?t recall what the fix was. Can someone out there help? >>> >>> But what you need to do is to reclone form https://github.com/modula3/cm3 and make sure to use that in future. >>> >>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>> 305 N. University Street | West Lafayette | IN 47907 | USA >>> Mobile +1 765 427 5484 >>> >>> >>> >>>> On Nov 18, 2014, at 2:30 PM, Antony Hosking wrote: >>>> >>>> PS https://github.com/modula3/cm3 >>>> >>>> dragisha is a different repo! >>>> >>>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>>> 305 N. University Street | West Lafayette | IN 47907 | USA >>>> Mobile +1 765 427 5484 >>>> >>>> >>>> >>>>> On Nov 18, 2014, at 2:06 PM, Rodney M. Bates wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Is https://github.com/modula3/cm3 just a rename of https://github.com/dragisha/cm3? >>>>> Or a different repository? I seem to have the latter name stored somewhere in my local >>>>> repository, as its origin, and am seeing worrisome messages about the different names. >>>>> >>>>> I did a fetch and merge in my local repo, which appeared to work as expected, but said >>>>> it was merging from dragisha. Then at the end, it told me the name had changed. Later, >>>>> I did a push, with several local commits waiting. Now, github shows _my_ merge as a >>>>> commit in _its_ repo, which seems very odd. Could this have backdated things to >>>>> an outdated repo? >>>>> >>>>> >>>>> >>>>> -- >>>>> Rodney Bates >>>>> rodney.m.bates at acm.org >>>>> >>>>> >>>> >>> >> > > -- Rodney Bates rodney.m.bates at acm.org From dragisha at m3w.org Thu Nov 27 21:59:36 2014 From: dragisha at m3w.org (=?utf-8?Q?Dragi=C5=A1a_Duri=C4=87?=) Date: Thu, 27 Nov 2014 21:59:36 +0100 Subject: [M3devel] github rename question In-Reply-To: <1D721A55-5B88-4DC8-910A-956986BA65BF@purdue.edu> References: <546A54A2.20305@lcwb.coop> <546B98C8.60400@lcwb.coop> <5E7FECCE-4BE0-4C9E-AA7E-36AC60804B42@purdue.edu> <41383B6E-F532-4FA7-BE5D-A44712E7CADA@purdue.edu> <1D721A55-5B88-4DC8-910A-956986BA65BF@purdue.edu> Message-ID: <8F3CEEE0-475E-46BA-85B9-8FE5F4FA663C@m3w.org> Hi, I am reading through repo but I don?t see a problem (end of day and all?). Can somebody point me in right direction? I had problem accessing to repo, 403 Forbidden something. Somehow, my 2010 MBP had git binary 1.6.1 from Jan 2009 in /usr/local/bin :). OSX Yosemite git is 1.9.x, though. Access works. (just a hint to anybody else meeting similar 403 problem:) dd > On 18 Nov 2014, at 20:57, Antony Hosking wrote: > > Scratch that. > It looks like the right code is there. > I think you did the same as I was doing before I got a fresh clone, in which a merge event ends up in the history. > I?m hoping Dragisha or someone can let us know how to fix it. > >> On Nov 18, 2014, at 2:42 PM, Antony Hosking wrote: >> >> It looks like your commit backdated to old code. >> I see reversions of the thread fixes I made a few months back. >> >> Can anyone help Rodney undo? >> I?d try, but my git foo is pretty weak. >> >>> On Nov 18, 2014, at 2:35 PM, Antony Hosking wrote: >>> >>> I had a similar problem because I was using an outdated clone. >>> I don?t recall what the fix was. Can someone out there help? >>> >>> But what you need to do is to reclone form https://github.com/modula3/cm3 and make sure to use that in future. >>> >>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>> 305 N. University Street | West Lafayette | IN 47907 | USA >>> Mobile +1 765 427 5484 >>> >>> >>> >>>> On Nov 18, 2014, at 2:30 PM, Antony Hosking wrote: >>>> >>>> PS https://github.com/modula3/cm3 >>>> >>>> dragisha is a different repo! >>>> >>>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>>> 305 N. University Street | West Lafayette | IN 47907 | USA >>>> Mobile +1 765 427 5484 >>>> >>>> >>>> >>>>> On Nov 18, 2014, at 2:06 PM, Rodney M. Bates wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Is https://github.com/modula3/cm3 just a rename of https://github.com/dragisha/cm3? >>>>> Or a different repository? I seem to have the latter name stored somewhere in my local >>>>> repository, as its origin, and am seeing worrisome messages about the different names. >>>>> >>>>> I did a fetch and merge in my local repo, which appeared to work as expected, but said >>>>> it was merging from dragisha. Then at the end, it told me the name had changed. Later, >>>>> I did a push, with several local commits waiting. Now, github shows _my_ merge as a >>>>> commit in _its_ repo, which seems very odd. Could this have backdated things to >>>>> an outdated repo? >>>>> >>>>> >>>>> >>>>> -- >>>>> Rodney Bates >>>>> rodney.m.bates at acm.org >>>>> >>>>> >>>> >>> >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 495 bytes Desc: Message signed with OpenPGP using GPGMail URL: From rodney_bates at lcwb.coop Sat Nov 29 00:27:40 2014 From: rodney_bates at lcwb.coop (Rodney M. Bates) Date: Fri, 28 Nov 2014 17:27:40 -0600 Subject: [M3devel] github rename question In-Reply-To: <8F3CEEE0-475E-46BA-85B9-8FE5F4FA663C@m3w.org> References: <546A54A2.20305@lcwb.coop> <546B98C8.60400@lcwb.coop> <5E7FECCE-4BE0-4C9E-AA7E-36AC60804B42@purdue.edu> <41383B6E-F532-4FA7-BE5D-A44712E7CADA@purdue.edu> <1D721A55-5B88-4DC8-910A-956986BA65BF@purdue.edu> <8F3CEEE0-475E-46BA-85B9-8FE5F4FA663C@m3w.org> Message-ID: <547904EC.4020807@lcwb.coop> From a combination of reading github documentation pages and a couple of experiments, I am pretty well convinced that the two github repository URLs I was worried about are just pointers to the same repo. I also successfully changed the URL my local repo has stored as the 'origin' repo to the new one, so now it doesn't nag or worry me when I do pulls or pushes. I still can't supply an explicit URL to any git command to name the remote repo. They all either give error messages or do apparently nothing. On 11/27/2014 02:59 PM, Dragi?a Duri? wrote: > Hi, > > I am reading through repo but I don?t see a problem (end of day and all?). Can somebody point me in right direction? > > I had problem accessing to repo, 403 Forbidden something. Somehow, my 2010 MBP had git binary 1.6.1 from Jan 2009 in /usr/local/bin :). OSX Yosemite git is 1.9.x, though. Access works. (just a hint to anybody else meeting similar 403 problem:) > > dd > >> On 18 Nov 2014, at 20:57, Antony Hosking wrote: >> >> Scratch that. >> It looks like the right code is there. >> I think you did the same as I was doing before I got a fresh clone, in which a merge event ends up in the history. >> I?m hoping Dragisha or someone can let us know how to fix it. >> >>> On Nov 18, 2014, at 2:42 PM, Antony Hosking wrote: >>> >>> It looks like your commit backdated to old code. >>> I see reversions of the thread fixes I made a few months back. >>> >>> Can anyone help Rodney undo? >>> I?d try, but my git foo is pretty weak. >>> >>>> On Nov 18, 2014, at 2:35 PM, Antony Hosking wrote: >>>> >>>> I had a similar problem because I was using an outdated clone. >>>> I don?t recall what the fix was. Can someone out there help? >>>> >>>> But what you need to do is to reclone form https://github.com/modula3/cm3 and make sure to use that in future. >>>> >>>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>>> 305 N. University Street | West Lafayette | IN 47907 | USA >>>> Mobile +1 765 427 5484 >>>> >>>> >>>> >>>>> On Nov 18, 2014, at 2:30 PM, Antony Hosking wrote: >>>>> >>>>> PS https://github.com/modula3/cm3 >>>>> >>>>> dragisha is a different repo! >>>>> >>>>> Antony Hosking | Associate Professor | Computer Science | Purdue University >>>>> 305 N. University Street | West Lafayette | IN 47907 | USA >>>>> Mobile +1 765 427 5484 >>>>> >>>>> >>>>> >>>>>> On Nov 18, 2014, at 2:06 PM, Rodney M. Bates wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Is https://github.com/modula3/cm3 just a rename of https://github.com/dragisha/cm3? >>>>>> Or a different repository? I seem to have the latter name stored somewhere in my local >>>>>> repository, as its origin, and am seeing worrisome messages about the different names. >>>>>> >>>>>> I did a fetch and merge in my local repo, which appeared to work as expected, but said >>>>>> it was merging from dragisha. Then at the end, it told me the name had changed. Later, >>>>>> I did a push, with several local commits waiting. Now, github shows _my_ merge as a >>>>>> commit in _its_ repo, which seems very odd. Could this have backdated things to >>>>>> an outdated repo? >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Rodney Bates >>>>>> rodney.m.bates at acm.org >>>>>> >>>>>> >>>>> >>>> >>> >> > -- Rodney Bates rodney.m.bates at acm.org