Am 04.08.2011 02:32, schrieb Stas Malyshev:
I'm not sure I understand why you need week refs there - can't you just
always use $prodDb->getProduct(1) and when you don't need it anymore
just do $prodDb->drop(1)? Or let it drop it whenever it wants to?
My Project requires lots of DB-Record <=> PH
Hi!
On 8/3/11 12:22 PM, Jan Dolecek wrote:
Thanks Etienne,
I was waiting for this for a while! I wrote a blog post how to get
best benefits from weak references:
http://blog.juzna.cz/2011/08/weak-references-in-php/
Perhaps this will help showing people what are they good for.
I'm not sure I
Thanks!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, Aug 4, 2011 at 12:35 AM, Jonathan Bond-Caron wrote:
> On Wed Aug 3 05:16 PM, Lester Caine wrote:
>> Jan Dolecek wrote:
>> > I was waiting for this for a while! I wrote a blog post how to get
>> > best benefits from weak references:
>> > http://blog.juzna.cz/2011/08/weak-references-in-php/
On Wed Aug 3 05:16 PM, Lester Caine wrote:
> Jan Dolecek wrote:
> > I was waiting for this for a while! I wrote a blog post how to get
> > best benefits from weak references:
> > http://blog.juzna.cz/2011/08/weak-references-in-php/
> > Perhaps this will help showing people what are they good for.
Jan Dolecek wrote:
I was waiting for this for a while! I wrote a blog post how to get
best benefits from weak references:
http://blog.juzna.cz/2011/08/weak-references-in-php/
Perhaps this will help showing people what are they good for.
This again relates to MySQl's method of working ...
ibase_
In the date() function the formats are split up. In date() G is w/o leading
zeros and H is w/ leading zeros.
Why were these (as well as many others) combined and turned into an
either/or for DateTime::createFromFormat?
On Wed, Aug 3, 2011 at 4:10 PM, Derick Rethans wrote:
> On Wed, 3 Aug 2011,
On Wed, 3 Aug 2011, Nicolai Scheer wrote:
> On 03.08.2011 21:29, Joey Smith wrote:
> >> 2011/8/4 Nicolai Scheer :
> >>> Hi!
> >>>
> >>> Did anyone had the time to review bug 55240
> >>> (https://bugs.php.net/bug.php?id=55240), yet?
> >>>
> >
> > It definitely appears to be unexpected behaviour - t
Hi!
On 03.08.2011 21:29, Joey Smith wrote:
>> 2011/8/4 Nicolai Scheer :
>>> Hi!
>>>
>>> Did anyone had the time to review bug 55240
>>> (https://bugs.php.net/bug.php?id=55240), yet?
>>>
>
> It definitely appears to be unexpected behaviour - the 'G' format for
> hours is "24-hour format without lea
On Wed, Aug 03, 2011 at 01:29:54PM -0600, Joey Smith wrote:
> DateTime::createFromFormat("dn", "118")
> -- Did you mean "August 11th", "November 8th", or "June 1st"?
Pardon my idiocy, here - it's quite clear that "November 8th"
wouldn't be a possible meaning here - I collapsed a couple of
example
On Thu, Aug 04, 2011 at 01:06:38AM +0800, Laruence wrote:
> Hi:
>I read the ext/date/lib/parse_date.c, and I think this could not be a bug ,
>since 800 will be think as 80h 0min(timelib_get_nr is common
> function, to get number from data description string with fixed max
> length),
>th
Thanks Etienne,
I was waiting for this for a while! I wrote a blog post how to get
best benefits from weak references:
http://blog.juzna.cz/2011/08/weak-references-in-php/
Perhaps this will help showing people what are they good for.
And thanks to PECL extension I hope we can start using them in
Hi:
I read the ext/date/lib/parse_date.c, and I think this could not be a bug ,
since 800 will be think as 80h 0min(timelib_get_nr is common
function, to get number from data description string with fixed max
length),
than 11 + (80 / 24) ~= 14
thanks
2011/8/4 Nicolai Scheer :
> Hi!
>
>
Hi!
Did anyone had the time to review bug 55240
(https://bugs.php.net/bug.php?id=55240), yet?
So far it just has been adjusted to reflect the right package.
Any pointers are welcome!
Grettings,
Nico
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php
Hello,
Voting is now open for "Error message formatting for development" RFC.
The RFC and patch can be found here:
https://wiki.php.net/rfc/error-formatting-for-developers
You can vote here:
https://wiki.php.net/rfc/error-formatting-for-developers#vote
cheers,
Derick
--
PHP Internals - PHP Ru
On Wed, Aug 3, 2011 at 4:29 PM, Etienne Kneuss wrote:
> Hi,
>
> http://pecl.php.net/package/Weakref has been created, and the
> standalone code should compile fine (I checked for 5_3 only but
> everything should be smooth for 5_4/trunk)
Not exactly (for the record here):
weakref.c
g:\php-sdk\ph
Hi,
On Wed, Aug 3, 2011 at 16:35, Gustavo Lopes wrote:
> Em Wed, 03 Aug 2011 15:29:20 +0100, Etienne Kneuss
> escreveu:
>
>> Hi,
>>
>> http://pecl.php.net/package/Weakref has been created, and the
>> standalone code should compile fine (I checked for 5_3 only but
>> everything should be smooth f
Em Wed, 03 Aug 2011 15:29:20 +0100, Etienne Kneuss
escreveu:
Hi,
http://pecl.php.net/package/Weakref has been created, and the
standalone code should compile fine (I checked for 5_3 only but
everything should be smooth for 5_4/trunk)
The next planned addition is a StrongRef class, following
Hi,
http://pecl.php.net/package/Weakref has been created, and the
standalone code should compile fine (I checked for 5_3 only but
everything should be smooth for 5_4/trunk)
The next planned addition is a StrongRef class, following the exact
same interface as WeakRef only that it is always valid a
Good idea. I will see what I can do when I get time.
~Hannes
On 3 August 2011 12:32, Pierre Joye wrote:
> hi Hannes,
>
> I would suggest to still update the RFC with the various very
> instructive comments and example use cases you use in this thread.
> Doing the same in the long run should help
I guess to get a clear error message, because this is a BC change.
Many people would wonder why working scripts are causing parse errors
after upgrade of php. Makes sense to have error messages as clear as
possible ;)
Jan Dolecek
juzna...@gmail.com
2011/7/29 Kiyoto Tamura :
> Hi Johannes,
>
> T
hi Hannes,
I would suggest to still update the RFC with the various very
instructive comments and example use cases you use in this thread.
Doing the same in the long run should help as well to understand the
goals, implementations, etc., for the pecl users or for the 2nd
attempt to get it in the
Hello,
We had a healthy discussion around WR and I have been able to express
my concerns. The consensus is clearly to put it in a PECL extension so
I think this discussion should move on to the practical matters of
doing this. I suggest aborting the vote and changing the RFC state to
something lik
Am 03.08.2011 09:35, schrieb Lester Caine:
I think this is were I am sitting at the moment ... If a script needs to
tidy up memory because something has gone wrong, then in my book the
script is faulty? The example of why it is needed does not make sense to
me, probably because I don't understand
Rasmus Lerdorf wrote:
I think the only valid point for putting this in core is that it does
feel more like a core feature than a pecl add-on. However, a number of
us are uncomfortable with the impact of it and would like to understand
better how people other than yourself would use it, or more li
25 matches
Mail list logo
