A documentation is important also without documenting HB_STATIC_FUNC for now What do you think about using a robodoc for extract from source Also here you see that separing prg and c will be more useful for generating documentation
Is not possible a way of join prg and c file if have same name or similar whit a fixed extension? Mysample.prg and Mysample_linked.c will be part of same module during linking? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maurizio la Cecilia Sent: Friday, June 06, 2008 11:32 AM To: 'Harbour Project Main Developer List.' Subject: R: R: R: [Harbour] HB_STATIC_FUNC Hi Victor, > From a purely practical POV regarding hwgui, the only > thing I don't see here is what makes ANIMATE > class so different from the other classes, that this > problem is present here, but not in other places. > Simply because this was first class in alphabetical order and when i started to make a wiki (hwgui.altervista.org) to give an updated reference guide on hwGUI i've analyzed his code. Other classes don't are affected just because after changing to static the class methods of hAnimate some signal of incompatibility with Watcom/Harbour was raised and i've stopped to implement static methods waiting for a solution, and stopped the documenting on wiki, because in doubt if also to reference the functions or avoid this. _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
