Page MenuHomeFreeBSD

Add warnings when _ON is defined and _OFF is not (and vice versa)
Needs ReviewPublic

Authored by mat on Sep 17 2018, 8:34 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mar 21 2024, 6:33 PM
Unknown Object (File)
Jan 5 2024, 5:40 PM
Unknown Object (File)
Dec 25 2023, 9:42 AM
Unknown Object (File)
Dec 24 2023, 4:44 AM
Unknown Object (File)
Nov 8 2023, 12:43 PM
Unknown Object (File)
Nov 6 2023, 6:55 PM
Unknown Object (File)
Oct 30 2023, 11:55 PM
Unknown Object (File)
Oct 18 2023, 6:51 AM
Subscribers

Details

Reviewers
None
Group Reviewers
portmgr

Diff Detail

Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 19618
Build 19193: arc lint + arc unit

Event Timeline

I don't think it's right, there are legitimate use of _ON without _OFF.

There are, yes, I agree, this is why it is a warning, not an error, something saying "hey, make sure you did not mess it up".

Or do we need to have a third level like, DEV_NOTICE, because people treat warnings as errors ?

  • Add warnings about OPTIONS_SLAVE and OPTIONS_EXCLUDE.
  • Add warnings about non existent options for specific variables.