On 2/23/11 5:55 AM, Martin Koegler wrote: > Why does the trace/error infrastructure of libjpeg puts all parameters > for formating the message into a structure and then calls via a > pointer a functions (emit_message), which determines, if the message > should be printed?
Not sure. That is inherited behavior from the upstream libjpeg, and it's been that way for decades. Tom Lane would likely be the only one who remembers why it was designed that way. The answer is probably, like many things, that there was a good reason for it at one time but the reason may no longer be valid. Remember that libjpeg v6b still supported 16-bit platforms (Messy-DOS), so there's a lot of esoteric memory management code and other legacy items in there, like the ability to alias all of the functions to 8-character names. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
