Changes between Version 6 and Version 7 of Migrating to NQPrx

Show
Ignore:
Timestamp:
11/18/09 08:01:15 (5 years ago)
Author:
Austin_Hastings
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Migrating to NQPrx

    v6 v7  
    55Here are the things I have found so far: 
    66 
    7   1. $-variable interpolation in double-quoted strings. 
     7=== $-variable interpolation in double-quoted strings. === 
    88 
    9   I have been using qq strings because they allow backslash-interpolation, but because a bunch of my stuff generates PIR on the fly, I have " ... $P0 ... " all over the place. Needless to say, this is generating a fair amount of rework. 
     9I have been using qq strings because they allow backslash-interpolation, but because a bunch of my stuff generates PIR on the fly, I have " ... $P0 ... " all over the place. Needless to say, this is generating a fair amount of rework. 
    1010 
    11   1. Stricter POD syntax. 
     11=== Stricter POD syntax === 
    1212 
    13   I haven't dug into the code for the new rules, but the current POD recognizer is more picky than it used to be. Formerly, the POD parser took just about any set of `^=` lines as POD. (And I took horrible advantage of that.) Now, I'm not sure what it's doing. (For myself, I'm just converting everything to # comments.) 
     13I haven't dug into the code for the new rules, but the current POD recognizer is more picky than it used to be. Formerly, the POD parser took just about any set of `^=` lines as POD. (And I took horrible advantage of that.) Now, I'm not sure what it's doing. (For myself, I'm just converting everything to # comments.) 
    1414 
    15   1. Lexical subs. 
     15=== Lexical subs === 
    1616 
    17   I've read this in Pmichaud's release notes, but I haven't had the chance to bounce off it yet (because I'm still working on the issues above). This will make a difference in code that has been doing Foo::bar() style calls, since apparently bar() will now require "our sub bar" instead of "sub bar". That doesn't seem too bad, considering the other changes. More as it becomes relevant. 
     17I've read this in Pmichaud's release notes, but I haven't had the chance to bounce off it yet (because I'm still working on the issues above). This will make a difference in code that has been doing Foo::bar() style calls, since apparently bar() will now require "our sub bar" instead of "sub bar". That doesn't seem too bad, considering the other changes. More as it becomes relevant. 
    1818 
    19   1. Spaces before postfix operators disallowed. 
     19=== Spaces before postfix operators disallowed === 
    2020 
    21   I had some code like `$x ++;` and `$x --;` that failed. Removed spaces. 
     21I had some code like `$x ++;` and `$x --;` that failed. Removed spaces. 
    2222 
    23   1. Stricter whitespace rules around keywords 
     23=== Stricter whitespace rules around keywords === 
    2424 
    2525  `if $condition { } else {}` now requires spaces around the `else` keyword