From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,9192417d428824a0
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news1.google.com!news4.google.com!proxad.net!feeder1-2.proxad.net!194.25.134.126.MISMATCH!newsfeed01.sul.t-online.de!t-online.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: Problem with QTAda 3.0 and QTCore4.dll on Windows
Newsgroups: comp.lang.ada
User-Agent: 40tude_Dialog/2.0.15.1
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Reply-To: mailbox@dmitry-kazakov.de
Organization: cbb software GmbH
References: 
 <1660bebd-45ca-4568-b92a-380614d94ecc@c34g2000yqn.googlegroups.com>
  <8ec14209-e505-4873-86b4-294149841777@v25g2000yqk.googlegroups.com>
 <bddbcb0d-d573-4152-899f-d7a700f439f6@m16g2000yqc.googlegroups.com>
 <KWf1n.4151$%54.3403@newsfe22.ams2>
 <199i04cdgiqlc$.1tlj9wnffh6g9$.dlg@40tude.net>
 <ec2d7604-ed68-441e-96f5-5fc946184ad5@j5g2000yqm.googlegroups.com>
Date: Fri, 8 Jan 2010 00:02:38 +0100
Message-ID: <1ph5w4hfwxweu$.1a0r04qtvcqwl.dlg@40tude.net>
NNTP-Posting-Date: 08 Jan 2010 00:02:36 CET
NNTP-Posting-Host: 09b67dd5.newsspool4.arcor-online.net
X-Trace: 
 DXC=Z`77Lb9XNL9;]cDoEWD6A44IUK<Cl32<14Fo<]lROoR18kF<OcfhCO;B8\XIF5o5f3[6LHn;2LCV>[<mhadbfdU;Va>>32Ml<?=;dIn8b6lSG;
X-Complaints-To: usenet-abuse@arcor.de
Xref: g2news1.google.com comp.lang.ada:8662
Date: 2010-01-08T00:02:36+01:00
List-Id: <comp.lang.ada>

On Thu, 7 Jan 2010 14:11:37 -0800 (PST), Vadim Godunko wrote:

> On Jan 7, 1:59�pm, "Dmitry A. Kazakov" <mail...@dmitry-kazakov.de>
> wrote:
>> On Thu, 07 Jan 2010 08:19:17 +0100, Per Sandberg wrote:
>>> The core reason is that the Binary Interface specific the name-mangling
>>> in C++ is different between gcc and MSVC, on top of that the
>>> documentation in the MSVC case is "sparse".
>>
>> That should not be a problem in case of C. One should only make a choice
>> between stdcall and cdecl convention when you make a call from Ada. I guess
>> Qt has plain C interface? Then what happens inside of it is no matter.
>>
> Qt is pure C++ library, there is no C interface provided by it.

Well, the question is whether the interface uses virtual functions and
classes you have to derive from. That would make a real difference.

> QtAda's code includes both C/C++ and Ada code which refers to each
> others in both directions, so it is unpractical to separate it into
> two independent shared libraries to build C/C++ part using MSVC and
> Ada part using GNAT; but mixing of MSVC and GNAT object files in the
> same shared library is not supported now.

I agree. It is the Visual Studio's debugger, which makes MSVC attractive.
Since that won't work with GNAT, there seems to be no reason left to port
Qt into MSVC.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de