Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

it seems like since Perl 6 is already committed to not worrying about backward compatibility

Perl 6 is promised to be compatible in 80-90% of the code out there. Sometimes it may have a radically different implementation (such as the => operator), but will end up working the same way in practice. Other things have had significant additions, but will still work the old way if you really want to (like subroutine signatures--but realize you'll be missing out on a lot of really cool stuff if you ignore them). Regexen are the only major subsystem I can think of that are complete incompatible.

----
: () { :|:& };:

Note: All code is untested, unless otherwise stated


In reply to Re^5: Ensuring forward compatibility by hardburn
in thread Ensuring forward compatibility by DrHyde

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.