-Messaggio Originale-
Da: bhays bh...@abacuslaw.com
A: 'xHarbour-Developers' xharbour-developers@lists.sourceforge.net
Data invio: mercoledì 7 gennaio 2009 2.33
Oggetto: Re: [xHarbour-developers] Current CVS stable?
Enrico:
Thanks. Is it possible for us to catch this at link time
-Messaggio Originale-
Da: Enrico Maria Giordano e.m.giord...@emagsoftware.it
A: bhays bh...@abacuslaw.com; 'xHarbour-Developers'
xharbour-developers@lists.sourceforge.net
Data invio: mercoledì 7 gennaio 2009 9.31
Oggetto: Re: [xHarbour-developers] Current CVS stable
Patrick:
I understand. But if we're going to release a build that causes
unidentifiable crashing, shouldn't we consider putting something in the
build to identify it?
Wouldn't incrementing the PCode version accomplish this, even if it was an
item structure change instead of pcode change that
Hello,
Wouldn't incrementing the PCode version accomplish this, even if it was an
item structure change instead of pcode change that causes the crash?
I fully agree with PCode version. The structure change is quite dangerous
if we do not do it.
But than all 3rd party LIB's need to be
Very stable! :-)
One important status now compared to Harbour :-):
xHarbour gently free VIRTUAL MEMORY upon application exit while
Harbour, at the present moment, does not.
(As usual, I use MEMPROOF with BCC build to make a test.)
Congrats for the xHarbour crews!
--
Andi
On Tue, 6 Jan
Andi,
Very stable! :-)
Than I think the moment arrived to start preparing for a new release, right?
This has been on the table for long now.
Patrick
--
Check out the new SourceForge.net Marketplace.
It is the best
That is, once we fixed brian's GPF off course! ;-)
On Wed, Jan 7, 2009 at 11:51 AM, Patrick Mast, xHarbour.
patrick.m...@xharbour.com wrote:
Andi,
Very stable! :-)
Than I think the moment arrived to start preparing for a new release, right?
This has been on the table for long now.
Patrick
On Wed, 7 Jan 2009 11:51:45 +0100
Patrick Mast, xHarbour. patrick.m...@xharbour.com wrote:
Very stable! :-)
Than I think the moment arrived to start preparing for a new release, right?
This has been on the table for long now.
Yes, IMO.
--
Andi
As Enrico told him, recompiling the PRGs will do it. So, in other words,
a PCode version increment is a MUST ;-)
--
Andi
On Wed, 7 Jan 2009 11:52:14 +0100
Patrick Mast, xHarbour. patrick.m...@xharbour.com wrote:
That is, once we fixed brian's GPF off course! ;-)
On Wed, Jan 7, 2009 at 11:51
On Wed, 7 Jan 2009 01:21:30 -0800
bhays bh...@abacuslaw.com wrote:
Wouldn't incrementing the PCode version accomplish this, even if it was an
item structure change instead of pcode change that causes the crash?
I fully agree with PCode version. The structure change is quite dangerous
if we do
Very stable! :-)
Yes, I confirm. FWH works perfectly with latest cvs.
Regards,
Toninho.
--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open
Patrick:
That GPF was caused by a FWH .prg file that wasn't in our
own modified collection of FWH code (listbox.prg). When
a true RTE happen, the listbox object created by the FWH
error dialog bombed when an AEval occured inside
TListbox():Default().
As soon as I pulled this prg from FWH into
-Messaggio Originale-
Da: Patrick Mast, xHarbour. patrick.m...@xharbour.com
A: Luis Krause Mantilla lkrau...@shaw.ca
Cc: xHarbour-Developers xharbour-developers@lists.sourceforge.net
Data invio: mercoledì 7 gennaio 2009 18.20
Oggetto: Re: [xHarbour-developers] Current CVS stable?
Hey
5:08 PM
Subject: Re: [xHarbour-developers] Current CVS stable?
-Messaggio Originale-
Da: Patrick Mast, xHarbour. patrick.m...@xharbour.com
A: Luis Krause Mantilla lkrau...@shaw.ca
Cc: xHarbour-Developers xharbour-developers@lists.sourceforge.net
Data invio: mercoledì 7 gennaio 2009 18.20
-Original Message-
From: Patrick Mast, xHarbour. [mailto:patrick.m...@xharbour.com]
Sent: Wednesday, January 07, 2009 9:21 AM
To: Luis Krause Mantilla
Cc: xHarbour-Developers
Subject: Re: [xHarbour-developers] Current CVS stable?
Hey Luis,
Thanks for the info.
Ok, so than I think
Hello,
For all of use, Happy New Year! ;-)
I was wondering.. Since I did not see any bugreports anymore for
current CVS, is current CVS stable?
Does anyone have any pending bugreports?
Thanks!
Patrick
--
Hey Enrico,
It's perfectly stable for me.
Thank you for the fast reply ;-)
Can you tell us how you experience the new Speed? Do you feel the difference?
Patrick
--
___
-Messaggio Originale-
Da: Patrick Mast, xHarbour. patrick.m...@xharbour.com
A: Enrico Maria Giordano e.m.giord...@emagsoftware.it
Cc: xHarbour-Developers xharbour-developers@lists.sourceforge.net
Data invio: martedì 6 gennaio 2009 15.40
Oggetto: Re: [xHarbour-developers] Current CVS
...@xharbour.com]
Sent: Tuesday, January 06, 2009 6:35 AM
To: xHarbour-Developers
Subject: [xHarbour-developers] Current CVS stable?
Hello,
For all of use, Happy New Year! ;-)
I was wondering.. Since I did not see any bugreports anymore for
current CVS, is current CVS stable?
Does anyone
-Messaggio Originale-
Da: bhays bh...@abacuslaw.com
A: 'xHarbour-Developers' xharbour-developers@lists.sourceforge.net
Data invio: martedì 6 gennaio 2009 21.22
Oggetto: Re: [xHarbour-developers] Current CVS stable?
With the current cvs, our ErrorSys in Fivewin apps is throwing a gpf
: Tuesday, January 06, 2009 2:07 PM
To: bhays; 'xHarbour-Developers'
Subject: Re: [xHarbour-developers] Current CVS stable?
-Messaggio Originale-
Da: bhays bh...@abacuslaw.com
A: 'xHarbour-Developers' xharbour-developers@lists.sourceforge.net
Data invio: martedì 6 gennaio 2009 21.22
Hey Brian,
Thanks. Is it possible for us to catch this at link time
instead of waiting for untraceable gpfs? Was there a pcode version
change, and if not shouldn't there be?
I use this XBP file to rebuild Fivehmx.lib
http://www.xHarbour.net/Downloads/Fivehmx_xHB.lib.zip
In my tests, FWH
22 matches
Mail list logo
