Cynerd commented on PR #16280: URL: https://github.com/apache/nuttx/pull/16280#issuecomment-2837627688
> it seems LOG_EMERG will always have to be active. Just to clarify. At least one level will always have to be enabled. It doesn't have to be `LOG_EMERG`, but it is the most reasonable choice. I think it is more important to be POSIX compliant than to allow all logs to be disabled, when emergency logs are pretty much nowhere to be found. At least, applications expecting defined behavior would inevitably disable all logs because users of `setlogmask` should not expect that `0` clears all bits, as it goes against POSIX. Thus, the current behavior is malicious, in my opinion. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
