From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id WAA31533; Mon, 28 Jun 2004 22:00:54 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id WAA31519 for ; Mon, 28 Jun 2004 22:00:52 +0200 (MET DST) X-SPAM-Warning: Sending machine is listed in blackholes.five-ten-sg.com Received: from eposta.kablonet.com.tr ([62.248.102.66]) by nez-perce.inria.fr (8.12.10/8.12.10) with SMTP id i5SK0oEV021538 for ; Mon, 28 Jun 2004 22:00:51 +0200 Received: (qmail 76484 invoked by uid 1007); 28 Jun 2004 20:07:23 -0000 Received: from exa@kablonet.com.tr by eposta.kablonet.com.tr by uid 0 with qmail-scanner-1.21 (clamdscan: 0.70-rc. Clear:RC:0(81.214.24.132):. Processed in 0.533323 secs); 28 Jun 2004 20:07:23 -0000 Received: from unknown (HELO orion) (exa@kablonet.com.tr@81.214.24.132) by 0 with SMTP; 28 Jun 2004 20:07:20 -0000 From: Eray Ozkural Reply-To: erayo@cs.bilkent.edu.tr Organization: Bilkent University CS Dept. To: =?iso-8859-1?q?=A3ukasz_Dobrek?= Subject: Re: [Caml-list] Re: Efficient C++ Interfacing? Date: Mon, 28 Jun 2004 22:58:24 +0300 User-Agent: KMail/1.6.51 Cc: caml-list@inria.fr References: <3a4641a78693342be4a5f7172e068f53@remailer.frell.eu.org> <200406082349.18131.exa@kablonet.com.tr> <20040608211914.GA13251@pld-linux.org> In-Reply-To: <20040608211914.GA13251@pld-linux.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <200406282258.24202.exa@kablonet.com.tr> X-Miltered: at nez-perce with ID 40E078F2.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; eray:01 ozkural:01 caml-list:01 interfacing:01 2004:99 2004:99 eray:01 ozkural:01 caml-list:01 interfacing:01 toolkit:01 namespaces:01 typedefs:01 bug:01 typedefs:01 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk On Wednesday 09 June 2004 00:19, Łukasz Dobrek wrote: > On Tue, Jun 08, 2004 at 11:49:18PM +0300, Eray Ozkural wrote: > > Date: Tue, 8 Jun 2004 23:49:18 +0300 > > From: Eray Ozkural > > Subject: Re: [Caml-list] Re: Efficient C++ Interfacing? > > To: Fritz Wuehler > > Cc: caml-list@inria.fr > > > > On Tuesday 08 June 2004 18:02, Fritz Wuehler wrote: > > > > Sure but this is a C++ code generator > > > > > > No, see the Overview. > > > "OpenC++ is a toolkit for C++ translators and analyzers." > > > > Good. I had checked out OpenC++ but I don't know the current state so let > > me ask. > > > > 1. Is it 100% ISO C++ compatible? > > Nope, appart of the fact that I have not seen a 100% ISO compatibile > compiler yet, this one is for shure not one of them. > > I watched it once carefully, now I don't remember so well all the > problems, but for the record: > - It won't parse namespaces aliases. > ( namespace identifier = org_namespace_name ; ) > - It's mechanism of type resolution is not supporting typedefs. > - It's mechanism which is suppose to find for a member template function > definition its declaration in the class definition, will not work > if the names of the template parameters differ in this two cases: > template< class T > > class A > { > int f(); > } > > template > int A::f(){ return 1 ; } > > there was more but It is all I could find out again now. Okay, thank you very much for the information. The member template function bug should not matter too much, because as discussed in another thread, interfacing C++ templates from ocaml is awkward and unreliable, it seems practically impossible at the moment. I wonder what the INRIA team thinks about it, is it theoretically impossible to interface C++ template functions? The other bugs do not sound nasty, but in a large library, a host of typedefs and aliases are likely to be found. Namespaces aren't used like as in boost, in Qt/KDE libs, but I expect their use to increase (as in KDevelop code), and there is probably a lot of typedefs (although I can't tell just how much in the interfaces), especially the latter would be a serious problem. I think the best for me is to try these parsers systematically on the target code, and see if they fail. There does not seem a better recourse. The ANTLR C++ parser seems impressive, it's said to actually parse MFC libraries IIRC, it was also being used in KDevelop (the C++ support is a critical component apparently). The only sad thing about these systems is that they are not written in ocaml. :) > Anyway I think it is an excellent project and can be very usefull. > In hope it helps Thanks again. I'm now getting the impression that I need to complete my self-training of ANTLR parser generator as well as OpenC++. Best Regards, -- Eray Ozkural (exa) Comp. Sci. Dept., Bilkent University, Ankara KDE Project: http://www.kde.org http://www.cs.bilkent.edu.tr/~erayo Malfunction: http://malfunct.iuma.com GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners