ERRHDR(1)

πŸ’– ERRHDR πŸ’–

okay bestie, so errhdr is a lil NCBI Tools User's Manual girly and her whole thing is turning a file of messages into a C header file. that's it, that's the job. she's a compiler-adjacent baddie and she ate. ✨


🌸 SYNOPSIS 🌸

errhdr [-2] [-s] msgfile [hdrfile]

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea πŸ“ β€” errhdr reads a file that describes error codes and the messages that go with them, and then it produces a C header file. and where does that header go? either straight to standard output, or into hdrfile if you gave it one. main character energy, honestly.

the input file has a simple text-based format. no cap, it's giving very readable. one file β€” errmsg/valid.msg in the source tree β€” starts like this:

MODULE valid
$$ SEQ_INST, 1
$^   ExtNotAllowed, 1
# This is a comment
A Bioseq "extension" is used for special classes of Bioseq. This class of
Bioseq should not have one but it does. This is probably a software error.

$^   ExtBadOrMissing, 2
This class of Bioseq requires an "extension" but it is missing or of the
wrong type. This is probably a software error.

and lowkey the best part: detailed descriptions are optional, and you don't need any "end" lines of any sort. not one. not ever. iconic behavior fr fr πŸ’…


✨ OPTIONS ✨

a summary of options is included below, bestie, as a lil treat πŸŽ€

  • -2 β€” Code, subcode tuples
  • -s β€” Short subcode defines

πŸ‘‘ AUTHOR πŸ‘‘

The National Center for Biotechnology Information. πŸ’œ


okay that's the whole page, bestie!! this one came from NCBI, dated 2001-10-05, and it's page ERRHDR(1) of the NCBI Tools User's Manual. go make some headers, you absolute legend πŸ«ΆπŸŽ€πŸŒŸ

πŸ“¦ where this page comes from