Re: [PATCH] parse-options: fix the description of defval
- From
Ivan Ukhov <ivan.ukhov@gmail.com>
- Date
- Mar 29, 2015, 09:28 UTC
- Message-ID
- <0AC17F77-A324-40FA-9D5A-772C11E3BBDA@gmail.com>
- In-Reply-To
- <CACRoPnTjAu_pyPp2TXZGou=H8mkXBmQqgxGNusjW6u8peEfw6Q@mail.gmail.com>
Hello Paul,
> On Mar 29, 2015, at 11:08 AM, Paul Tan <pyokagan@gmail.com> wrote: > > Actually, it can contain a pointer for OPTION_CMDMODE, OPTION_STRING > and OPTION_FILENAME.
I have checked the definitions of the three macros you mentioned, and it seems that none of them uses defval to store pointers. OPTION_CMDMODE stores chars and integers. OPTION_STRING does not use defval at all (pointers go in a different field of the option struct), and the same applies to OPTION_FILENAME. I am probably missing something; can you please clarify what you mean? Thank you.
Regards, Ivan