Graeme Geldenhuys wrote:
Hi,
I use the xlib.pp unit a lot. As far as I understand it and many
others like it was created with a automated tool. As I use the
functions, I thought I could start changing the para1, para2... to
more descriptive parameter names. This makes it much easier to code
Graeme Geldenhuys wrote:
1)
function XSetSelectionOwner(ADisplay:PDisplay; ASelection:TAtom;
AOwner:TWindow; ATime:TTime):cint;cdecl;external libX11;
or maybe
2)
function XSetSelectionOwner(display:PDisplay; selection:TAtom;
owner:TWindow; time:TTime):cint;cdecl;external libX11;
My
Zitat von Graeme Geldenhuys [EMAIL PROTECTED]:
Hi,
I use the xlib.pp unit a lot. As far as I understand it and many
others like it was created with a automated tool. As I use the
functions, I thought I could start changing the para1, para2... to
more descriptive parameter names. This
Hi,
I use the xlib.pp unit a lot. As far as I understand it and many
others like it was created with a automated tool. As I use the
functions, I thought I could start changing the para1, para2... to
more descriptive parameter names. This makes it much easier to code
if you use something like
On 01/02/2008, Mattias Gärtner [EMAIL PROTECTED] wrote:
My preference is 1). What's your thoughts?
Parameter names are needed by many headers.
Why not write a tool, that does it semi-automatically?
Give it the c file with nice parameter names and the pascal unit and it
replaces
para*
On Feb 1, 2008 6:58 PM, Graeme Geldenhuys [EMAIL PROTECTED] wrote:
I might have asked this before, but why doesn't the h2pas tool put in
the correct parameter names in the first place? I'm sure there must be
some technical reason? :)
I think that h2pas just needs to be improved.
I took a
On Fri, 1 Feb 2008 19:12:19 +0100
Felipe Monteiro de Carvalho [EMAIL PROTECTED] wrote:
On Feb 1, 2008 6:58 PM, Graeme Geldenhuys [EMAIL PROTECTED]
wrote:
I might have asked this before, but why doesn't the h2pas tool put
in the correct parameter names in the first place? I'm sure there
