About the range of index

[Frank Fock]

Hi Robert,

Please read the license agreement of AgentGen Standard
carefully. It is only free for non-commercial use!

If v is always 0 then it could also be a type mismatch
(that should be detected before by the super-class as
I wrote before).

Best regards,
Frank Fock

罗先录 wrote:
> Hi,Frank
> Sorry for confusing question.
> 
> First, I using the stardard version 1.5 of AgentGen.
> Second, My question is when I debugging the value_ok function,
> I find that v variable always is zero which value_ok is checking.
> So, any value is OK after checking.
> 
> Best regards,
> Robert
> 
> 
> ----- Original Message ----- 
> From: "Frank Fock" <Frank.Fock____t-online.de>
> To: "罗先录" <luoxianlu____huawei.com>
> Cc: <agentpp-dl____agentpp.com>
> Sent: Saturday, May 17, 2003 7:26 PM
> Subject: Re: About the range of index
> 
> 
> 
>>Hi Robert,
>>
>>which version of AgentGen are you using? What is
>>exactly your question? The code works and it is
>>called when MibLeaf::prepare_set_request is executed.
>>So either, you do not call that method in your
>>derived hwNmFaultQueryConditionDeviceType (and thus
>>you have removed that call) or you do not test the
>>right object.
>>
>>BTW, your company has bought a license for AgenPro
>>yet. Using it anyway, not only violates international
>>laws, it is also a guarantee to not receive any
>>support.
>>
>>Best regards,
>>Frank Fock
>>
>>罗先录 wrote:
>>
>>>Hi,Frank
>>> 
>>>When I set the range of index and other variables, agentGen will 
>>>generate code like these:
>>> 
>>>boolean hwNmFaultQueryConditionDeviceType::value_ok(const Vbx& vb)
>>>{
>>> long v;
>>> vb.get_value(v);
>>> if (!(((v >= 0) && (v <= 255))))
>>>   return FALSE;
>>> 
>>> file://--AgentGen BEGIN=hwNmFaultQueryConditionDeviceType::value_ok
>>> file://--AgentGen END
>>> return TRUE;
>>>}
>>> 
>>>But it can not work before commit_set_request;I can set value above 255 
>>>freely.
>>>Would you PLS give me some explanation?
>>> 
>>>warm regards,
>>>~Robert
>>
>>
>>
>>