Re: Compile error with 3.0.11 snmp.c on SGI IRIX 6.5
| From: | Sascha Schumann | Date: | Sun, 11 Jul 1999 10:06:45 +0000 |
| Subject: | Re: Compile error with 3.0.11 snmp.c on SGI IRIX 6.5 | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-8355@lists.php.net to get a copy of this message | ||
On Sun, Jul 11, 1999 at 01:26:25AM -0400, Steven Lawrance wrote:
> When compiling PHP 3.0.11 with SNMP support, the compiler (SGI's proprietary
> 64-bit compiler, presumably compiling 32-bit code with PHP due to the year
> 2039 bug) stops compiling when it comes across seven "return" statements
> inside of void functions. This, I think, would probably cause any compiler
> to complain unless if that option is disabled. Removing the "return" from
> the statements fixed the problem and it compiled.
The RETURN_* statements are necessary to control program flow. I
don't see any reason why the compiler should complain, if he sees
a macro such as RETURN_FALSE:
#define RETURN_FALSE {var_reset(return_value); return;}
The RETURN_* macros don't return(anything). They only set
return_value.
What for error messages does the compiler generate?
> For a web page, I would like to be able to set a value using SNMP. Are
> there any plans to make a function such as snmpset()? I'm thinking about
> just adding it to the code for this project and will then upload it to the
> CVS tree if no one objects..
We accept code contributions...
--
Regards,
Sascha Schumann
Consultant