ssues using a home-grown server a few years ago. This page
(http://www.ethereal.com/media.html) has a bit more information
in the differences between the loop-back mechanisms on each
system. You may also want to check that everything is set up
correctly in you
--- Sterling Hughes <[EMAIL PROTECTED]> wrote:
> also, when you start quoting djikstra in a php context, you've
> lost.
>
> goto is fine, fight the power!
s/quoting djikstra/mentioning state machines/
also
s/quoting djikstra/agonising about the algorithmic efficiency of
goto versus switch/
--- Marc Richards <[EMAIL PROTECTED]> wrote:
> 3) So this leaves a function call which begs two questions:
> What do we call it,
[snip]
> These include: ifset(), ifelse(), ifexists() and
[snip]
> nvl(), ifnull() and coalesce() have been proposed because of
> This currently leaves us with a hand ful
> That would satisfy some of the requested feature, but try
> calling ifsetor($my_array['bad key'],
> functionWithSideEffects()).
That could be circumvented (somewhat hackishly, I concede) by
recoding a new function and passing the second arg as the string
"functionWithSideEffects" and using the
Isn't this problem solvable with just a "User Space" function?
$variable exists.');
}
else{
$tmp = $alternate;
echo('no $variable here.');
}
return $tmp;
}
// no errors thrown ...
$nonexistent = ifsetor($nonexistent);
if
--- Nuno Lopes <[EMAIL PROTECTED]> wrote: > Can anybody
take a look into this, please?
>
>From having a look in the source, and more pain with
pgsql than anyone should be subjected to, I think
what's happening is a cross-confusion of two issues.
You're right in that if you call it with three
par
--- Wez Furlong <[EMAIL PROTECTED]> wrote:
> Looking at the opcode handler for exit, it looks
> like you can call
> zend_bailout() to terminate the request.
>
> Note that since exit is an opcode and not a
> function,
> call_user_function won't work.
Thank you very much. A similar thought occurre
Hi all,
I've been working on an extension which contains a
"debugging function". This function uses zend_printf()
to print a list of extension-specific information /
help instructions to the screen, in a similar manner
to phpinfo().
It was pointed out to me that this might be a useful
function to
