of last SNMP-related error
* formatting markup
* some fixes in max_oids logic: NULL will set it to default value,
do not allow non-positive user-supplied values
* unit tests for changes
MFH: . Renamed the function to snmp_set_oid_output_format() which describes
MFH: it's behaviour better. Old one was left as an alias for it.
MFH: . Added 2 new constants: SNMP_OID_OUTPUT_FULL and SNMP_OID_OUTPUT_NUMERIC
MFH: - Fixed some memleaks
This is a basic SNMP operation that retrieves the next value as the
one provided to the command.
NOTE: snmpgetnext does not follow the official naming convetions of
functions, but now it is equal to it version 1 equivalents snmpget
and snmpset.
I also would like to reserve the snmp_getnext for a function to
which a session can be given instead of the multiple values to
create the session internally. (Work in progress).
The patch enables control on the way the values are returned
into the PHP script, instaed of always strings. Also the
type of the value is now returned when configured to do so.
This enables better management scripts to do more automatic
processing and value calculations.
(By default the values are returned as strings, as was before)
This splits the old php_snmp function into an argument parsing part and
a data retrieval part. The data retrieval part is reused for SNMPv3.
SNMPv3 has only a different argument parsing.
THe code is not extremely beautiful, but having NET-SNMP and
UCD-SNMP support creates this. :-(
Documentation must still be done.
Draft 3 of IEEE 1003.1 200x, "2.2 The Compilation Environment"
All identifiers that begin with an underscore and either an uppercase
letter or another underscore are always reserved for any use by the
implementation.
- small optimizations
- delete that switch case in php_snmp
=The different functions are now in the PHP_FUNCTION declaration thingies
- If-else blocks have brackets
