多个堆栈,多个版本打扰任何人,或者只是我? [英] multiple stacks, multiple versions bother anybody, or is it just me?

查看:68
本文介绍了多个堆栈,多个版本打扰任何人,或者只是我?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

持有5.0.4的所有版本,多个版本的多个版本

配置不可避免


将不得不等待看看问题的影响是什么例如
http://bugs.php.net/应用程序世界的bug.php?id = 33643 。我们可以

等待合适的热门分辨率并跳转到

的未来版本。 PHP4和PHP5之间已经存在分歧,然后进一步

这些开发创造了另一个,将阵营分成了4个。

语言修复影响php4和php5前进,

即它打破了很多现有的应用程序。由于它,我有应用程序打破




MySQL 4和MySQL 5之间也存在不连续性。显然

升级是如此糟糕,以至于XAMPP没有发布升级补丁为

它的下一个版本。它们要求您手动迁移数据。

XAMPP堆栈的未来版本存在疑问,或者至少要花费很多时间。现在更多的努力。


我们可以修复自己的代码,在某些堆栈或PHP版本上运行

和MySQL,但是我们无法解决所有第三方软件的问题。出来

那里。鉴于同一事物的版本之间的破碎率

更不用说事物的配置,多个堆栈是不可避免的。

这个性价比高吗?


或者我是在一个小山丘上建造一座山吗?


Best问候,

-Rich


-

http://groups.yahoo.com/group/heuristic/

Holding all versions at 5.0.4, Multiple stacks with multiple-version
configurations inevitable

Will have to wait to see what the impact of problems such as
http://bugs.php.net/bug.php?id=33643 to the application world. We may
wait for a suitable popular resolution and jump to that version in the
future. There''s already a rift between PHP4 and PHP5, and then further
developments such as these create another, splitting the camp into 4.
The fix to the language nit affects both php4 and php5 going forward,
that is it breaks a lot of existing applications. I have had apps break
due to it.

There is also a discontinuity between MySQL 4 and MySQL 5. Apparently
the upgrade is so bad that XAMPP is not releasing an upgrade patch for
it''s next versions. They require you to migrate the data manually.
Future versions of XAMPP stack are in doubt, or will at least be much
more of an effort now.

We can fix up our own code to run on certain stacks or versions of PHP
and MySQL, but we can''t fix up all the 3rd party software that is out
there. Given the rate of brokenness between versions of the same thing
let alone configurations of things, multiple stacks are inevitable. Is
this cost-effective?

Or am I making a mountain out of a molehill?

Best regards,
-Rich

--

http://groups.yahoo.com/group/heuristic/

推荐答案

Rich Kucera写道:
Rich Kucera wrote:
将所有版本保存在5.0.4,多个版本的多个版本
配置不可避免

将有等待查看问题的影响,例如
http ://bugs.php.net/bug.php?id = 33643 到应用程序世界。我们可能会等待合适的流行解决方案并在
的未来跳转到该版本。 PHP4和PHP5之间已经存在分歧,然后进一步开发这样的开发创建了另一个,将阵营分成了4个。
对语言的修复会影响php4和php5的发展,
就是它打破了很多现有的应用程序。由于它,我有应用程序破解。

MySQL 4和MySQL 5之间也存在不连续性。显然,升级太糟糕了,XAMPP没有发布升级补丁为
它的下一个版本。他们要求您手动迁移数据。
XAMPP堆栈的未来版本存在疑问,或者至少现在更多的努力。

我们可以修复我们自己的代码可以运行在PHP
和MySQL的某些堆栈或版本上,但是我们无法解决那里出现的所有第三方软件。鉴于同一事物的版本之间的破碎率,更不用说事物的配置,多个堆栈是不可避免的。这是否具有成本效益?

或者我是在一个小山丘上建造一座山?

致以最诚挚的问候,
-Rich

-

http:// groups .yahoo.com / group / heuristic /
Holding all versions at 5.0.4, Multiple stacks with multiple-version
configurations inevitable

Will have to wait to see what the impact of problems such as
http://bugs.php.net/bug.php?id=33643 to the application world. We may
wait for a suitable popular resolution and jump to that version in the
future. There''s already a rift between PHP4 and PHP5, and then further
developments such as these create another, splitting the camp into 4.
The fix to the language nit affects both php4 and php5 going forward,
that is it breaks a lot of existing applications. I have had apps break
due to it.

There is also a discontinuity between MySQL 4 and MySQL 5. Apparently
the upgrade is so bad that XAMPP is not releasing an upgrade patch for
it''s next versions. They require you to migrate the data manually.
Future versions of XAMPP stack are in doubt, or will at least be much
more of an effort now.

We can fix up our own code to run on certain stacks or versions of PHP
and MySQL, but we can''t fix up all the 3rd party software that is out
there. Given the rate of brokenness between versions of the same thing
let alone configurations of things, multiple stacks are inevitable. Is
this cost-effective?

Or am I making a mountain out of a molehill?

Best regards,
-Rich

--

http://groups.yahoo.com/group/heuristic/




FWIW,我同意这个结论。 Temporaries不应该作为

引用传递给函数或作为返回值。


它根本不会影响我的代码,因为我从来没有这样做过。

-

==================

删除x来自我的电子邮件地址

Jerry Stuckle

JDS计算机培训公司
js ******* @ attglobal.net

==================



FWIW, I agree with the conclusion. Temporaries should not be passed as
references, either to a function or as a return value.

It won''t affect my code at all, since I never did it in the first place.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================


为什么不呢?你从来没有这样做过:
Why not? You never did this:


x = f1(f2(
x = f1( f2(


这篇关于多个堆栈,多个版本打扰任何人,或者只是我?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆