When you @ "at" a command (supress error messaging) within a function, is
the scope of the @ within the function?
Example:
CloseODBC(1);
# is error message supressed here too?
function CloseODBC($connection_id)
{
# error messaging supressed
@odbc_close($connection_id);
}
--
PHP G
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have the solution to my problem here but can't see why i need it?
this snippet takes $AuthId from a form and but does not work (doesn't
seem to pass it to the function)
case "edit":
$tips->get_author($AuthId);
$content
My understanding is, it simple supress the any messages generated from
the result. So I guess it is local.
Karl J. Stubsjoen wrote:
> When you @ "at" a command (supress error messaging) within a function, is
> the scope of the @ within the function?
>
> Example:
>
>
> CloseODBC(1);
>
> # is
On Wednesday 14 February 2001 17:36, Karl J. Stubsjoen wrote:
> When you @ "at" a command (supress error messaging) within a function,
> is the scope of the @ within the function?
>
> Example:
>
>
> CloseODBC(1);
>
> # is error message supressed here too?
>
>
> function CloseODBC($connection_id)
>
come from, am I
right ?
so you use :
$where = @where($user);
this will always return true no matter what happen
Cheers,
Maxim Maletsky
-Original Message-
From: Karl J. Stubsjoen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 15, 2001 1:37 AM
To: PHP Mailing List
Subject: [PH
On Friday 16 February 2001 04:19, Maxim Maletsky wrote:
> It will escape the error ... or better say you force the function to
> always return true.
[...]
> $where = @where($user);
>
> this will always return true no matter what happen
Bullshit (sorry. I just *had* to say this :). From the manual
According to the PHP 4 docs all variables are global unless within a
function. I've got the following test code which should output 2, but
outputs 1. The while loop creates it's own class object (which seems strange
since it isn't explicitly instantiated by my code; I would think it would
cause er
On Mon, 2002-03-11 at 18:51, Randall Perry wrote:
> According to the PHP 4 docs all variables are global unless within a
> function. I've got the following test code which should output 2, but
> outputs 1. The while loop creates it's own class object (which seems strange
> since it isn't explicitl
rch 11, 2002 6:52 PM
To: [EMAIL PROTECTED]
Subject: [PHP] Scope problem in while loop
According to the PHP 4 docs all variables are global unless within a
function. I've got the following test code which should output 2, but
outputs 1. The while loop creates it's own class object (w
Whoops, you're right. Classic 'C' mistake using = instead of ==. Never mind
:(
> On Mon, 2002-03-11 at 18:51, Randall Perry wrote:
>> According to the PHP 4 docs all variables are global unless within a
>> function. I've got the following test code which should output 2, but
>> outputs 1. The whi
Hi all,
a quick question about using PHP's objects, specifically in terms of the
scope of class attributes:
Normally, in PHP, a variable in a function is local to that function and
is NOT a reference to a similarly-named variable outside the function,
right? To the best of my knowledge, ther
If anyone read this post, you probably already forgot about it, but I
just wanted to clarify that I found the source of the problem and it was
a coding mistake on my part, not a problem with PHP's array
implementation.
Erik
On Thursday, June 6, 2002, at 03:11 PM, Erik Price wrote:
> Hi
12 matches
Mail list logo