We do not need ARGV, Argc and Argv - just use argc and argv like normal
people do.

ok beck@ (although he wanted #Arrrrrrrgv instead).
Casting from a const unsigned char ** to a const unsigned char ** seems...
unnecessary. Remove the temporary ugly casts - the comments even call them
that!

ok guenther@
Figure out endianness at compile-time, using _BYTE_ORDER from
<machine/endian.h>, rather than writing 1 to a 32-bit variable and checking
whether the first byte is nonzero.

tweaks and ok matthew@; ok beck@ tedu@
Remove duplicate pointer assignment in ASN1_primitive_free(); Dirk Engling
Unifdef -UPEDANTIC. ok beck@ tedu@
Forgotten during latest spring cleaning of unreferenced bits.
Grr, the more you remove, the more there remain.
I'm glad to know that Ultrix CC has a bug optimizing switch() statements
lacking an explicit `case 0:' construct. But Ultrix has been dead for more than
15 years, really. Don't give it any reason to move out of its coffin.
Remove IRIX_CC_BUG workaround.
When I grow up, I want to write workaround for long long multiplications
under __TANDEM systems and compilers, using hardcoded octal numbers. NOT.
One last Dec C tentacle on alpha.
if realloc failed, BIO_accept would leak memory and return NULL, causing
caller to crash. Fix leak and return an error instead. from Chad Loder
close socket in failure cases too
whitespace
The usual idiom to cope with systems not defining socklen_t is to add a
#define socklen_t int
somewhere (or a typedef, whatever gives you an integer type of the size
your system expects as the 3rd argument of accept(2), really).

OpenSSL here is a bit more creative by using an union of an int and a size_t,
and extra code if sizeof(int) != sizeof(size_t) in order to recover the
proper size. With a comment mentioning that this has no chance to work on
a platform with a stack growing up and accept() returning an int, fortunately
this seems to work on HP-UX.

Switch to the light side of the force and declare and use socklen_t variables,
period. If your system does not define socklen_t, consider bringing it back
to your vendor for a refund.

ok matthew@ tedu@
null pointers after free to prevent double frees and worse. also fix a
very obvious use after free. this file may still be a total loss.
No longer needed during build. Brings a smile on beck@'s face.
malloc/memset -> calloc. from peter malone
Don't bother generating win64 assembly prologue.
replace a bunch of hand duped strings with strdup