I see that even in hwgui, there are plenty of .c and
.prg files anyway, so I wonder why the mixed ones?
One reason might be that this way, they can make
those C functions 'static' to the .prg file that uses
them (hence the recent question and all the hacking
to achieve this). To me this seems like something
which can be resolved using some internal namespaces,
or other logical distinction between published and
private API. All in all this is a fully regular problem,
present in all projects using more than one source
file, and everyone solves it without mixing.
BTW, hwgui main source folder has two hb_inline()s,
both seems easy to replace with one hb_bit*() call
each, plus there are a few files with BEGINDUMP, no
C code there has any special properties (and only some
of them are 'static') which would prevent moving them
into .c files, IMO. I had similar experience when porting
code with inline C from xhb to Harbour.
Brgds,
Viktor
On 2008.06.05., at 23:54, Massimo Belgrano wrote:
Hi Maurizio
Your problem in hwgui will be resolved isolating c code in external
*.C ?
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
] On Behalf Of Szakáts Viktor
Sent: Thursday, June 05, 2008 7:46 PM
To: Harbour Project Main Developer List.
Subject: Re: [Harbour] HB_STATIC_FUNC
I'd add one more problem with INLINE C code:
I extensively use grep for Harbour and my own projects
too, it's a very powerful tool to locate stuff in the
source.
When I'm looking for C code parts (function names
let's say), naturally I search through *.c files only.
Problem: C code may be hiding inside .prg, too, or
even in .ch. This results in either wrong code updates,
decisions, or in the best, case another pass of grep.
Not to mention all the tools which rightly except
some kind of content in a given file type (most
obvious example is syntax coloring).
So this is IMO just one more thing that makes development
more complicated and error prone, without much gain.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
