• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 22 subscribers
  • Views 804 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Re: About structure definition

Stefan Fricke

To avoid flames, if I try to reply a cannot find a 'post' nor 'preview' button,
so I must start a new message thread.
Sorry for the inconvinience.

Dear KEIL Support Team, can you solve the
problem with posting ?

----------------------------------------
It simply sets the all MInfo.'values' to a defined status, that is right.
It was probably used with the intention to
preset more than one variable of type
MfCmdInfo.

Example:

MfCmdInfo MInfo, MSecondInfo, MAnotherInfo;

ResetInfo(MInfo);
ResetInfo(MSecondInfo);
ResetInfo(MAnotherInfo);

will result in:

MInfo.cmd=0
MInfo.status=MI_OK;
.....

MSecondInfo.cmd=0;
MSecondInfo.status=MI_OK;
.....

MAnotherInfo.cmd=0;
MAnotherInfo.status=MI_OK;
.....

For the rest I'm confirm with Drew, it is a simply substitution macro and if we misunderstand you, let us know , what
exactly you want to try.

Stefan

  • 0

    "To avoid flames, if I try to reply a cannot find a 'post' nor 'preview' button,
    so I must start a new message thread."

    The buttons are there - you just have to scroll way over to the right to find them!

    "Dear KEIL Support Team, can you solve the
    problem with posting ?"

    The problem lies in the original post - because it was so damned wide!
    The buttons just position themselves at the midpoint of the width!

    "It was probably used with the intention to preset more than one variable of type"

    Which begs the question: why use a macro rather than a true function, or memset?

  • 0 in reply to Andy Neil

    Hi Andrew ,

    thanks your are right, with your hints, about the buttons. ;-)

    Stefan ( I keep it in mind )

  • 0 in reply to Stefan Fricke

    "Which begs the question: why use a macro rather than a true function, or memset?"

    To use a function, you'd have to pass a pointer to the structure; maybe the original author didn't understand how to use structure pointers?

    Or maybe he was worried about efficiency - in which case memset would have been better.