>> Moreover, if someone wants to do this (per source >> options), there are other, already working ways to >> solve it. (f.e. defines, and pragmas). This are >> make-system agnostic, part of the source code, thus >> much better. >> > > #pragma could be a solution and have tested and works ok. > So this part is now fine with me. > > One test point to other anomaly when including #pragma > directive in the source is that its value is retained for rest of the > files too. For example, #prgma /N- is first source is effective for > the next sources too.
I can confirm this, and it looks like a bug to me. >> Pls provide a reduced example. >> > > It cannot be reduced as a self-reduced as the warnings > are issued with really large sources written in sephgetti styles. All we know is you sometimes get this, despite you set -w0 on the command line: C:\Dev\C5\cn.prg(50) Warning W0001 Ambiguous reference 'MESSAGE' C:\Dev\C5\cn.prg(67) Warning W0001 Ambiguous reference 'E_VAR' Is it possible that you have any of these somewhere in your source: #pragma WARNINGLEVEL=1 #pragma -w1 (where 1 could be any valid warning level) Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
