Viktor Szakáts wrote:
>
> -w0 only changes Harbour warning level. To turn off
> C compiler warnings, you can use -warn=no option, by
> default hbmk2 uses the same warning level as Harbour
> build and bcc is known to exit with fatal error if
> number of warnings is high. I'd suggest to experiment
> with -warn=low first.
>
> Anyhow it's strange you have any C warnings in
> generated .c code, but it's possible that xhb's
> lower standard on warnings is kicking in here.
>
At this point I feel C compiler is not in picture.
Harbour.exe is to process all .prgs and then C compiler is called.
My strong feeling is if Harbour.exe is designed to be invoked for
single source at a time. I could compile other applications
with much more sources but almost negligible warnings.
To me it appears harbour.exe does not clear the stack(s) before
processing next source. But I can be totally wrong.
-----
enjoy hbIDEing...
Pritpal Bedi
http://hbide.vouch.info/
--
View this message in context:
http://harbour-devel.1590103.n2.nabble.com/hbMK2-xhb-issues-switch-n-by-default-which-breaks-process-tp5005754p5011187.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
