Re: Running valgrind with Wine

[Mike Hearn]

On Sun, 05 Sep 2004 12:55:33 +0900, Mike McCormack wrote:
> - wine_init( argc, argv, error, sizeof(error) );
> - wine_init( argc, argv, error, sizeof(error), reserve );

It's worth noting that any change to this functions prototype breaks the
Ardour/Wine VST plugin bridge. Last time this issue was raised the change
was reverted.

While we're technically not API stable yet, it's painfully obvious that
1.0 is still a long way away. Stability is a policy rather than a target,
so we've got to start at some point ....

Running valgrind with Wine

[Boaz Harrosh]

Mike Hearn wrote:
> While we're technically not API stable yet, it's painfully obvious that
> 1.0 is still a long way away. Stability is a policy rather than a target,
> so we've got to start at some point ....

I totally agree but that should not stop you from doing things Like:

+    wine_init_ex( argc, argv, error, sizeof(error), reserve );

+        #ifdef __DEEP_DEBUG__
+        #define wine_init wine_init_ex
+        #endif

(Old API code calls new _ex functions. No point in having 2 of them. But that goes with out saying. right?)

The old API is there and a new, freshly compiled programs can see, API for advance uses. SO go for the patch. And do keep API Stability.

Free Life
Boaz