On 27 Apr 2000, Oleg Goldshmidt wrote:
If you must code in C, at least use the safe routines in glib (for
example g_strdup_sprintf) rather then using unsafe functions such as
sprintf.
This might be not feasible if you need to write portable code
(nor will be snprintf(), which is
On 27 Apr 2000, Oleg Goldshmidt wrote:
To reiterate my point: use glib instead of libc. Glib is *very* portable.
What do you mean? What if your target platform does not have glibc?
This might be outside of your control... Come to think of it, it
usually *is* outside of your control.
Moshe Zadka [EMAIL PROTECTED] writes:
On 27 Apr 2000, Oleg Goldshmidt wrote:
To reiterate my point: use glib instead of libc. Glib is *very* portable.
What do you mean? What if your target platform does not have glibc?
This might be outside of your control... Come to think of it, it
On 27 Apr 2000, Oleg Goldshmidt wrote:
Moshe Zadka [EMAIL PROTECTED] writes:
On 27 Apr 2000, Oleg Goldshmidt wrote:
To reiterate my point: use glib instead of libc. Glib is *very* portable.
What do you mean? What if your target platform does not have glibc?
This might be
"David Tabachnikov (NetHunter)" wrote:
Nobody was talking about GLIBC, Moshe was talking about GLIB, the
library that is under GTK+, which provides safe and portable
alternatives to the libc5/6(aka glibc) and everything else.
GLib (iirc) runs on IRIX, AIX, Windows, Linux, *BSD, DOS, BeOS,
Omer Mussaev [EMAIL PROTECTED] writes:
Sorry, ppl , but IMHO Oleg had pointed out a very strong point. Imagine
you are to distribute small utility, which takes, say, 300 kb. But, instead
of using libc and debugging your code to death, you decided to rely on glib
to provide it to you. As a
If you must code in C, at least use the safe routines in glib
(for example g_strdup_sprintf) rather then using unsafe
functions such as sprintf.
This might be not feasible if you need to write portable code
(nor will be snprintf(), which is non-standard, IIRC). You need
to get
On Thu, 27 Apr 2000, David Tabachnikov (NetHunter) wrote:
Nobody was talking about GLIBC, Moshe was talking about GLIB, the
library that is under GTK+, which provides safe and portable
alternatives to the libc5/6(aka glibc) and everything else.
it looks like there is a quarel here between
Of course, the best way to avoid buffer overflows is to use good
libraries, or even better a good language. Neither Python nor Perl nor
Guile nor Tcl will *let* you have a buffer overflow as long as the
implementation is bug free. Since you are relying anyway on external
code (e.g., libc), might
