Hi, Philip, > Von: Philip Martin [mailto:philip.mar...@wandisco.com] > > To do that, I would need to introduce an additional type letter into > > the "bindf" format, because some parameters will still need to be > > int64_t > > I think that is a bad idea unless there is some way to automatically catch > a mismatch between an integer argument and multiple integer format > letters. We regularly made mistakes in svn_error_createf before we added > the gcc stuff to do printf checking. > > I don't know if we can use that for bindf as I'm not sure if it would > handle our "t" that consumes two arguments, but until we have some sort of > automatic checking the fewer format letters the better. While we rely on > manual checking the rule "all bound integers are 64bit" is easier to > verify.
Maybe http://gcc.gnu.org/onlinedocs/gcc/Function-Attributes.html#Function-Attr ibutes helps (scroll down to the "format" section). It seems that allows you to apply custom printf like checking. Best regards Markus Schaber ___________________________ We software Automation. 3S-Smart Software Solutions GmbH Markus Schaber | Developer Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50 Email: m.scha...@3s-software.com | Web: http://www.3s-software.com CoDeSys internet forum: http://forum.3s-software.com Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
