http://master.php.net/manage/users.php
On Friday 16 April 2004 20.00, Ted Rolle wrote:
> I seem to have {lost|forgotten} the procedure for updating the information
> that forwards [EMAIL PROTECTED] to [EMAIL PROTECTED] I remember 'master'
> somewhere, http://master.php.net, but that doesn't work.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I seem to have {lost|forgotten} the procedure for updating the information
that forwards [EMAIL PROTECTED] to [EMAIL PROTECTED] I remember 'master'
somewhere, http://master.php.net, but that doesn't work.
Ted
-BEGIN PGP SIGNATURE-
Version: Gn
I'll take care of changing everything to E_WARNING tomorrow.
John
On Fri, 2004-04-16 at 18:27, Andi Gutmans wrote:
> John,
>
> I agree that currently it's better to change these back to real E_WARNINGS.
> I agree that exceptions should be thrown for things which we'd usually make
> E_ERRORs (i
I guess this would only help the lazy guys around. There are many other
ways to get around this without writing that many ternary constructs
eg:
function get_post_var ( $name , $default ) {
return isset ( $_POST[ $name ] ) ? $_POST[ $name ] : $default ;
}
$CUST_ID = (integer) get_post_var (
Yeah,
When we first switched to E_ALL error mode, I thought "Cool, I'll just put
an @ in front of these expressions"
Not cool. It was taking FOREVER (like seconds) to load a simple page that
had been taking ~ 20ms. After that we switched to the ternary operator,
and hence began the ifsetor()
Hello Alan,
Saturday, April 17, 2004, 2:36:55 AM, you wrote:
> Jason Garber wrote:
>> In our code, you will find many blocks looking like
>>
>> $CUST_ID = (integer) (isset($_POST['CUST_ID']) ? $_POST['CUST_ID'] : 0);
> so how is that different from
> $CUST_ID = (integer) @$_POST['CUST_ID'];
@
Jason Garber wrote:
In our code, you will find many blocks looking like
$CUST_ID = (integer) (isset($_POST['CUST_ID']) ? $_POST['CUST_ID'] : 0);
so how is that different from
$CUST_ID = (integer) @$_POST['CUST_ID'];
other than being pig headed about @... :)
Regards
Alan
--
PHP Internals - PHP Ru
In our code, you will find many blocks looking like
$CUST_ID = (integer) (isset($_POST['CUST_ID']) ? $_POST['CUST_ID'] : 0);
$CONTACT_ID = (integer) (isset($_POST['CONTACT_ID']) ? $_POST['CONTACT_ID']
: 0);
And when you want to read an element from an array that may or may not
exist, you see th
How about,
if (isset($b)) {
$a = $b;
} else {
$a = 10;
}
Or is that a bit too revolutionary? :)
The problems with these operators is that the logic you want here is rarely
simple, and when you need to refactor, you need to change your construct
back to if{}else{} often introducing bugs. I s
George Schlossnagle wrote:
On Apr 16, 2004, at 5:51 PM, Marcus Boerger wrote:
Hello George,
thinking twice and rechecking it is a bit more complicated though.
"NVL" in oracle means "Null-VaLue" or beter 'NULL Value replacement'.
We want to replace the non-existing situation with a predefined v
Derick Rethans wrote:
> On Fri, 16 Apr 2004, Marcus Boerger wrote:
>
>> [RFC] ifsetor operator
>>
>> Hello List,
>>
>> i also agrre that an internal function is much better. And here is
>> it as such an internal function (that does not result in an expensive
>> function call).
>>
>> Synopsis: "
Good call.
At 4/17/2004 01:17 AM +0300, Andi Gutmans wrote:
I don't want to spoil the party but:
a) I don't think we should add a new reserved word for this. I will try
and think of an alternative which uses the existing vocabulary.
b) I would not want to add this before releasing PHP 5.0.0. I th
Hello Andi,
Saturday, April 17, 2004, 12:17:49 AM, you wrote:
> I don't want to spoil the party but:
> a) I don't think we should add a new reserved word for this. I will try and
> think of an alternative which uses the existing vocabulary.
> b) I would not want to add this before releasing PHP 5
John,
I agree that currently it's better to change these back to real E_WARNINGS.
I agree that exceptions should be thrown for things which we'd usually make
E_ERRORs (if recoverable).
As most people here prefer not to go the route of exceptions, and I think
many (not all) of their reasoning ma
On Fri, 16 Apr 2004, Sterling Hughes wrote:
> Tidy's current error handling scheme is totally messed up - every
> single thing in the extension should be an E_WARNING by PHP standards.
> Its RC2, and this stuff has worked for a long time, breaking it now is
> counterproductive and annoying.
>
> Jo
Tidy's current error handling scheme is totally messed up - every
single thing in the extension should be an E_WARNING by PHP standards.
Its RC2, and this stuff has worked for a long time, breaking it now is
counterproductive and annoying.
John, if you insist on messing up the error handling i
Argh! Guys, let's not use anything that just combines 2 existing
keywords. Being able to read stuff at a glance is important:
if exists(...)
ifexists(...)
or
else if(...)
ifelse(...)
these would do vastly different things but look alike, and that is ungood.
-Rasmus
On Sat, 17 Apr 20
I don't want to spoil the party but:
a) I don't think we should add a new reserved word for this. I will try and
think of an alternative which uses the existing vocabulary.
b) I would not want to add this before releasing PHP 5.0.0. I think we
should add it afterwards. We are not talking about a
On Fri, 16 Apr 2004, Edin Kadribasic wrote:
>
>On Friday, Apr 16, 2004, at 22:25 Europe/Copenhagen, Rasmus Lerdorf
>wrote:
>
>> On Fri, 16 Apr 2004, Derick Rethans wrote:
>>
>>> On Fri, 16 Apr 2004, Rasmus Lerdorf wrote:
>>>
> This would lead to
> $a = isset($b, 'default');
I th
Jason Garber wrote:
As Wez pointed out, this is almost ready to insert into the parser.
Most of yesterdays conversation was spent hashing out the ways that this
should be implemented.
Ok, now I'm confused. Why is an RFC (Request For Comment) posted to the
internals list if it was already decide
On Apr 16, 2004, at 5:51 PM, Marcus Boerger wrote:
Hello George,
thinking twice and rechecking it is a bit more complicated though.
"NVL" in oracle means "Null-VaLue" or beter 'NULL Value replacement'.
We want to replace the non-existing situation with a predefined value
which is slightly differ
Should be fixed now -- windows builds too.
John
On Fri, 2004-04-16 at 15:34, Nuno Lopes wrote:
> >Should be fixed now.
> >Derick
>
> It isn't fixed because tidy tries to open NULL :)
> Please apply my patch that (hoppefully) fixes the problem. (I've tested it!)
>
> Nuno
--
-=~=--=~=--=~=--=~=-
Hello George,
thinking twice and rechecking it is a bit more complicated though.
"NVL" in oracle means "Null-VaLue" or beter 'NULL Value replacement'.
We want to replace the non-existing situation with a predefined value
which is slightly different.
Hence the name should be "NEL", "NEV" or "NEVA
s not result in an expensive
>>> function call).
>>>
>>> Synopsis: "ifsetor" "(" value "," default ")"
>>>
>>> Returns the value if it exists or a given default value.
>>>
>>> Syntax: "ifse
On Friday, Apr 16, 2004, at 22:25 Europe/Copenhagen, Rasmus Lerdorf
wrote:
On Fri, 16 Apr 2004, Derick Rethans wrote:
On Fri, 16 Apr 2004, Rasmus Lerdorf wrote:
This would lead to
$a = isset($b, 'default');
I think this is the sanest suggestion yet.
But it's already in use... (isset accepts mul
")"
Semantic:
- The value in question must be a variable.
- The default value can be any expression.
- The default value can be omitted in which case NULL will be used.
http://marcus-boerger.de/php/ext/ze2/ze2-ifsetor-20040416-2.diff.txt
best regards
marcus
Friday, April 16, 2004,
Chris -
As Wez pointed out, this is almost ready to insert into the parser. Most
of yesterdays conversation was spent hashing out the ways that this should
be implemented.
Remember, one of the biggest reasons for creating this function was so that
E_NOTICE would not be issued when attempting
Hello Everyone,
I have a problem reusing variables.
This does not work (second query does not return any data):
$rs = fbsql_query("select * from tuser;", $con);
...
$rs = fbsql_query("select * from tuser;", $con);
These three combinations work fine (both queries return data):
$rs = fbsql_query
On Fri, 16 Apr 2004, Derick Rethans wrote:
> On Fri, 16 Apr 2004, Rasmus Lerdorf wrote:
>
> > > This would lead to
> > > $a = isset($b, 'default');
> >
> > I think this is the sanest suggestion yet.
>
> But it's already in use... (isset accepts multiple parameters and does
> an AND on those).
A
Marcus Boerger wrote:
You cannot do this because that syntax is already defined for PHP
with another semantic.
Ok, missed that one, I never used multiple arguments to isset ;-)
Let's call it ifsetor, ifset or default then. But I still think allowing
a list of expressions is a good idea because bo
On Fri, 16 Apr 2004, Rasmus Lerdorf wrote:
> > This would lead to
> > $a = isset($b, 'default');
>
> I think this is the sanest suggestion yet.
But it's already in use... (isset accepts multiple parameters and does
an AND on those).
Derick
--
PHP Internals - PHP Runtime Development Mailing Lis
> > function call).
> >
> > Synopsis: "ifsetor" "(" value "," default ")"
> >
> > Returns the value if it exists or a given default value.
> >
> > Syntax: "ifsetor" "(" variable [ ","
On Fri, 16 Apr 2004, Christian Schneider wrote:
> Derick Rethans wrote:
> > isset() works on a variable only too, so this behavior matches already
> > existing behavior.
>
> Hmm... this brings up another idea:
> Extend isset to have this behaviour. Funnily enough when I was thinking
> about such
Derick wrote:
> I don't like this name though, the rest sounds ok.
Me either, but can't think of anything better (well, ?:
operator is good ;)
> Other possibilities:
>
> ifset
> default
default is already used in switch
--Wez.
--
PHP Internals - PHP Runtime Development Mailing List
To unsub
setor" "(" value "," default ")"
>
> Returns the value if it exists or a given default value.
>
> Syntax: "ifsetor" "(" variable [ "," expression ] ")"
>
> Semantic:
> - The value in q
Hello Christian,
Friday, April 16, 2004, 10:10:01 PM, you wrote:
> Derick Rethans wrote:
>> isset() works on a variable only too, so this behavior matches already
>> existing behavior.
> Hmm... this brings up another idea:
> Extend isset to have this behaviour. Funnily enough when I was thinking
Derick Rethans wrote:
isset() works on a variable only too, so this behavior matches already
existing behavior.
Hmm... this brings up another idea:
Extend isset to have this behaviour. Funnily enough when I was thinking
about such a feature I wished I could call it isset. And now I realize
that w
On Fri, 16 Apr 2004, Marcus Boerger wrote:
> [RFC] ifsetor operator
>
> Hello List,
>
> i also agrre that an internal function is much better. And here is
> it as such an internal function (that does not result in an expensive
> function call).
>
> Synopsis: "ifsetor" "(" value "," default ")"
lt value.
Syntax: "ifsetor" "(" variable [ "," expression ] ")"
Semantic:
- The value in question must be a variable.
- The default value can be any expression.
- The default value can be omitted in which case NULL will be used.
http://marcus-boerger.de/php/
On Fri, 16 Apr 2004, Christian Schneider wrote:
> Marcus Boerger wrote:
> > [RFC] ifsetor operator
> >
> > Synopsis: "ifsetor" "(" value "," default ")"
> > Returns the value if it exists or a given default value.
> > Syntax: "ifsetor" "(" variable [ "," expression ] ")"
> > Semantic:
> > -
Marcus Boerger wrote:
[RFC] ifsetor operator
Synopsis: "ifsetor" "(" value "," default ")"
Returns the value if it exists or a given default value.
Syntax: "ifsetor" "(" variable [ "," expression ] ")"
Semantic:
- The value in question must be a variable.
I'd prefer to not have this restrict
ue if it exists or a given default value.
Syntax: "ifsetor" "(" variable [ "," expression ] ")"
Semantic:
- The value in question must be a variable.
- The default value can be any expression.
- The default value can be omitted in which case NULL wil
>Should be fixed now.
>Derick
It isn't fixed because tidy tries to open NULL :)
Please apply my patch that (hoppefully) fixes the problem. (I've tested it!)
Nuno
Index: tidy.c
===
RCS file: /repository/php-src/ext/tidy/tidy.c,v
retri
On Fri, 16 Apr 2004, Nuno Lopes wrote:
> This simple code:
> new tidy();
> ?>
>
> echoes:
> // note these funny characters
> Warning: tidy::__construct(Xâââ): failed to open stream: No such file or
> directory in /home/Nuno/php5/sapi/cli/tidy.php on line 2
Should be
Hello John et all,
Before giving my opinion about the exceptions and errors in tidy, there are
two errors that need to be corrected first:
*Win32 build is broken:
tidy.c
..\php_build\include\libtidy\platform.h(473) : warning C4005: 'strcasecmp' :
macro redefinition
Zend\zend_config.w32.
John Coggeshall wrote:
Exceptions from use. I'm not prepared to do that, a failure to open a
file is an exception in OO-world and that's what should be there.
No! OO and exceptions are two completely different things. One is about
data encapsulation and one is about error handling. OO can happily
On Fri, 2004-04-16 at 12:44, Derick Rethans wrote:
> I disgree with this behavior too. E_WARNINGs were never supposed to
> abort a script, that's what we have E_ERRORs for. (Making E_ERROR an
> exception in an OO context is fine, as when it's unhandled it should
> abort the script, just like in PHP
On Fri, 16 Apr 2004, Christian Schneider wrote:
> John Coggeshall wrote:
> > the best compromise I can reach without discarding exceptions entirely,
> > which I believe is even more wrong for OO code.
>
> I disagree. I lost track over the last couple of days, what is everyone
> else's view on this
John Coggeshall wrote:
the best compromise I can reach without discarding exceptions entirely,
which I believe is even more wrong for OO code.
I disagree. I lost track over the last couple of days, what is everyone
else's view on this?
- Chris
--
PHP Internals - PHP Runtime Development Mailing
On Fri, 2004-04-16 at 12:01, Christian Schneider wrote:
> I think this is wrong.
> For E_WARNING the program flow continues unchanged whether you handle
> the return value of e.g. fopen or not.
> For exceptions you _have_ to handle it, otherwise your program aborts.
> Two different things.
I agre
John Coggeshall wrote:
E_WARNINGs are exceptions.
I think this is wrong.
For E_WARNING the program flow continues unchanged whether you handle
the return value of e.g. fopen or not.
For exceptions you _have_ to handle it, otherwise your program aborts.
Two different things.
- Chris
--
PHP Intern
On Fri, 16 Apr 2004, Uwe Schindler wrote:
> Appended a patch to the sybase extensions, that set the default value for
> the sybase appname to ("PHP " PHP_VERSION). I have seen that in PHP 4.3.6
> where this variable is statically set to "PHP 4.0" (!!!). In the tree of
> PHP5 it is a little bit bet
On Fri, 2004-04-16 at 03:32, Derick Rethans wrote:
> Do you mean E_ERRORS become exceptions or also E_WARNINGS? E_WARNINGS
> should never become exceptions as it's a non-fatal error.
E_WARNINGs are exceptions. If you look at the code with the patch
applied, I've downgraded all truly minor error co
Appended a patch to the sybase extensions, that set the default value for
the sybase appname to ("PHP " PHP_VERSION). I have seen that in PHP 4.3.6
where this variable is statically set to "PHP 4.0" (!!!). In the tree of
PHP5 it is a little bit better when this is set to "PHP 5", but the perfect
On Fri, 16 Apr 2004, Enrico Weigelt wrote:
> I'm currently thinking about ways to integrate several other
> languages beside php into the zend engine.
>
> For example perl and php seem to be quite similar. Some perl
> experts told me, there're some things in perl which php semantically
> does not
On Fri, 16 Apr 2004, Enrico Weigelt wrote:
> For example perl and php seem to be quite similar. Some perl
> experts told me, there're some things in perl which php semantically
> does not support, especially for OPP, but perhaps these come w/ php-5 ?
See http://www.zend.com/php5/articles/php5-per
On Fri, 16 Apr 2004, Enrico Weigelt wrote:
> I've often got the problem that a larger application behaves unclear
> if some of the include()'d/require()'ed scripts has some syntax error.
> It seems that the all the code is executed until this require-statement
> where the parse fails. If its an in
Hi folks,
I'm currently thinking about ways to integrate several other
languages beside php into the zend engine.
For example perl and php seem to be quite similar. Some perl
experts told me, there're some things in perl which php semantically
does not support, especially for OPP, but perha
Hi folks,
I've often got the problem that a larger application behaves unclear
if some of the include()'d/require()'ed scripts has some syntax error.
It seems that the all the code is executed until this require-statement
where the parse fails. If its an include() then it seems execution
procee
On Fri, 16 Apr 2004, Kenneth Schwartz wrote:
> Examples:
>
> Outputs the RFC formatted date (current date/time)
>
>
> Outputs the RFC formatted date of the element as the unix
> timestamp
>
> I just wanted to be sure of what I've gathered from testing and the
> source that the usage of both fun
I'm documenting the new XSL extension and needed a little clarification
on the two XSL functions in the PHP namespace [function() and
functionString()]. In what case would either of these XSL functions be
called? As I understand it php:function() only allows string parameters
to the handling PHP
Hi Eric,
I don't see very much value in such an option and I doubt it would help
run-tme very much. In any case, the access control is very much part of the
infrastructure and it can't just be skipped very easily.
Andi
At 11:32 AM 4/16/2004 +0200, Eric Daspet wrote:
Hi,
Is it possible or plan
Hi,
Is it possible or planned to have a php.ini option in order to disable
interfaces and access control ? something like assert.active for assertions.
What I mean is something like a option "access_control.active". If it is
disabled then PHP do not check private/public/protected access, do not
On Fri, 16 Apr 2004, Andi Gutmans wrote:
> At 02:21 PM 4/15/2004 -0400, Sean Coates wrote:
> >Andi Gutmans wrote:
> >>It could be implemented but I don't see the big advantage over $bar ? 0 :
> >>$base
> >>It's one character...
> >>oes to GCC and its C extension).
> $bar ? : $baz;
>
On Thu, 15 Apr 2004, John Coggeshall wrote:
> - All errors were re-evaluated, and those (such as a bogus config
> option) were demoted to E_NOTICE or promoted to E_ERROR as
> necessary
> - Those errors which are truly E_WARNING will behave as such when
> called from a procedural co
I'm not sure how much Java code you have seen/written but this tends to
lead to a million of empty try/catch statements which only lead to a false
sense of security because in practice, you are barely handling any exceptions.
At 11:05 AM 4/16/2004 +1200, Jevon Wright wrote:
> Guys, I'm am not fo
66 matches
Mail list logo
