Hi, Andi!
First at all, I must say it is a hard topic, and
there will be many points of view about it.
On Thu, 17 Feb 2011, Andi Jahja wrote:
> Let us reach a point :
> "What Are Core Libraries"
> I'd say:
> "Core libraries are libraries which are required to build a basic
> xHarbour application."
IMHO,
"Core libraries are libraries INCLUDED in the
package (xHarbour). It can be a big package."
> Example:
> /* hello.prg */
> proc main()
> ? "Hello World"
> The above program can be built _without_ CGI, TIP and CT, hence CGI, TIP
> and CT are not entitled to be classified as CORE lib.
> OTOH, the above two-line-program cannot be built without common.lib,
> rtl.lib, vm.lib etc. etc. That means common.lib, rtl.lib, vm.lib etc.
> etc. are CORE libraries.
> Simple, is it not?
Once again, "What is a BASIC application?".
According to your sample, you can move to contrib/
all Windows-specific functions, included DLL and OLE
(they can't be considered as BASIC functions because
they can't work on Linux).
And, you can move out MD5, XML, ZLIB, crypt,
NUMTOHEX*, and RDD functions, too.
> If others have different views, please speak up. I'd love to have my
> brain refreshed.
My two cents.
Atte.
Vic
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
