Hello!
Can you add please CURLOPT_PRIVATE and CURLINFO_PRIVATE text parameters
to curl extension for php like CURLOPT_URL ?
Diff file for ext/curl/interface.c:
---
--- interface.c Tue May 22 08:39:20 2007
+++ php.5.2.3.interface.
I sometimes get the following error
>> Fatal error: Exception thrown without a stack frame in
>> Unknown on line 0
What does this mean?
When we see these, they're typically from our custom session handler.
In my experience that error is almost certainly in a piece of your
code that is r
On 6/29/07, Lars Schultz <[EMAIL PROTECTED]> wrote:
Hi there
I just tried to switch from 5.1 to 5.2.3 and got thrown off right away by:
"Object of class MyObject could not be converted to string"
I googled a bit and also read any Messages in the internals list but
couldn't find a decisive answe
always helpful). Is there any other way than casting an object to a
string to get an objects #ID?
spl_object_hash?
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing Li
Yes, unfortunately the end user needs to be aware enough of his
environment to either control the unicode.semantics flag or choose
the right server to run it on. Believe me, we've tried making
unicode.semantics controllable on a per-request basis, and after a
long and hard debate after part
> It sounds like your libraries are definitely oriented towards working
> with binary strings, rather than Unicode strings. So, I am not sure
> why you have unicode.semantics turned on then. If you turn it off,
> you will get backwards compatibility with PHP 5. And if you do that,
> you can still c
It sounds like your libraries are definitely oriented towards working
with binary strings, rather than Unicode strings. So, I am not sure
why you have unicode.semantics turned on then. If you turn it off,
you will get backwards compatibility with PHP 5. And if you do that,
you can still cre
Hi Lars,
In the meanwhile .. check out spl_object_hash
Evert
Lars Schultz wrote:
Hi there
I just tried to switch from 5.1 to 5.2.3 and got thrown off right away
by:
"Object of class MyObject could not be converted to string"
I googled a bit and also read any Messages in the internals list
Hi there
I just tried to switch from 5.1 to 5.2.3 and got thrown off right away by:
"Object of class MyObject could not be converted to string"
I googled a bit and also read any Messages in the internals list but
couldn't find a decisive answer as to wether this will stay this way or not.
I
> Call to developers:
> Create new versions of your apps/libraries which use new features of
> language. Make your users interested in upgrading. If users want it,
> hosting-owners will consider upgrades faster. It's all about
> marketing ;)
It also depends on your marketing policy. PHP 5.2.1 req
Hi,
On 6/29/07, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
For me it means that I have to maintain wrappers for fwrite,
base64_encode, ord, crc32 and all other unicode aware functions. Any
direct PHP string or stream function call can cause compatibility issues
or notices. Any function working w
>> Unicode code points can be defined with \u, but PHP6 breaks existing
>> octal
>> and hex escape sequences.
>
> What do you mean? Doesn't \x20 create U0020 character? Or you mean you'd
> expect it to create just one-byte 0x20? Doesn't binary string do that?
Try higher than 0x7F values.
If I wri
The thing which I don't understand is: why do people want backward
compatibility that much?
For me, PHP6 is the new environment and I don't want to move my
existing solutions there. That just won't be right.
Just like I didn't reuse code written for PHP4 in PHP5 projects.
This is a major version,
Hi,
On 6/29/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> PHP6 is very noisy ("Notice: fwrite(): 13 character unicode buffer
> downcoded for binary stream runtime_encoding", "Warning: base64_encode()
> expects parameter 1 to be strictly a binary string, Unicode string given")
Well, expor
Unicode code points can be defined with \u, but PHP6 breaks existing octal
and hex escape sequences.
What do you mean? Doesn't \x20 create U0020 character? Or you mean you'd
expect it to create just one-byte 0x20? Doesn't binary string do that?
PHP6 is very noisy ("Notice: fwrite(): 13 chara
On 29/06/07, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
>> It comes down to predicting the future. Whichever way we go, the
>> decision is going to be second-guessed. If we have critical mass for
>> a
>> clean BC break, then I am ok with it. For me personally it would make
>> things a bit easie
16 matches
Mail list logo
