Fwd: Re: [GCC-XML] Function bodies

[Daniel J. Lauk]

Sorry, previous mail didn't work (too large w/ attachment).

I hope this is better now. I left out pygccxml changes (those go directly to 
Roman now).

Best wishes,
DJ

----------  Weitergeleitete Nachricht  ----------

Subject: Re: [GCC-XML] Function bodies
Date: Mittwoch, 5. Juli 2006 17:49
From: "Daniel J. Lauk" <dj at djlauk.de>
To: gccxml at gccxml.org

Hi.

I wanted to publish my changes under the zlib/libpng license. I am not a
lawyer, so all I can do is hope, that this does not conflict with gcc's or
gccxml's licensing model.
If so, please contact me and I'm sure we'll find a suitable solution.

I run this grep to find the files, I modified (I marked them as such):
grep -l -i lauk -R .

I hope, I did not miss (to comment) anything.
I furthermore hope attaching files works... *crossingfingers*

So, to sum it up: There you go. Good luck! ;-)

Feel free to ask any questions, though I'm not checking this mail account
regularly for the time being. I'm not much at home anyway. :-S
So chances are, answers will take longer than you'd like, but I *will* answer
any non-spam-ish mails on the subject that haven't been answered.

Most probably the "GCC internals" documentation will help more than my
comments anyway ;-)

Best regards,
DJ

Am Mittwoch, 5. Juli 2006 05:15 schrieb David Genest:
> Hi,
>
> I must add my vote for this function body project, it would be very
> usefull.
>
> David.
>
> On 6/28/06, Balasubramanyam, Shivakumar <sbalasub at qualcomm.com> wrote:
> > I agree. I would certainly be interested in looking at the code.
> >
> > >-----Original Message-----
> > >From: gccxml-bounces+sbalasub=qualcomm.com at gccxml.org [mailto:gccxml-
> > >bounces+sbalasub=qualcomm.com at gccxml.org] On Behalf Of Roman Yakovenko
> > >Sent: Wednesday, June 28, 2006 10:53 AM
> > >To: Daniel J. Lauk
> > >Cc: gccxml at gccxml.org
> > >Subject: Re: [GCC-XML] Function bodies
> > >
> > >On 6/28/06, Daniel J. Lauk <dj at djlauk.de> wrote:
> > >> Hi.
> > >>
> > >> Well... I did some work on this because of my graduation thesis. What
> >
> > I
> >
> > >> developed so far is an (almost) 1-to-1 dump of GCC's syntax/code
> >
> > tree.
> >
> > >> Because licensing might be an issue and because I got a job right
> >
> > after
> >
> > >> graduation ( :-) ) I did not publish my code, yet.
> > >>
> > >> I think it would be most benefitial if it was refactored in such a
> >
> > way
> >
> > >that
> > >
> > >> the structure would be the equivalent of C(++) syntax. I did not
> >
> > complete
> >
> > >on
> > >
> > >> this because I did not have the C++ syntax available and it wasn't
> > >
> > >necessary
> > >
> > >> for my thesis (and time's always short on thesises ;-) ).
> > >>
> > >> So, let me know if you still need the code and would like to work on
> >
> > it.
> >
> > >It could be nice if you can publish the code. Users will decide
> > >whether they can use
> > >the code or not, but at least the functionality will be available.
> > >
> > >--
> > >Roman Yakovenko
> > >C++ Python language binding
> > >http://www.language-binding.net/
> > >_______________________________________________
> > >gccxml mailing list
> > >gccxml at gccxml.org
> > >http://www.gccxml.org/mailman/listinfo/gccxml
> >
> > _______________________________________________
> > gccxml mailing list
> > gccxml at gccxml.org
> > http://www.gccxml.org/mailman/listinfo/gccxml

-------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gccxml.tar.bz2
Type: application/x-tbz
Size: 24075 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/gccxml/attachments/20060705/f2bc1cc8/attachment.bin>