Andi, Core libraries are ALL libraries which meet the coding and reliability standards of the core xHarbour AND provide functionality which we would like to offer in the core xHarbour. In contrary contrib libraries are generally either failing to meet the coding and reliability standards of the core project, or provide SPECIALIZED functionality which is therefore not needed by the majority of the xHarbour users community. Additional criteria is PORTABILITY but there are some exceptions in cases where non portable feature is extremely desirable or popular on some platform, such as OLE on Windows.
Ron -------------------------------------------------- From: "Andi Jahja" <andi.ja...@yahoo.co.id> Sent: Thursday, February 17, 2011 8:49 AM To: <l...@xharbour.com.br> Cc: "Ron Pinkas" <ron.pin...@xharbour.com>; <xharbour-developers@lists.sourceforge.net> Subject: Re: [xHarbour-developers] MEMIO > 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." > > 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? > > If others have different views, please speak up. I'd love to have my > brain refreshed. > > Andi > > On Thu, 17 Feb 2011 14:24:07 -0200 > l...@xharbour.com.br wrote: > >> Ron >> >> If i remember correctly, on the changelogs was the motive why this >> modules >> was moved from contrib to core >> >> Regards >> Luiz >> >> > Hi Andi, >> > >> > We generally try to avoid situations where someone reverts changes that >> > other[s] contributed - it seems very aggressive. I believe Luiz was >> > just >> > trying to be friendly. >> > >> > In the future I would recommend some discussion before making >> > structural >> > changes, since it almost always affect others. >> > >> > Most importantly THANK YOU for your enthusiastic contributions. >> > >> > Ron >> > -------------------------------------------------- >> > From: "Andi Jahja" <andi.ja...@yahoo.co.id> >> > Sent: Thursday, February 17, 2011 6:32 AM >> > To: <xharbour-developers@lists.sourceforge.net> >> > Subject: Re: [xHarbour-developers] MEMIO >> > >> >>> not only memio, as also tip, ct,cgi that was wrongly moved back to >> >>> contrib >> >> >> >> If you find it wrong, then you can put it back. You have the write >> >> access, don't you, Luiz? This is xHarbour, not Harbour, you all have >> >> the >> >> same right and freedom without being bound with academic bullshits. :) >> >> >> >> Andi > > ------------------------------------------------------------------------------ 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
