search for: defautmsg

...t know if DIDescriptor are the best thing to use here). ** Summary ** I am starting to think that we should be able to cover the reporting case plus some querying mechanism with something like: void reportSomehtingToFEHandler(enum Reporting Kind, bool IsAbort, <some information>, const char* DefautMsg, <pointer to a list of args to format in the defautMsg>) Where <some information> is supposed to be the class/struct/pointer to the relevant information for this kind. If it is not enough the FE should call additional APIs to get what it wants. This looks similar to the “classical” b...

...e best thing to use here). > > ** Summary ** > I am starting to think that we should be able to cover the reporting case > plus some querying mechanism with something like: > void reportSomehtingToFEHandler(enum Reporting Kind, bool IsAbort, <some > information>, const char* DefautMsg, <pointer to a list of args to format in > the defautMsg>) Personally I dislike losing type safety in this kind of API ("here's a blob of data you must programmatically query based on a schema implied by the 'Kind' parameter & some documentation you read"). I'...

On Mon, Jul 22, 2013 at 2:21 PM, Eric Christopher <echristo at gmail.com>wrote: > >> This is pretty much the same as what Quentin proposed (with the > addition of the enum), isn't it? > >> > > > > Pretty close yeah. > > > > Another thought and alternate strategy for dealing with these sorts of > things: > > A much more broad set of

.... >> >> ** Summary ** >> I am starting to think that we should be able to cover the reporting case >> plus some querying mechanism with something like: >> void reportSomehtingToFEHandler(enum Reporting Kind, bool IsAbort, <some >> information>, const char* DefautMsg, <pointer to a list of args to format in >> the defautMsg>) > > Personally I dislike losing type safety in this kind of API ("here's a > blob of data you must programmatically query based on a schema implied > by the 'Kind' parameter & some documentatio...