Age | Commit message (Collapse) | Author |
|
|
|
could very well cause a negate number get passed in and thus cause reading
outside of the array usually used for this purpose.
We avoid this by using the uppercase macro versions introduced just now that
does some extra crazy typecasts to avoid byte codes > 127 to cause negative
int values.
|
|
|
|
So avoid using x_was_used().
|
|
|
|
VS2005.
|
|
|
|
|
|
Confirmed by Paul Nolan.
|
|
|
|
|
|
precaution to prevent mistakes to lead to buffer overflows.
|
|
linked list for name resolved data, even on hosts/systems with only IPv4
stacks as this simplifies a lot of code.
|
|
|
|
memory.h is included everywhere for this.
|
|
previously they could return a piece of the string, making it impossible
for the caller to detect errors.
|
|
|
|
|
|
make strtol() returns get stored in long variables
don't mix size_t with int
|
|
|
|
|
|
|
|
|
|
can use a 64bit type with MSVC that is a long long equivalent.
|
|
int to various types
|
|
and I doubt anyone else uses it.
Better preprocessor magic for the O flag (for curl_off_t printing) to prevent
compiler warnings.
|
|
warnings. Minor edits by me.
|
|
|
|
|
|
outside its given buffer. Discovered and reported by James Bursa.
|
|
|
|
in the urlglobbing just now, fixed in the debian bug tracker as Bug#203827
|
|
|
|
way for emacs, and vim users should provide a similar non-polluting style
|
|
|
|
|
|
empty string
|
|
|
|
where BLA is undefined
|
|
should anyone ever want a good printf() clone
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
gcc 3.0 warned about it
|
|
|
|
|