A Simple Real World Benchmark for cygwin

[Robb, Sam]

> That's not the point.  The application *may* call CoInit() before
> requesting the first path to a shortcut and it *may* call CoUninit()
> before requesting another path to a shortcut, all in the same thread.

Would creating a seperate thread for the purpose of executing
Cygwin-originated COM calls be an answer?  Wouldn't be as fast
as assuming CoInit has already been called, but would probably
be faster than calling CoInit/CoUninit for every shortcut check.

-Samrobb

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/