On 9/16/05, Pierre Joye <[EMAIL PROTECTED]> wrote:
> From my side, after some cleanup, I should be UC ready pretty soon,
> but that is all post pear-1.4.0/5.1.0 stories :)
+ ext/gd
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 9/16/05, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> I don't think that's feasible as it makes development even harder.
> I don't think Unicode support is that far off. Most of the core work
> is done. The more people can help with upgrading the functions the better...
I agree here, as far as """
I don't think that's feasible as it makes development even harder.
I don't think Unicode support is that far off. Most of the core work
is done. The more people can help with upgrading the functions the better...
I'm off for the weekend Might find some Internet connection at some point.
And
On 9/16/05, Jani Taskinen <[EMAIL PROTECTED]> wrote:
> I really meant what I said. Like Andi said, PHP 6 won't
> be out very soon, but I'd really like to have the cleaned
> up PHP, preferrably yesterday. This year is fine too.
>
> And without unicode..
Having a PHP6 and a PHP
On Thu, 15 Sep 2005, Andi Gutmans wrote:
I don't really see how PHP 6 can support a build without ICU. With the whole
Call that version PHP 7.
core using the ICU library it's almost like not supporting libC. If you find a
way I'd be happy to hear about it and discuss but I think it's not
On Fri, 16 Sep 2005, Pierre Joye wrote:
On 9/16/05, Andi Gutmans <[EMAIL PROTECTED]> wrote:
Jani,
I don't really see how PHP 6 can support a build
without ICU. With the whole core using the ICU
library it's almost like not supporting libC. If
you find a way I'd be happy to hear about it and
di
On 9/16/05, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> Jani,
>
> I don't really see how PHP 6 can support a build
> without ICU. With the whole core using the ICU
> library it's almost like not supporting libC. If
> you find a way I'd be happy to hear about it and
> discuss but I think it's not real
On 9/16/05, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> I think most of that list can be implemented but while it's easy to
> give a +1 and make the changes, I still want to dive into some of
> them more. I've been much busier looking at the Unicode stuff and
> 5.1.x patches so I didn't have a lot of
I think most of that list can be implemented but while it's easy to
give a +1 and make the changes, I still want to dive into some of
them more. I've been much busier looking at the Unicode stuff and
5.1.x patches so I didn't have a lot of time to look into it. I think
it's quite reasonable to
On 9/16/05, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> Jani,
>
> I don't really see how PHP 6 can support a build
> without ICU. With the whole core using the ICU
> library it's almost like not supporting libC. If
> you find a way I'd be happy to hear about it and
> discuss but I think it's not rea
Jani,
I don't really see how PHP 6 can support a build
without ICU. With the whole core using the ICU
library it's almost like not supporting libC. If
you find a way I'd be happy to hear about it and
discuss but I think it's not realistic.
Regarding spring cleaning, I suggest to relax a
bi
Touché. :)
But I must insist. I want to upgrade at some point.
I might even have use for unicode, at some point. But why can't
I disable it as long as it does not give me anything I need?
On other topic, I want to do the spring cleaning we discussed earlier
already in PH
No one is forcing you to upgrade to PHP 6.
--Wez.
On 9/15/05, Jani Taskinen <[EMAIL PROTECTED]> wrote:
>
> I don't care about this as long as I can DISABLE it from
> my PHP builds (and not be forced to link it with ICU).
>
> --Jani
>
> On Wed, 14 Sep 2005, Rasmus Lerdorf wrote:
I don't care about this as long as I can DISABLE it from
my PHP builds (and not be forced to link it with ICU).
--Jani
On Wed, 14 Sep 2005, Rasmus Lerdorf wrote:
Makoto Tozawa wrote:
Jani Taskinen wrote:
Show me one such person please. One that does this using PHP. :)
On Thursday 15 September 2005 06:12, Rasmus Lerdorf wrote:
> Makoto Tozawa wrote:
> > Jani Taskinen wrote:
> >> Show me one such person please. One that does this using PHP. :)
> >> One that really NEEDS this to be possible..
> >
> > It's impossible to find one as PHP doesn't support it tod
Makoto Tozawa wrote:
> Jani Taskinen wrote:
>
>> Show me one such person please. One that does this using PHP. :)
>> One that really NEEDS this to be possible..
>
>
> It's impossible to find one as PHP doesn't support it today.
>
> Think of defining a class which encapsulates a database
Jani Taskinen wrote:
Show me one such person please. One that does this using PHP. :)
One that really NEEDS this to be possible..
It's impossible to find one as PHP doesn't support it today.
Think of defining a class which encapsulates a database table, and the
table name and column n
On 9/14/05, Tex Texin <[EMAIL PROTECTED]> wrote:
> Pierre, I am glad it is acceptable to you. What you say does not apply to
> everyone.
>
> > Well, english is the language of choice for programming
> > because everyone understands very basic english words.
>
> This is just not true. It is true f
""Tex Texin"" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> -Original Message-
>>It is fine you don't want or intend to take advantage of it. (Personally,
>>I
>>think more than 5 characters in an identifier is too much to type.)
>>But why do you want to not let others us
On Tue, 13 Sep 2005, Ilia Alshanetsky wrote:
> Rasmus Lerdorf wrote:
> > What do you mean? Why wouldn't it be portable?
>
> Well, for one thing code written to use unicode identifiers will
> immediately be limited to running on PHP 6 installs. While code using
> ASCII identifier with standard
On Tue, 13 Sep 2005, Ondrej Ivanič wrote:
> Pierre Joye wrote:
> > On 9/13/05, Ondrej Ivanič <[EMAIL PROTECTED]> wrote:
> >
> > >IMHO, if someone need ...
> >
> > I know, that's why I say: PHP6.
>
> Another constraint? why?
>
> 1) It's a BC break (... which impact 1 or 2 users? :) )
Actually,
> -Original Message-
> From: Jani Taskinen [mailto:[EMAIL PROTECTED]
>
> On Wed, 14 Sep 2005, Tex Texin wrote:
>
> > ok, so you shouldn't program in french. For others it is fine and
> > works better than english.
>
> Show me one such person please. One that does this using PHP. :
In addition to the ongoing discussion I like to ask, how far you would
like to go?
If you like unicode support for functions, classes and variable names,
are you willing to do the same for all the php specific function names
and php language specific words? Will "function" and "class" or "return
On Wed, 14 Sep 2005, Tex Texin wrote:
ok, so you shouldn't program in french. For others it is fine and works
better than english.
Show me one such person please. One that does this using PHP. :)
One that really NEEDS this to be possible..
I'm with Pierre on this, and I'm not nati
snipped...
>
> Check the history, every language developement tools which
> tried to do it do not support it anymore. Why? For the exact
> same reasons listed in this thread.
I am not sure why you say this. Java and other languages support
multilingual identifiers.
The newest standards for pr
gt; From: Pierre Joye [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 14, 2005 1:38 AM
> To: Tex Texin
> Cc: Andi Gutmans; Andrei Zmievski; Rasmus Lerdorf; Ilia
> Alshanetsky; internals
> Subject: Re: [PHP-DEV] PHP6, Unicode for language functions,
> classes,methods, vars name
On 9/14/05, Tex Texin <[EMAIL PROTECTED]> wrote:
> Imagine implementing some complicated workflow or other process or algorithm,
> where each
> step has a name in the local language, and as a programmer, you have to come
> up with a
> meaningless (to you) string to represent it, and having to s
ED]
> Sent: Tuesday, September 13, 2005 3:28 PM
> To: Andrei Zmievski; Rasmus Lerdorf
> Cc: Ilia Alshanetsky; [EMAIL PROTECTED]; internals
> Subject: Re: [PHP-DEV] PHP6, Unicode for language functions,
> classes,methods, vars names
>
>
> Me too...
>
> At 09:16 AM
Me too...
At 09:16 AM 9/13/2005, Andrei Zmievski wrote:
Yep, what Rasmus said.
-Andrei
On Sep 13, 2005, at 6:25 AM, Rasmus Lerdorf wrote:
Ilia Alshanetsky wrote:
Pierre Joye wrote:
is not something I like to see. For language constructs, I would
really like to have only ASCII support...
At 20:12 13/09/2005, Sebastian Nohn wrote:
Rasmus Lerdorf wrote:
This is a choice that should be up to the developer. If she wants to
share his code with people who don't understand his language and/or
character set, then she should use some common language/character set.
But the language shou
> The language does put a limitation as it
> does not provide a way to show the
> identifiers in a neutral way. For example
> ACI 4D (for those who knows it) did it
> in the right way. All functions are localized,
> I can choose the language I want I will be
> able to read the identifiers. But I do
Rasmus Lerdorf wrote:
This is a choice that should be up to the developer. If she wants to
share his code with people who don't understand his language and/or
character set, then she should use some common language/character set.
But the language should not force this limitation on her.
Why n
On 9/13/05, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
> This is a choice that should be up to the developer. If she wants to
> share his code with people who don't understand his language and/or
> character set, then she should use some common language/character set.
> But the language should not
Ilia Alshanetsky wrote:
> Rasmus Lerdorf wrote:
>
>>What do you mean? Why wouldn't it be portable?
>
>
> Well, for one thing code written to use unicode identifiers will
> immediately be limited to running on PHP 6 installs. While code using
> ASCII identifier with standard "compat" layer cou
Rasmus Lerdorf wrote:
> What do you mean? Why wouldn't it be portable?
Well, for one thing code written to use unicode identifiers will
immediately be limited to running on PHP 6 installs. While code using
ASCII identifier with standard "compat" layer could run just fine.
Another reason to onl
Yep, what Rasmus said.
-Andrei
On Sep 13, 2005, at 6:25 AM, Rasmus Lerdorf wrote:
Ilia Alshanetsky wrote:
Pierre Joye wrote:
is not something I like to see. For language constructs, I would
really like to have only ASCII support...
+1 IMHO language identifiers should be limited to ASCII.
Ilia Alshanetsky wrote:
> Pierre Joye wrote:
>
>>is not something I like to see. For language constructs, I would
>>really like to have only ASCII support...
>
>
> +1 IMHO language identifiers should be limited to ASCII. Yes you can now
> use language specific chars by changing the locale, so th
Pierre Joye wrote:
> is not something I like to see. For language constructs, I would
> really like to have only ASCII support...
+1 IMHO language identifiers should be limited to ASCII. Yes you can now
use language specific chars by changing the locale, so that ž, č, ÿ are
taken, but that hardly
Pierre Joye wrote:
On 9/13/05, Ondrej Ivanič <[EMAIL PROTECTED]> wrote:
IMHO, if someone need ...
I know, that's why I say: PHP6.
Another constraint? why?
1) It's a BC break (... which impact 1 or 2 users? :) )
2) PHP can be scripting engine in learning programs for children ( like
this:
On Tue, 13 Sep 2005, Pierre Joye wrote:
Do we really want to support unicode for functions, classes, methods
and variables names?
No. I don't need unicode at all, but if I ever would need it,
it would be enough if I can store it in variables.
(which I can do already, without any f
On 9/13/05, Ondrej Ivanič <[EMAIL PROTECTED]> wrote:
> Pierre Joye wrote:
> >
> > is not something I like to see. For language constructs, I would
> > really like to have only ASCII support...
>
> This suff works in php4,5:
>
>
> function zmaž($čozmazať) {
> echo "mažem $čozmazať\n";
>
Pierre Joye wrote:
is not something I like to see. For language constructs, I would
really like to have only ASCII support...
This suff works in php4,5:
IMHO, if someone need ...
--
Ondrej Ivanič
([EMAIL PROTECTED])
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, v
Hello,
Do we really want to support unicode for functions, classes, methods
and variables names?
I really like to have unicode for comments (// /* */) and inside quotes.
But having:
is not something I like to see. For language constructs, I would
really like to have only ASCII support...
Rega
43 matches
Mail list logo
