diff options
author | Niels Provos <provos@cvs.openbsd.org> | 2000-11-10 15:33:16 +0000 |
---|---|---|
committer | Niels Provos <provos@cvs.openbsd.org> | 2000-11-10 15:33:16 +0000 |
commit | 5e5c20b4986d64cf4b989750655ce99a581ee745 (patch) | |
tree | 454d7edecf7d8c42395d523edcb4da46a285da42 /usr.sbin/dhcp/includes/cf/sample.h | |
parent | fa37968b43055a44587325acd7d958a96fc4e5a7 (diff) |
seperate -> separate, okay aaron@
Diffstat (limited to 'usr.sbin/dhcp/includes/cf/sample.h')
-rw-r--r-- | usr.sbin/dhcp/includes/cf/sample.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/usr.sbin/dhcp/includes/cf/sample.h b/usr.sbin/dhcp/includes/cf/sample.h index 892303b977e..e50d8b17b0e 100644 --- a/usr.sbin/dhcp/includes/cf/sample.h +++ b/usr.sbin/dhcp/includes/cf/sample.h @@ -255,13 +255,13 @@ char *strerror PROTO ((int)); /* #define HAVE_SA_LEN */ -/* Every operating system has its own way of seperating lines in a +/* Every operating system has its own way of separating lines in a sequential text file. Most modern systems use a single character, either an ASCII Newline (10) or an ASCII Carriage Return (13). The most notable exception is MS-DOS (and consequently, Windows), which uses an ASCII Carriage Return followed by a Newline to - seperate each line. Fortunately, MS-DOS C compiler libraries + separate each line. Fortunately, MS-DOS C compiler libraries typically hide this from the programmer, returning just a Newline. Define EOL to be whatever getc() returns for a newline. */ |