Hi list,
IMHO PHP6 might need more new features to attract developers to migrate
their code / write new code for PHP6. Unicode support is great for those
who need it, but is likely to cause work for those that "just have to
live with it". Nobody likes to so extra work, and it's hard to get
manager
Jordan Wambaugh wrote:
> I've just recently begun writing PHP extensions for the first time. Sara
> Golemon's article on extension development has been a priceless resource for
> me, but I haven't been able to find any documentation on how to define a
> class, give it methods and properties etc
Hi Jordan,
next to the book, which is a good reading there are some lsides from
Marcus at talks.somabo.de (look for "Code Camp" or something like that)
which give an introduction, but well, slides are always made for being
explained during a talk :-)
johannes
On Tue, 2007-06-19 at 13:53 -0400, J
Hi,
I think that PHP6 adoption will obviously come down to exactly how much
slower unicode support will make things. If its a 10% drop, I think we
will probably find ways to smooth out the kinks with some nice tweaks
here and there. If it gets considerably above 10%, then it will be more
tric
Ilia Alshanetsky wrote:
> Sorry to interject, but just a quick slightly off topic note.
>
> In your earlier e-mail you've said that
>
> -
>
> I actually don't have a problem with 95% of PHP 6 installations turning
> off Unicode support and this being the default setting for ISP's
De: Tomas Kuliavas [mailto:[EMAIL PROTECTED]
> We are working on different code. You have code with some specific
> character set and you can control all strings.
Tomas, stop arguing on this. As a library maintainer, I agree with you and I
don't understand where the
'killer feature' is (I heard t
Sorry to interject, but just a quick slightly off topic note.
In your earlier e-mail you've said that
-
I actually don't have a problem with 95% of PHP 6 installations turning
off Unicode support and this being the default setting for ISP's.
Full Unicode support in an applicati
Jani Taskinen wrote:
> Rasmus Lerdorf wrote:
>> Uh, this was agreed upon by everyone involved in the design of the
>> Unicode support. So saying I am the only one is extremely misleading.
>> I may be the only one explaining why the decision was reached, but I am
>> certainly not the only one in fa
Rasmus Lerdorf wrote:
Uh, this was agreed upon by everyone involved in the design of the
Unicode support. So saying I am the only one is extremely misleading.
I may be the only one explaining why the decision was reached, but I am
certainly not the only one in favour of it.
Yesterday's decisio
> On 19/06/07, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
>> I don't care about Unicode support, because it breaks things. I suspect
>> that PHP6 Unicode extension won't give me controls that I have in PHP5
>> and
>> PHP4 strings. PHP6 Unicode support is not designed for international
>> environment
On 6/19/07, muquaddim <[EMAIL PROTECTED]> wrote:
I think you have to buy the Sara's Book
Or/and read the sources. PHP or PECL are full of extensions
implementing classes :)
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I think you have to buy the Sara's Book
Very good book.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Jordan Wambaugh wrote:
I've just recently begun writing PHP extensions for the first time. Sara
Golemon's article on extension development has been a priceless resource for
me, but I haven't been able to find any documentation on how to define a
class, give it methods and properties etc within
I've just recently begun writing PHP extensions for the first time. Sara
Golemon's article on extension development has been a priceless resource for
me, but I haven't been able to find any documentation on how to define a
class, give it methods and properties etc within an extension. Is there a
I must organize the development of my own CMS, that the reason why i MUST have
a cvs please.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
PHP4 strings. PHP6 Unicode support is not designed for international
environment. It is designed for nationalized environments and allows PHP
script developers to code in their native language. Code written in
The goal of PHP 6 unicode support is definitely to allow
internationalized developmen
On 19/06/07, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
I don't care about Unicode support, because it breaks things. I suspect
that PHP6 Unicode extension won't give me controls that I have in PHP5 and
PHP4 strings. PHP6 Unicode support is not designed for international
environment. It is designe
> Pierre wrote:
>> On 6/19/07, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
>>
>>> But this is no different from writing code that will work on both PHP 5
>>> and PHP 6. The only difference is that instead of checking for PHP 5
>>> you will be checking for Unicode. Like I said, we don't want the
>>>
Jeremy Privett wrote:
> But, let's look at this situation from another angle. What if
> unicode.semantics becomes the next magic_quotes or safe_mode, and is
> ALWAYS OFF in 95%+ of PHP installations? All of the work you did to add
> unicode support was WASTED on this presumption that if you don't h
On 6/19/07, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
Pierre wrote:
> On 6/19/07, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
>
>> But this is no different from writing code that will work on both PHP 5
>> and PHP 6. The only difference is that instead of checking for PHP 5
>> you will be checking
> -Original Message-
> From: Pierre [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 19, 2007 9:09 AM
> To: Rasmus Lerdorf
> Cc: Peter Brodersen; internals@lists.php.net
> Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP
6?
>
> On 6/19/07, Rasmus Lerdorf <[EMAIL PROTECTE
Pierre wrote:
> On 6/19/07, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
>
>> But this is no different from writing code that will work on both PHP 5
>> and PHP 6. The only difference is that instead of checking for PHP 5
>> you will be checking for Unicode. Like I said, we don't want the
>> Unicod
Pierre wrote:
On 6/19/07, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
But this is no different from writing code that will work on both PHP 5
and PHP 6. The only difference is that instead of checking for PHP 5
you will be checking for Unicode. Like I said, we don't want the
Unicode decision to
I'm one of the Google Summer of Code students and I'm working on documenting
the new i18n and unicode features in PHP6. David Coallier (davidc) suggested me
to apply for a cvs account.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 6/19/07, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
But this is no different from writing code that will work on both PHP 5
and PHP 6. The only difference is that instead of checking for PHP 5
you will be checking for Unicode. Like I said, we don't want the
Unicode decision to be synonymous
So I have to write my own Sapi module in PHP way :-(
It looks like too tough for me. And its the right way.
My intention is to implement a simple funcion
int execute(char *filename); //filename is a php file
For I have to write a sapi module. No matter I'll at least try it.
Now the big question.
On Tue, 19 Jun 2007 07:26:57 -0700, in php.internals
[EMAIL PROTECTED] (Rasmus Lerdorf) wrote:
>> I think we were really close to get out of the
>> if(get_magic_quotes_gpc()) "requirement" but now it has been replaced
>> with a new one. Even if a developer would write (portable) PHP 6 only
>> code
Peter Brodersen wrote:
> On Fri, 15 Jun 2007 02:55:16 +0100, in php.internals
> [EMAIL PROTECTED] (Rasmus Lerdorf) wrote:
>
>> Those same shared hosting companies would never upgrade to PHP 6 if we
>> forced unicode semantics on them breaking legacy apps and that would
>> force us to maintain PHP
On Fri, 15 Jun 2007 02:55:16 +0100, in php.internals
[EMAIL PROTECTED] (Rasmus Lerdorf) wrote:
>Those same shared hosting companies would never upgrade to PHP 6 if we
>forced unicode semantics on them breaking legacy apps and that would
>force us to maintain PHP 5 forever.
On the other hand I fee
Alter ego. (with same karma as the other one, also remember to remove the mail
alias! :)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Fri, 15 Jun 2007, Derick Rethans wrote:
> 2. Add a new modifier "H" or "L" that is like G, but
>locale-insensitive.
I implemented this as the "H" modifier.
> Notes:
>
> - _build_trace_args (from Zend/zend_exceptions.c) seems also to be
> affected, as it uses the G modifier to build a
Can someone explain the closing comment on this bug report to me?
http://bugs.php.net/bug.php?id=38245
Surely in a addslashes-escaped string, \\ is the Windows directory
separator, not \.
The bug clearly describes irreversible corruption of upload filenames by
PHP. I just had a report of it in a
My mother told me.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
> The idea is to use the same set of "extension=foo" directives for all
> platforms (nearly all). It is relatively obvious that extension_dir
> will differ.
IMHO, it should also allow to dl() by extension name, but only as a fallback
mechanism to keep BC.
First consider the argument as a filenam
On 6/19/07, Stefan Priebsch <[EMAIL PROTECTED]> wrote:
Pierre,
> The idea is to use the same set of "extension=foo" directives for all
> platforms (nearly all). It is relatively obvious that extension_dir
> will differ.
>
> I like this idea and will ease our life, a litte :)
I got that, and I l
On Jun 19, 2007, at 4:38 AM, Richard Quadling wrote:
Sara has a nice article about TSRM:
http://blog.libssh2.org/index.php?/archives/22-What-the-heck-is-
TSRMLS_CC-anyway.html and since you're using php5ts.dll you have
zts enabled.
Why have ...
TSRMLS_CC
when ...
, TSRMLS_C
actually looks
Richard Quadling wrote:
On 19/06/07, Johannes Schlüter <[EMAIL PROTECTED]> wrote:
Sara has a nice article about TSRM:
http://blog.libssh2.org/index.php?/archives/22-What-the-heck-is-TSRMLS_CC-anyway.html
and since you're using php5ts.dll you have zts enabled.
Why have ...
TSRMLS_CC
when ...
On 19/06/07, Johannes Schlüter <[EMAIL PROTECTED]> wrote:
Sara has a nice article about TSRM:
http://blog.libssh2.org/index.php?/archives/22-What-the-heck-is-TSRMLS_CC-anyway.html
and since you're using php5ts.dll you have zts enabled.
Why have ...
TSRMLS_CC
when ...
, TSRMLS_C
actually lo
Pierre,
> The idea is to use the same set of "extension=foo" directives for all
> platforms (nearly all). It is relatively obvious that extension_dir
> will differ.
>
> I like this idea and will ease our life, a litte :)
I got that, and I like simplification. It would just not really make
php.in
On 6/19/07, Stefan Priebsch <[EMAIL PROTECTED]> wrote:
Andi,
Andi Gutmans schrieb:
> I got a feature idea from Apache. Apache will automatically translate
> mod_rewrite.so in LoadModule to mod_rewrite.dll on Windows. It'd be nice
> if we added the same to PHP so you wouldn't need to maintain two
David Zülke wrote:
Yeah, not to mention things like temp dirs, sendmail/smtp settings etc...
meaning to make it really useful, we would need a general way to handle
such platform difference. maybe with a syntax to handle platform
specific settings or prefixing of directories, but I guess then
Yeah, not to mention things like temp dirs, sendmail/smtp settings
etc...
David
Am 19.06.2007 um 08:51 schrieb Stefan Priebsch:
Andi,
Andi Gutmans schrieb:
I got a feature idea from Apache. Apache will automatically translate
mod_rewrite.so in LoadModule to mod_rewrite.dll on Windows. It
Hi again,
On Mon, 2007-06-18 at 18:12 -0400, muquaddim wrote:
> I think the configure option "--disable-zts" will work on the following
> lines.
>
> #ifdef ZTS
> #define TSRMLS_D void ***tsrm_ls
> #define TSRMLS_DC , TSRMLS_D
> #define TSRMLS_C tsrm_ls
> #define TSRMLS_CC , TSRMLS_C
> #else
> #d
43 matches
Mail list logo
