Jump to content

Recommended Posts

Hi.

I think that the explanation of setting values with password could be improved.

void cci_param_if::set_cci_value(const cci_value &, const void* pwd, const cci_originator& orig);

There are some statements saying that 'Writes to a locked parameter are rejected'. But with the pwd overload of set_cci_value, it is possible to write to a locked parameter without being rejected.

The LRM should be more clear about this:

Will the param be unlocked temporarily or not? If not, user needs to be aware that write callbacks can occur and latest originator can change even in locked state.

Another aspect is reset: Should it be allowed to reset a locked param without password?

 

Greetings

Ralph

Share this post


Link to post
Share on other sites

Ralph, thanks for your thorough review and very helpful feedback. The CCI WG agrees with your suggestions and will incorporate them into the LRM. reset() has no effect on a locked parameter (requiring that it explicitly be unlocked first) and we intend to add an example that demonstrates this.

Thanks again,
Trevor Wieman
CCI WG Chair

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...