Over the last year or so I have had a terrible time working with a PHP-4 application that had to be moved to PHP-7. I have constantly been confronted with niggling changes between one version and the other ... such as deprecating then removing regular-expression functions, only to introduce the same functions using different names but with the parameters reversed. Once a language has been in service for a long time, there are literally hundreds of millions of lines of source-code out there in production, and the most important business consideration is that it can be effectively maintained and efficiently migrated. I think that is the biggest mistake that the Perl-6 people made: theirs was and is a completely different language, with no forward-migration path nor any fallback position. If Perl-5 actually needs a successor, I think that it should just be called 5.x+1, and it should contain only incremental changes from what we have now. If you make changes to the language which wipe-out the installed code base, as PHP certainly did, you are creating a huge expense for no reason and with no return on investment.
-
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.
|
