diff options
| author | tb <> | 2023-05-14 16:36:25 +0000 | 
|---|---|---|
| committer | tb <> | 2023-05-14 16:36:25 +0000 | 
| commit | 816eddcf8128dfb5e2e9a4c68c07f2ca97df1275 (patch) | |
| tree | a797686d0bca2b1add947591c1d23014555744cd /src/lib/libcrypto/dsa/dsa_err.c | |
| parent | cb53eb80a3be6281f322df6ba16c89ac7f7b2109 (diff) | |
| download | openbsd-816eddcf8128dfb5e2e9a4c68c07f2ca97df1275.tar.gz openbsd-816eddcf8128dfb5e2e9a4c68c07f2ca97df1275.tar.bz2 openbsd-816eddcf8128dfb5e2e9a4c68c07f2ca97df1275.zip | |
Send the linebuffer BIO to the attic
  *) On VMS, stdout may very well lead to a file that is written to
     in a record-oriented fashion.  That means that every write() will
     write a separate record, which will be read separately by the
     programs trying to read from it.  This can be very confusing.
     The solution is to put a BIO filter in the way that will buffer
     text until a linefeed is reached, and then write everything a
     line at a time, so every record written will be an actual line,
     not chunks of lines and not (usually doesn't happen, but I've
     seen it once) several lines in one record.  BIO_f_linebuffer() is
     the answer.
     Currently, it's a VMS-only method, because that's where it has
     been tested well enough.
     [Richard Levitte]
Yeah, no, we don't care about any of this and haven't compiled this file
since forever. Looks like tedu's chainsaw got blunt at some point...
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions
