[M3devel] order of warnings, or even to have any?

Tony Hosking hosking at cs.purdue.edu
Sun May 4 15:19:48 CEST 2008


Why the difference on different targets?

Antony Hosking | Associate Professor | Computer Science | Purdue  
University
305 N. University Street | West Lafayette | IN 47907 | USA
Office +1 765 494 6001 | Mobile +1 765 427 5484



On May 4, 2008, at 7:17 AM, Jay wrote:

> C:\dev2\cm3\m3-sys\m3tests\src\p0\p004>cm3
> --- building in NT386 ---
> new source -> compiling Main.m3
> "..\Main.m3", line 35: warning: exception is never raised: Main.e
> "..\Main.m3", line 9: warning: exception is never raised: <ANY>
> "..\Main.m3", line 59: warning: unreachable statement
> "..\Main.m3", line 68: warning: unreachable statement
> "..\Main.m3", line 71: warning: unreachable statement
> "..\Main.m3", line 82: warning: unreachable statement
> "..\Main.m3", line 86: warning: unreachable statement
> "..\Main.m3", line 64: warning: unreachable statement
> 8 warnings encountered
>  -> linking pgm.exe
> link @_m3responsefile0.txt 2>&1 > pgm.lst
> mt /nologo /manifest pgm.exe.manifest /outputresource:pgm.exe;1
> .\pgm.exe >stdout.pgm.raw 2>stderr.pgm.raw
>
>
> Does the order of the warnings matter?
> Does the test even care if they are printed?
> The expected output and the actual output are in a different order.
> Neither are in order by line number, though the expected output is  
> closer.
> The order is consistent on all platforms?
> No. LINUXLIBC6 and NT386 output in a different order.
> This doesn't seem all that important..
>
>   - Jay
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080504/17655bba/attachment-0002.html>


More information about the M3devel mailing list