hi all, Am Donnerstag, 26. Juni 2008 10:04:47 schrieb Szakáts Viktor:
> Harbour is using a more modular approach [than xhb], > where core is strictly portable and doesn't contain > stuff which could easily live as an independent project. > All this independent and/or non-portable stuff is living > in /contrib. We have more strict naming conventions too, > so most of them now have a different name. > > So for example we don't deal with Windows registry in > code, rather we have a hbw32 lib implementing Windows > specific features. > > We also have CT lib (named hbct), which is living in > contrib. > > Since this is a Harbour list, we're using Harbour terms > and lib names. For best results I'd suggest to use the > Harbour codebase to find things easily :) thanks for explanations - they make it a lot clearer. but - what could be a reason for using xharbour then. - is xharbour just another (clipper-compatible) language - is xharbour a commercial project, while harbour is free - can i use the xharbour reference-guide with harbour - can i use the clipper 5.1 handbook with harbour -- Mit freundlichen Grüßen Fritz Eichelhardt Brückenstr. 1 53545 Linz Tel.: 02644 - 3784 Fax/UMS: 01212 - 517045068 _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
