Skip to content

Instantly share code, notes, and snippets.

@Whateverable
Created March 15, 2017 03:14
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Whateverable/9276cc9c7912d65af40c6eea840f0391 to your computer and use it in GitHub Desktop.
Save Whateverable/9276cc9c7912d65af40c6eea840f0391 to your computer and use it in GitHub Desktop.
bisectable6
old=2015.07 say 5 .Int
Bisecting: 3168 revisions left to test after this (roughly 12 steps)
[8d0af58a48c240ad17a65917367365858aaf7c51] Make sure we emit :($ is raw).perl correctly
»»»»» Testing 8d0af58a48c240ad17a65917367365858aaf7c51
»»»»» Script output:
5
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 79efbb1dacffb2c6229891a811220b43f56611c7
»»»»» Script output:
5
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 30e8464db9b34f0569ec2c010eed4b7fea077075
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/ijMnVqZVMK
Two terms in a row
at /tmp/ijMnVqZVMK:1
------> say 5⏏ .Int
expecting any of:
infix
infix stopper
postfix
statement end
statement modifier
statement modifier loop
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing ab7d9632e3eb42429cac22b2ec56b817506b0df8
»»»»» Script output:
5
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 3091699043875bc459f2f4cbf98eae7c1a2230d9
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/ijMnVqZVMK
Two terms in a row
at /tmp/ijMnVqZVMK:1
------> say 5⏏ .Int
expecting any of:
infix
infix stopper
postfix
statement end
statement modifier
statement modifier loop
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 1acccc2efe8a05dce8336a03c9197df4f33ed899
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/ijMnVqZVMK
Two terms in a row
at /tmp/ijMnVqZVMK:1
------> say 5⏏ .Int
expecting any of:
infix
infix stopper
postfix
statement end
statement modifier
statement modifier loop
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 95674c856ced78409eae0b4ed2da5862b2bace18
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/ijMnVqZVMK
Two terms in a row
at /tmp/ijMnVqZVMK:1
------> say 5⏏ .Int
expecting any of:
infix
infix stopper
postfix
statement end
statement modifier
statement modifier loop
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 91b8b1ee03c64f3b9941642d930b9199b8aa3a86
»»»»» Script output:
5
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing de8024d25d95b64a4a0a8f55d04dd444f09595cd
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/ijMnVqZVMK
Two terms in a row
at /tmp/ijMnVqZVMK:1
------> say 5⏏ .Int
expecting any of:
infix
infix stopper
postfix
statement end
statement modifier
statement modifier loop
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing db0c46e74491479a228f7da5570f5ca99b7618df
»»»»» Script output:
5
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 0132b654104259b26a2920fb9a89f545281bb9b3
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/ijMnVqZVMK
Two terms in a row
at /tmp/ijMnVqZVMK:1
------> say 5⏏ .Int
expecting any of:
infix
infix stopper
postfix
statement end
statement modifier
statement modifier loop
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing cb25b2f475f31335d77d018474482aceec2c74de
»»»»» Script output:
5
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 73836e1a70378b0c56c234e84385159564a0c355
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/ijMnVqZVMK
Two terms in a row
at /tmp/ijMnVqZVMK:1
------> say 5⏏ .Int
expecting any of:
infix
infix stopper
postfix
statement end
statement modifier
statement modifier loop
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
cb25b2f475f31335d77d018474482aceec2c74de is the first new commit
commit cb25b2f475f31335d77d018474482aceec2c74de
Author: TimToady <larry@wall.org>
Date: Sat Sep 26 23:01:22 2015 -0700
Allow infix:<.> if next thing is alphabetic
As much as I mistrust "fluent" programming, we already have an infix:<.=>
operator, so it's not a big stretch to have infix:<.>. We limit it
to actual method names so that we can detect (most) accidental use
of P5's use of . for concatenation. Note that this is a term/infix
distinction now, so .meth where a term is expected still defaults to $_.
Community standards for method cascades will likely ask for whitespace
around infix:<.> to make a visual disinction from the term form, but we
don't enforce that, if for no other reason than to refrain from giving
the fluent programmers something to yammer on about. Basically, I've
decided that the slight possibility for greater confusion is outweighed
by consistency with .= and utility of have a . that can also serve as
a precedence modifier. (Since both .= and . parse leftward with
item assignment precedence, but rightward as a term.)
:040000 040000 be07c9752378c7034bc8d1ab2b34c78903ae1029 b09e45504a167da4e8328131c80bebac71267277 M src
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment