Hi!
Date is immutable, but there's no reason why date object should be able
to represent only one date. Reference to Java is not exactly applicable
here, as many problems existing in Java (thread safety, long-living
object references, etc.) do not exist in PHP.
Say we have a blog post entity,
As Nikita says, from an ORM perspective, an object is always immutable (at
least with current implementations I know of), and that's because they can
simply use the object hashes to identify two different objects.
While this may be a niche to many of you, I've encountered a quite big
amount of
Hi Internals,
Why not EOL until Zend has it's ZCE program up to date with the latest
version?
Kind regards,
Chris van Dam
Op 11-12-12 02:29 schreef Johannes Schlüter johan...@php.net:
On Tue, 2012-12-11 at 08:55 +0900, Yasuo Ohgaki wrote:
2012/12/10 Adam Harvey ahar...@php.net:
On 10
Hi,
2012/12/11 Johannes Schlüter johan...@php.net:
Well, people don't trust .0 versions, so we then should wait for 5.5.1
or 5.5.2 ... but by then 5.6 will already be in development, so why not
wait for 5.6?
+1
It's much better!
--
Yasuo Ohgaki
yohg...@ohgaki.net
--
PHP Internals - PHP
On Tue, Dec 11, 2012 at 11:30 AM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi,
2012/12/11 Johannes Schlüter johan...@php.net:
Well, people don't trust .0 versions, so we then should wait for 5.5.1
or 5.5.2 ... but by then 5.6 will already be in development, so why not
wait for 5.6?
+1
It's
On Tue, Dec 11, 2012 at 12:48 PM, Pierre Joye pierre@gmail.com wrote:
what's about:
- announce 5.3 EOL plan with 5.5 final release
then:
- EOL by release of php-next (a year later)
or
- EOL by release of php-next+1 (two years later)
depending on which option got accepted.
In
hi,
On Tue, Dec 11, 2012 at 12:30 PM, Lior Kaplan lio...@zend.com wrote:
On Tue, Dec 11, 2012 at 12:48 PM, Pierre Joye pierre@gmail.com wrote:
what's about:
- announce 5.3 EOL plan with 5.5 final release
then:
- EOL by release of php-next (a year later)
or
- EOL by release of
It matters as calling userspace functions is in at least 90% of the cases
the wrong approach and there are better ones. The better approach depends
on the goal.
(The only times where it is a good thing to do is when calling a user
provided callback as in usort() or a method from an object
hi,
On Tue, Dec 11, 2012 at 3:25 PM, Amir ad...@ecdcconference.org wrote:
It matters as calling userspace functions is in at least 90% of the cases
the wrong approach and there are better ones. The better approach depends
on the goal.
(The only times where it is a good thing to do is when
On Tue, 2012-12-11 at 17:55 +0330, Amir wrote:
It matters as calling userspace functions is in at least 90% of the cases
the wrong approach and there are better ones. The better approach depends
on the goal.
(The only times where it is a good thing to do is when calling a user
provided
Hi!
As Nikita says, from an ORM perspective, an object is always immutable
(at least with current implementations I know of), and that's because
they can simply use the object hashes to identify two different objects.
Why for ORM Date is even an object? In most databases, date is a basic
People tend to desire API changes that go on the same directions they are
going.
That's nature...
Daniel Ribeiro Gomes Pereira
Twitter https://twitter.com/#!/drgomesp |
Facebookhttps://www.facebook.com/profile.php?id=10407054469
| LinkedIn
Hi!
strings/timestamps (it could be database's representation of date like
2010-10-23 or just integer with timestamp) or it could be objects of
DateTime. More efficient and logical way would be objects, but that way
you must aware users that they shouldn't modify values of DateTime
Hi!
@Stas a DateTime object is the perfect representation of what in DB
world has dozens of different representations. The reasoning behind it
is exactly the same as having a DateTime object vs having a date+time
string.
You are confusing internal PHP representation with object identity vs.
Stas Malyshev smalys...@sugarcrm.com писал(а) в своём письме Tue, 11 Dec
2012 21:06:05 +0400:
Hi!
As Nikita says, from an ORM perspective, an object is always immutable
(at least with current implementations I know of), and that's because
they can simply use the object hashes to identify
On 12/10/12 8:32 AM, Johannes Schlüter wrote:
Hi,
On Mon, 2012-12-10 at 14:10 +0100, Pierre Joye wrote:
There was no consensus, I am not sure where you get the idea.
By spending the time to go through the thread, taking the opinions
stated there, filtering out side discussions (like LTS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Internals,
I think with the start of recent 5.3 EOL discussion, it's about time
to give an overview over the 5.5 schedule as far as I planned it.
I want to go for a new alpha this week (on thursday), 4 week after the
first one. I should have send
On 12 December 2012 04:40, David Soria Parra dso...@gmx.net wrote:
From there I want to go with a new alpha in about two weeks, as we
there are some things like ext/mysql deprecation in the pipeline.
The MySQL commit was pushed yesterday, so that's not a blocker at this point.
Adam
--
PHP
18 matches
Mail list logo
