Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Lack of space after != operator changes behaviour #3322
The following test in roast currently is skipped for Rakudo as a nom regression:
STD parses the comparision successfully:
<psch> std: 3 !=3
while Rakudo tries to assign and fails:
<psch> r: say 3 !=3
that STD says it is okay does not mean much here, because:
./viv -e 'say 1 != 3'
./viv -e 'say 1 !=3'
So already STD has a problem here and I will open a STD-issue in its github repo, see:
If the programmer omits the space after the != (not equal, numeral) operator, the behavior of the operator changes to: [assign RHS to LHS, return !RHS], as can be seen from these examples:
<ZoffixW> m: say 0 != 0
This behaviour is confusing and probably not wanted by most programmers.
On Mon Apr 25 09:20:43 2016, firstname.lastname@example.org wrote:
This is a dupe of https://rt-archive.perl.org/perl6/Ticket/Display.html?id=121108, which is wrongly titled at the moment.