Hi, I find that : for table columnar objects having read-create access, smilib returns SmiNode structure having the following two members as access=SMI_ACCESS_READ_WRITE create=0
where as I expected create=1
Due to this we incorrectly get the access as ReadWrite instead of ReadCreate for some objects having ReadCreate access. Can anybody explain the reason ?
However, for table-entry object ( which is generally not-accessible, If I mention access as read-create, smilib returns expected correct values of ReadCreate)
kr, abhay
-- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.
Deshmukh, Abhay writes:
Deshmukh> Hi, I find that : for table columnar objects having Deshmukh> read-create access, smilib returns SmiNode structure having Deshmukh> the following two members as Deshmukh> access=SMI_ACCESS_READ_WRITE create=0
Deshmukh> where as I expected create=1
Deshmukh> Due to this we incorrectly get the access as ReadWrite Deshmukh> instead of ReadCreate for some objects having ReadCreate Deshmukh> access. Can anybody explain the reason ?
The create bit is set on the row node. This reflects the fact that row creation is actually a row property rather than a per-column property. See the tools/dump-smi.c file on how to demangle this back into the SMIv2 notation.
/js
participants (2)
-
Deshmukh, Abhay -
Juergen Schoenwaelder