| |||||||||||||
|
| |||||||||||||
Getting the message from the kernelGetting the message from the kernelPosted Jun 21, 2007 6:44 UTC (Thu) by pfavr (subscriber, #38205)In reply to: Getting the message from the kernel by pj Parent article: Getting the message from the kernel
Yes! This is the way to go.
If you get messages from the kernel - then __FILE__ and __LINE__ is the easiest way to get people grok the source.
People interested in looking up numbers on a list are probably building their own kernel anyway.
Using __FILE__ and __LINE__ will make sure the references are updated with changes to the kernel.
(and the source is the real documentation anyway :-)
Best regards,
Peter
(Log in to post comments)
Getting the message from the kernel Posted Jun 21, 2007 20:57 UTC (Thu) by jordanb (subscriber, #45668) [Link] The problem is that line numbers are volatile so it'd be difficult to keep a manual or (more likely) a translation table attached to the proper message.
Getting the message from the kernel Posted Jul 2, 2007 9:19 UTC (Mon) by alext (guest, #7589) [Link]
Besides the error message is already going to have to be unique and therefore
The big use must be to allow external full explanations to exist that allow admin's etc to apply any known changes to config that get around the problem.
And as the start of the thread suggested, why is there so much resistance to potentially having something as simple as a call with a string and that string having a unique ID attached? It sounds like Linus being a bit precious rather than treating it like just adding a new hook to the code base for others to use in documenting behavior.
|
|
||||||||||||