'Re: [Kde-bindings] Common work for Qt4 bindings'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bindings
Subject:    Re: [Kde-bindings] Common work for Qt4 bindings
From:       Eric Jardim <ericjardim () gmail ! com>
Date:       2005-09-10 4:28:32
Message-ID: 432ec6c5050909212817fcf599 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

2005/9/10, Marcus <mathpup@mylinuxisp.com>:
> 
> That is not entirely correct. GCCXML does not handle uninstantiated 
> templates.
> Instantiated templates do appear in the output. GCCXML uses GCC for its
> parsing, so it is capable of parsing anything GCC can. It is just that
> uninstantiated templates are not handled by the part that analyzes the 
> parsed
> code and produces the XML.

That is good, so. Now we have something concrete.

I have written an app that reads in GCCXML input and represents the various
> C++ declarations as objects and such. It does not yet handle templates. I
> have not looked at this in a few months. 

My idea is to separate 3 stages:
1 - query the C++ for classes, functions and enums, and all Qt specific info 
(not sure if GCCXML can handle this part)
2 - select which of them will be wrapped with meta-data info, like hints. 
With this hints, everyone can make your own bindings, respecting every 
language features and limitations.
3 - Generate the bindings (this is specific for each language). It may also 
be the Smoke library.

It is written in C#, which seems to
> be hated by anyone who deals with KDE, however.
> 

Hehehe, don't be sad. This work intent is to be language free. That is the 
more important and noble goal. Keep people "tastes" aside.

[Eric Jardim]

[Attachment #5 (text/html)]

2005/9/10, Marcus &lt;<a \
href="mailto:mathpup@mylinuxisp.com">mathpup@mylinuxisp.com</a>&gt;:<div><span \
class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> That is not \
entirely correct. GCCXML does not handle uninstantiated templates.<br>Instantiated \
templates do appear in the output. GCCXML uses GCC for its<br>parsing, so it is \
capable of parsing anything GCC can. It is just that <br>uninstantiated templates are \
not handled by the part that analyzes the parsed<br>code and produces the \
XML.</blockquote><div><br> That is good, so. Now we have something concrete.<br>
&nbsp;</div><br><blockquote class="gmail_quote" style="border-left: 1px solid \
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I have written an \
app that reads in GCCXML input and represents the various<br>C++ declarations as \
objects and such. It does not yet handle templates. I <br>have not looked at this in \
a few months. </blockquote><div><br> My idea is to separate 3 stages:<br>

1 - query the C++ for classes, functions and enums, and all Qt specific info (not \
sure if GCCXML can handle this part)<br>

2 - select which of them will be wrapped with meta-data info, like hints. With this \
hints, everyone can make your own bindings, respecting every language features and \
limitations.<br>

3 - Generate the bindings (this is specific for each language). It may also be the \
Smoke library.<br> <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">It is written in C#, which seems \
to<br>be hated by anyone who deals with KDE, however. <br></blockquote></div><br>
Hehehe, don't be sad. This work intent is to be language free. That is
the more important and noble goal. Keep people &quot;tastes&quot; aside.<br>
<br>
[Eric Jardim]<br>

_______________________________________________
Kde-bindings mailing list
Kde-bindings@kde.org
https://mail.kde.org/mailman/listinfo/kde-bindings

[prev in list] [next in list] [prev in thread] [next in thread] 