Re: is there a standard for specifying assertions?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/26/07, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote:
  is there (or can there be) a prescribed standard for assertions in
kernel code?  as it stands, include/asm-generic/bug.h defines the
following debugging directives:

  BUG()
  BUG_ON(condition)
  WARN_ON(condition)
  WARN_ON_ONCE(condition)

these are really the only things people should be using

which, you would think, would be sufficient to cover the majority of
needs.  and yet, loads of people insist on defining some variation of
an assertion for their code:

usually fall out from people who had custom assert/debug code and
didnt know about the BUG/WARN macros
-mike

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux