Tony Marston wrote on 09/02/2015 10:07:
There may not be an actual RFC for any of these *YET*, but the
revolutionaries are still out there, plotting and scheming in their
dark corners. They will be the ones who leap on an innocent-sounding
feature and silently convert it to something more insid
Lester Caine wrote on 09/02/2015 01:31:
On 09/02/15 00:05, Rowan Collins wrote:
>>Some of the new 'styles' of writing things are
>>going to make things considerably worse for those who are going to have
>>to maintain this code in the future.
>
>If you're writing code that you know will be har
On 09/02/2015 11:07, Tony Marston wrote:
There may not be an actual RFC for any of these *YET*, but the
revolutionaries are still out there, plotting and scheming in their dark
corners. They will be the ones who leap on an innocent-sounding feature
and silently convert it to something more insidi
"Matteo Beccati" wrote in message news:54d883d2.5020...@beccati.com...
On 09/02/2015 10:49, Tony Marston wrote:
But there is a vociferous group who want to change the language in a
revolutionary way instead of an evolutionary way. They want to drop weak
typing and replace it with strict typing
On 09/02/2015 10:49, Tony Marston wrote:
But there is a vociferous group who want to change the language in a
revolutionary way instead of an evolutionary way. They want to drop weak
typing and replace it with strict typing, they want to replace a lot of
function names with something "more consis
"Matteo Beccati" wrote in message news:54d74c68.6070...@beccati.com...
On 08/02/2015 11:24, Tony Marston wrote:
Well said. If it is not possible to have a single codebase that runs in
both PHP 5 *AND* PHP 7 then that will be a total disaster.
Of course you can have a single codebase running
On 09/02/15 00:05, Rowan Collins wrote:
>> Some of the new 'styles' of writing things are
>> going to make things considerably worse for those who are going to have
>> to maintain this code in the future.
>
> If you're writing code that you know will be hard to maintain in the
> future, you're d
On 08/02/2015 20:53, Lester Caine wrote:
On 08/02/15 19:00, Rowan Collins wrote:
We have a single code base happily running on 5.2, 5.3, 5.4, and I think
even 5.5, so it is definitely possible with some code bases. There were
a few pieces that had to be changed to work right under 5.3 and 5.4, b
On 08/02/15 19:00, Rowan Collins wrote:
> We have a single code base happily running on 5.2, 5.3, 5.4, and I think
> even 5.5, so it is definitely possible with some code bases. There were
> a few pieces that had to be changed to work right under 5.3 and 5.4, but
> none for which the new solution d
On 08/02/2015 12:30, Lester Caine wrote:
Currently it is impossible to run the PHP5.2 code base on PHP5.4. That
is a simple fact. So I can't do between 5.2 and 5.4 what I am currently
doing between 5.4 and 7. The code has to be reworked ... so what ever
anybody says PHP5 .4*IS* PHP6 in terms of
On 08/02/2015 11:45, Matteo Beccati wrote:
On 08/02/2015 11:24, Tony Marston wrote:
Well said. If it is not possible to have a single codebase that runs in
both PHP 5 *AND* PHP 7 then that will be a total disaster.
Of course you can have a single codebase running both on PHP5 and
PHP7, unless
On 08/02/15 11:43, Ralf Lang wrote:
> A lot of sites sticked with PHP5.3 because they were driven by
> enterprise platforms which by definition won't upgrade during the life
> cycle. That had its own costs and aches which are entirely not PHP's fault.
>
>> > PHP7 is proposing a LOT of shiny new fe
On 08/02/2015 11:24, Tony Marston wrote:
Well said. If it is not possible to have a single codebase that runs in
both PHP 5 *AND* PHP 7 then that will be a total disaster.
Of course you can have a single codebase running both on PHP5 and PHP7,
unless you want to use PHP7-only features.
But t
Hi Lester,
On 07.02.2015 13:36, Lester Caine wrote:
> My personal experience of PHP4 is simply one of having been developing
> all my code in PHP5.0 to 5.2 but ensuring that the code also still run
> clean on the PHP4 host.
Actually, PHP 4 changed a lot of things from PHP3. PHP 5.0.0 on the
othe
"Lester Caine" wrote in message news:54d73248.9030...@lsces.co.uk...
On 08/02/15 06:37, Yasuo Ohgaki wrote:
Hi Lester,
PHP7 is proposing a LOT of shiny new features which will break much
legacy code. So the question has to be just what is the plan
regarding
cross version support.
On 08/02/15 06:37, Yasuo Ohgaki wrote:
> Hi Lester,
>
> PHP7 is proposing a LOT of shiny new features which will break much
> legacy code. So the question has to be just what is the plan regarding
> cross version support. I see that the general consensus is PHP5 should
> just run?
Hi Lester,
On Sat, Feb 7, 2015 at 9:36 PM, Lester Caine wrote:
> PHP7 is proposing a LOT of shiny new features which will break much
> legacy code. So the question has to be just what is the plan regarding
> cross version support. I see that the general consensus is PHP5 should
> just run?
>
Do
My personal experience of PHP4 is simply one of having been developing
all my code in PHP5.0 to 5.2 but ensuring that the code also still run
clean on the PHP4 host. It was not until 5.3 that it was necessary to
freeze the code base for 5.2 for every PHP4 host and maintain that fork
while 'taking a
18 matches
Mail list logo
