At 02:27 27/11/2002, Stig S. Bakken wrote:
Let's try being realistic, and focus on the quick wins first, such as
good error codes.
Go Stig.
Zeev
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
On Mon, 25 Nov 2002, John Coggeshall wrote:
I am completely +1 to the concept of taking error codes out of the PHP
core and replacing them with an XML document, period. I say this
regardless of language considerations -- I just think for everyone
involved having a XML document which controls
On Tue, 26 Nov 2002, John Coggeshall wrote:
Maxim (and anyone else who is interested)
Shall we try to get a patch for this working then? I'm thinking perhaps
starting off with an XML file defining the error messages, which is
converted to a cdb for actual use.
Waste of time
Derick
--
I've seen a big poster in my local Fullbright foundation represantive.
It says something like : One of every four people on the earth knows some
English.
Andrey
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
At 10:14 26.11.2002, Derick Rethans wrote:
On Tue, 26 Nov 2002, John Coggeshall wrote:
Maxim (and anyone else who is interested)
Shall we try to get a patch for this working then? I'm thinking perhaps
starting off with an XML file defining the error messages, which is
converted to a cdb
John Coggeshall [EMAIL PROTECTED] wrote... :
Wow..
Alrighty... I've read through all of this stuff -- everyone seems to
have quite a strong opinion on this one :) Since I kinda brought it up
with Maxim, let me provide a concept of implementation and defend it...
I'd of course love to
Well, yes, if it is not XML it can still work. A thought here is - to
connect built-in errors to the documentation, which is where XML would
help.
--
Maxim Maletsky
[EMAIL PROTECTED]
Shane Caraveo [EMAIL PROTECTED] wrote... :
I am completely +1 to the concept of taking error codes out of
Again, XML was my throw to this thread. I intuitively thought of XML
because it would help connecting the PHP error reporting to the official
documentaion.
Don't you think it would be helpful? Of course there are work-arounds
for that too.
--
Maxim Maletsky
[EMAIL PROTECTED]
John Coggeshall
PROTECTED]; 'Maxim Maletsky';
'PHP Developers Mailing List'
Subject: Re: [PHP-DEV] Error Codes, Langs, etc
cats or gettext comes to mind.
Neither are usable, though, because PHP would need to support
multiple concurrent message catalogues on a per-thread base.
gettext/catgets
Andrey Hristov [EMAIL PROTECTED] wrote... :
I've seen a big poster in my local Fullbright foundation represantive.
It says something like : One of every four people on the earth knows some
English.
Why does Billy localize M$ windows then? And, most importantly, what
would he sell without
I've seen a big poster in my local Fullbright foundation
represantive.
It says something like : One of every four people on the earth
knows some
English.
Why does Billy localize M$ windows then? And, most importantly,
what
would he sell without doing it? Remember, his users know basic IT
[EMAIL PROTECTED] (Marcus Börger) wrote... :
At 10:14 26.11.2002, Derick Rethans wrote:
On Tue, 26 Nov 2002, John Coggeshall wrote:
Maxim (and anyone else who is interested)
Shall we try to get a patch for this working then? I'm thinking perhaps
starting off with an XML file
I've seen a big poster in my local Fullbright foundation represantive.
It says something like : One of every four people on the earth knows
some
English.
Why does Billy localize M$ windows then? And, most importantly, what
would he sell without doing it? Remember, his users know
Billy tried localizing programming languages as well. Remember Excel
95? It ended up in complete disaster and was removed in the next
office version.
The language won't chance. Stop the FUD.
- Sascha
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit:
On Tue, 26 Nov 2002, Sascha Schumann wrote:
Billy tried localizing programming languages as well. Remember Excel
95? It ended up in complete disaster and was removed in the next
office version.
The language won't chance. Stop the FUD.
This is not FUD. He brought up the issue of M$
This is not FUD. He brought up the issue of M$ practises. And I didn't
hear you answer the question about why is parse error more difficult to
understand than register_shutdown_function?
You need to learn a bit about writing good compilers. It is
easy to write a compiler; it is hard
On Tue, 26 Nov 2002, Sascha Schumann wrote:
This is not FUD. He brought up the issue of M$ practises. And I didn't
hear you answer the question about why is parse error more difficult to
understand than register_shutdown_function?
You need to learn a bit about writing good compilers.
On Tue, 2002-11-26 at 04:21, Shane Caraveo wrote:
I am completely +1 to the concept of taking error codes out of the PHP
core and replacing them with an XML document, period.
I had wanted to avoid this whole thread, but decided to read this one
message, and ouch. While I'm all for
On Tue, 2002-11-26 at 05:04, John Coggeshall wrote:
I had wanted to avoid this whole thread, but decided to read this one
message, and ouch. While I'm all for internationalization in general,
I'm realy not all for using xml wherever possible just because it can
be. There are existing
On 27 Nov 2002 01:27:18 +0100 Stig S. Bakken [EMAIL PROTECTED] wrote:
If someone wants help on php-general and their error message is in Urdu,
then too bad. Companies like IBM and Oracle has solved this problem by
introducing more complex error codes (such as 0123-456 File not
found),
I am completely +1 to the concept of taking error codes out of the PHP
core and replacing them with an XML document, period.
I had wanted to avoid this whole thread, but decided to read this one
message, and ouch. While I'm all for internationalization in general,
I'm realy not all for using
On November 25, 2002 09:52 pm, John Coggeshall wrote:
I am completely +1 to the concept of taking error codes out of the PHP
core and replacing them with an XML document, period. I say this
regardless of language considerations -- I just think for everyone
involved having a XML document which
On Mon, 25 Nov 2002, Shane Caraveo wrote:
I am completely +1 to the concept of taking error codes out of the PHP
core and replacing them with an XML document, period.
I had wanted to avoid this whole thread, but decided to read this one
message, and ouch. While I'm all for
I am definitely -1 for this idea. XML is a buzzword, it is
good in some cases
not so good in others, definitely not a one size fits all
solution. In PHP's
case it would add decency on an XML parser, make life of
developers adding,
modifying, removing error messages difficult and just like
I had wanted to avoid this whole thread, but decided to read this one
message, and ouch. While I'm all for internationalization in general,
I'm realy not all for using xml wherever possible just because it can
be. There are existing techniques and libraries designed for
this, find
one and
John Coggeshall wrote:
I am definitely -1 for this idea. XML is a buzzword, it is
good in some cases
not so good in others, definitely not a one size fits all
solution. In PHP's
case it would add decency on an XML parser, make life of
developers adding,
modifying, removing error messages
cats or gettext comes to mind.
Neither are usable, though, because PHP would need to support
multiple concurrent message catalogues on a per-thread base.
gettext/catgets associate exactly one language with each
process through the use of environment variables, so that
they
[mailto:[EMAIL PROTECTED]]
Sent: Monday, November 25, 2002 11:29 PM
To: Shane Caraveo
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; 'Maxim Maletsky';
'PHP Developers Mailing List'
Subject: Re: [PHP-DEV] Error Codes, Langs, etc
cats or gettext comes to mind.
Neither are usable, though, because
Sascha Schumann wrote:
cats or gettext comes to mind.
Neither are usable, though, because PHP would need to support
multiple concurrent message catalogues on a per-thread base.
gettext/catgets associate exactly one language with each
process through the use of environment
Why? The error messages are for the developer, not the masses. But
Imagine someone using his web-hoster's environment for
debugging purposes. This affects the masses.
generaly I agree with using something else. More the point is that
stuff exists, techniques exist, no need to
30 matches
Mail list logo
