|View Issue Details [ Jump to Notes ]||[ Issue History ] [ Print ]|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000497||mercury||Feature Request||public||2020-04-03 15:13||2020-04-20 15:09|
|Target Version||Fixed in Version|
|Summary||0000497: make disable_warning forwards compatible|
|Description||Currently if the compiler does not recognise a warning name in a disable_warning(s) goal, it will report an error. I think we can reduce the severity of an unknown warning name from an error to a warning. This will provide a transition period in which a source file that has been updated to suppress warnings when using a newer compiler version, will still compile (with warnings) when using an older compiler.|
|Tags||No tags attached.|
|Feature implemented 2020 april 4.|
Thanks for taking a look.
However, the change is incomplete. When the clause is to be added in module_add_clause_2, MaybeBodyGoal is error1(...), the clause is not added, and compilation stops soon after.
BTW, this also affects duplicated names in disable_warnings scopes. The error message says "Error:" but the error spec has severity_warning.
|Fixed in commit 4f32c5082|
|2020-04-03 15:13||wangp||New Issue|
|2020-04-04 02:43||zs||Assigned To||=> zs|
|2020-04-04 02:43||zs||Status||new => resolved|
|2020-04-04 02:43||zs||Resolution||open => fixed|
|2020-04-04 02:43||zs||Note Added: 0001077|
|2020-04-04 13:07||wangp||Status||resolved => feedback|
|2020-04-04 13:07||wangp||Resolution||fixed => reopened|
|2020-04-04 13:07||wangp||Note Added: 0001078|
|2020-04-20 15:08||wangp||Status||feedback => assigned|
|2020-04-20 15:08||wangp||Resolution||reopened => fixed|
|2020-04-20 15:08||wangp||Note Added: 0001084|
|2020-04-20 15:09||wangp||Status||assigned => resolved|