messagedef.mes 3.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182
  1. # Copyright (C) 2011 Internet Systems Consortium, Inc. ("ISC")
  2. #
  3. # Permission to use, copy, modify, and/or distribute this software for any
  4. # purpose with or without fee is hereby granted, provided that the above
  5. # copyright notice and this permission notice appear in all copies.
  6. #
  7. # THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
  8. # REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
  9. # AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
  10. # INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
  11. # LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
  12. # OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  13. # PERFORMANCE OF THIS SOFTWARE.
  14. # $Id$
  15. $PREFIX MSG_
  16. # \brief Message Utility Message File
  17. #
  18. # This is the source of the set of messages generated by the message and logging
  19. # components. The associated .h and .cc files are created by hand from this
  20. # file though and are not built during the build process; this is to avoid the
  21. # chicken-and-egg situation where we need the files to build the message
  22. # compiler, yet we need the compiler to build the files.
  23. DUPLPRFX duplicate $PREFIX directive found
  24. + When reading a message file, more than one $PREFIX directive was found. In
  25. + this version of the code, such a condition is regarded as an error and the
  26. + read will be abandonded.
  27. IDNOTFND could not replace message for '%s': no such message identification
  28. + During start-up a local message file was read. A line with the listed
  29. + message identification was found in the file, but the identification is not
  30. + one contained in the compiled-in message dictionary. Either the message
  31. + identification has been mis-spelled in the file, or the local file was used
  32. + for an earlier version of the software and the message with that
  33. + identification has been removed.
  34. +
  35. + This message may appear a number of times in the file, once for every such
  36. + unknown mnessage identification.
  37. ONETOKEN a line containing a message ID ('%s') and nothing else was found
  38. + Message definitions comprise lines starting with a message identification (a
  39. + symbolic name for the message) and followed by the text of the message. This
  40. + error is generated when a line is found in the message file that contains just
  41. + the message identification.
  42. OPENIN unable to open message file %s for input: %s
  43. + The program was not able to open the specified input message file for the
  44. + reason given.
  45. OPENOUT unable to open %s for output: %s
  46. + The program was not able to open the specified output file for the reason
  47. + given.
  48. PRFEXTRARG $PREFIX directive has too many arguments
  49. + The $PREFIX directive takes a single argument, a prefix to be added to the
  50. + symbol names when a C++ .h file is created. This error is generated when the
  51. + compiler finds a $PREFIX directive with more than one argument.
  52. PRFINVARG $PREFIX directive has an invalid argument ('%s')
  53. + The $PREFIX argument is used in a symbol name in a C++ header file. As such,
  54. + it must adhere to restrictions on C++ symbol names (e.g. may only contain
  55. + alphanumeric characters or underscores, and may nor start with a digit). A
  56. + $PREFIX directive was found with an argument (given in the message) that
  57. + violates those restictions.
  58. PRFNOARG no arguments were given to the $PREFIX directive
  59. + The $PREFIX directive takes a single argument, a prefix to be added to the
  60. + symbol names when a C++ .h file is created. This error is generated when the
  61. + compiler finds a $PREFIX directive with noa rguments.
  62. READERR error reading from %s: %s
  63. + The specified error was encountered reading from the named input file.
  64. UNRECDIR unrecognised directive '%s'
  65. + A line starting with a dollar symbol was found, but the first word on the line
  66. + (shown in the message) was not a recognised message compiler directive.
  67. WRITERR error writing to %s: %s
  68. + The specified error was encountered writing to the named output file.