Question actually still stands though. If wine is not inclined to use our
code just because it's in C++, should that stop us from using it? We
already basically split with shell32.
On Tue, May 31, 2016 at 4:45 AM, David Quintana (gigaherz) <
gigaherz(a)gmail.com> wrote:
Wine doesn't wrap C++, they just simply don't
allow C in their codebase,
period. It's annoying.
On 31 May 2016 at 11:32, Ged Murphy <gedmurphy.maillists(a)gmail.com> wrote:
Would it not be better to do all this in C++ and
let wine write a C
interface around it?
When we're trying to move to C++, it seems like a step backwards in order
to support wine's insistence on using C
-----Original Message-----
From: Ros-diffs [mailto:ros-diffs-bounces@reactos.org] On Behalf Of
mjansen(a)svn.reactos.org
Sent: 28 May 2016 17:43
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [mjansen] 71439: [APPHELP] Begin shimlib
implementation. CORE-11329 Implement some macro's and functions that help
when registering shims. These are all written in C, so that wine can use
the shim ...
Author: mjansen
Date: Sat May 28 16:42:57 2016
New Revision: 71439
URL:
http://svn.reactos.org/svn/reactos?rev=71439&view=rev
Log:
[APPHELP] Begin shimlib implementation. CORE-11329 Implement some macro's
and functions that help when registering shims.
These are all written in C, so that wine can use the shim libraries as
well.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev