Enrico:
I'd prefer to have those warnings as a note that one time we should
modify the PRG file.
--
Andi
On Sat, 24 May 2008 22:27:51 +0200
Enrico Maria Giordano [EMAIL PROTECTED] wrote:
As subject. Currently there are tons of unuseful warnings related to unused
function parameters.
If
Or, if we'd preferred to please our eyes :-), we can create a macro for
that, ie:
rem -w2 is default
SET WARNINGLEVEL=2
Then: HARBOUR -n1 -w$(WARNINGLEVEL) ..
--
Andi
Enrico:
I'd prefer to have those warnings as a note that one time we should
modify the PRG file.
--
Andi
-Messaggio Originale-
Da: Andi Jahja [EMAIL PROTECTED]
A: Xharbour-Developers xharbour-developers@lists.sourceforge.net
Data invio: domenica 25 maggio 2008 12.25
Oggetto: Re: [xHarbour-developers] Proposal for replacing -w2 with -w
inmakefile
Enrico:
I'd prefer to have those
-Messaggio Originale-
Da: Andi Jahja [EMAIL PROTECTED]
A: Xharbour-Developers xharbour-developers@lists.sourceforge.net
Data invio: domenica 25 maggio 2008 12.53
Oggetto: Re: [xHarbour-developers] Proposal for replacing -w2 with -w
inmakefile
Or, if we'd preferred to please our eyes
Hi,
2008/5/25 Enrico Maria Giordano [EMAIL PROTECTED]:
Ok, I agree. But I hope the authors will fix all those warnings.
To achieve it faster, we can fix -es2 so that compilation fails on -w2
warnings too.
-- Ph.
-
This
-Messaggio Originale-
Da: Phil Krylov [EMAIL PROTECTED]
A: Enrico Maria Giordano [EMAIL PROTECTED]
Cc: Andi Jahja [EMAIL PROTECTED]; Xharbour-Developers
xharbour-developers@lists.sourceforge.net
Data invio: domenica 25 maggio 2008 16.38
Oggetto: Re: [xHarbour-developers] Proposal for
Hi,
I think we should FIX -W2 warnings instead of trying to hide them.
Ron? Did you not plan to take a closer look at the -Wx engine in xHarbour?
Patrick
-
This SF.net email is sponsored by: Microsoft
Defy all challenges.
Dear Friends
This small program bellow, when compiled with multithread support GPF
func main
? Stating thread
startthread(test,1,2) // GPF on thread.c 1667
startthread(@test(),1,2) // GPF on thread.c 1616
waitforthreads()
return nil
function test(a,b)
? a,b
return nil
Regards
Luiz
Luiz,
It works fine here.
What is your compile/link switch ?
--
Andi
On Sun, 25 May 2008 18:34:24 -0300
Luiz Rafael Culik Guimaraes [EMAIL PROTECTED] wrote:
Dear Friends
This small program bellow, when compiled with multithread support GPF
func main
? Stating thread
startthread(test,1,2)
2008/5/26 Luiz Rafael Culik Guimaraes [EMAIL PROTECTED]:
Dear Friends
This small program bellow, when compiled with multithread support GPF
func main
? Stating thread
startthread(test,1,2) // GPF on thread.c 1667
startthread(@test(),1,2) // GPF on thread.c 1616
waitforthreads()
return
2008/5/26 Phil Krylov [EMAIL PROTECTED]:
2008/5/26 Luiz Rafael Culik Guimaraes [EMAIL PROTECTED]:
Dear Friends
This small program bellow, when compiled with multithread support GPF
func main
? Stating thread
startthread(test,1,2) // GPF on thread.c 1667
startthread(@test(),1,2) // GPF on
Brian:
Sorry, but I'm not a Linux user.
It's there for Windows and of course we hope that Linux user will insert
a corresponding compatible error handling.
--
Andi
On Sun, 25 May 2008 15:19:51 -0700
bhays [EMAIL PROTECTED] wrote:
Andi (And ADS Linux users):
In your new ace32.c
On Mon, 26 May 2008 05:29:20 +0700
Andi Jahja [EMAIL PROTECTED] wrote:
Sorry, but I'm not a Linux user.
It's there for Windows and of course we hope that Linux user will insert
a corresponding compatible error handling.
Or we can easily replace it with a common ALERT()...
--
Andi
I think they should just throw/set an error code. Nothing visual (including
xharbour alert messages). Let the user do as he will with the error code.
In Linux the counterpart of ace32.dll is a shared library *.so. They work
in the very same manner. Although I don't think there is many people
14 matches
Mail list logo
