Rule as this are important (also if not jet approved) How give importance to this info? How we can know this rule to future harbour developer without reading all messages post in mailing list can restructure doc with information for harbour prg level user from harbour c level developer? Can adopt a external WIKI to make a collaborative work ? can write inside each library information and write a program who extract it ?
2009/2/4 Viktor Szakáts <harbour...@syenar.hu>: > Hi Pritpal, > > For future development a very simple rule can be added: > - If someone needs to access a Windows API function > from .prg code, look in hbwin.lib first, if it's there use it, > if not, implement it there using WIN_<winapi_name>() > naming scheme. Easier said than done I guess :) but > why not try it? _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
