[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Cooperating on .defs API specifications
From: |
Murray Cumming |
Subject: |
Re: Cooperating on .defs API specifications |
Date: |
Tue, 30 Mar 2004 22:27:30 +0200 |
On Tue, 2004-03-30 at 20:47, Xavier Ordoquy wrote:
> On Tue, 2004-03-30 at 19:50, Andreas Rottmann wrote:
> > Hi!
>
> Hi,
>
> > This means everybody interested will be able to check the "defs"
> > directory out, and plug it somewhere into their project tree, just
> > issuing a "tla update" to stay on track. Also, every project may fork
> > off (no write access or whatsoever required, thanks to Arch) and have
> > their local changes and generic improvements, which can be easily
> > merged back.
>
> How do you name your functions ? pygtk binds gtk_tree_view_new as
> gtk.tree_view_new which slightly changes the function name in our .defs
> files.
The defs format does not split up the function name, I think. It just
says what the name is and what object it belongs to. So, I think there's
no problem there.
--
Murray Cumming
www.murrayc.com
address@hidden
- Re: Cooperating on .defs API specifications, (continued)
- Re: Cooperating on .defs API specifications, Murray Cumming, 2004/03/30
- Re: Cooperating on .defs API specifications, Andreas Rottmann, 2004/03/30
- Re: Cooperating on .defs API specifications, Murray Cumming, 2004/03/30
- Re: Cooperating on .defs API specifications, Andreas Rottmann, 2004/03/30
- Re: Cooperating on .defs API specifications, James Henstridge, 2004/03/31
- Re: Cooperating on .defs API specifications, Andreas Rottmann, 2004/03/31
Re: Cooperating on .defs API specifications, Xavier Ordoquy, 2004/03/30
- Re: Cooperating on .defs API specifications,
Murray Cumming <=
Re: Cooperating on .defs API specifications, Shiro Kawai, 2004/03/30