Le 24/04/2011 21:48, NdK a écrit : > On 24/04/2011 13:17, Viktor TARASOV wrote: > >> The using of SC_PKCS15INIT_MAX_OPTIONS is not appropriate in this context. >> SC_PKCS15INIT_MAX_OPTIONS is the number of profile options that can be >> defined as an argument for the pkcs15init operations . > So I can use up to 16 +'option' ? :) > >> If you want to 'marconize' the raw value, you should introduce a new macro, >> something like > Ok. Done that. Attached. > I think that's always better to use symbolic constants instead of literal > ones. Commited in r5406, thank you.
> >> It's different from SC_MAX_AC_OPS -- maximal number of distinct card >> operations that can be protected by some access condition. > Yup. For these I usually use a typedef enum instead of a series of #define so > that any constant can be included anywhere in the sequence and the limit > stays updated automatically. > Another patch for that is attached. > > BYtE, > Diego. > > > _______________________________________________ > opensc-devel mailing list > opensc-devel@lists.opensc-project.org > http://www.opensc-project.org/mailman/listinfo/opensc-devel -- Viktor Tarasov <viktor.tara...@opentrust.com> _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
