[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Chris wrote:
As I understand it, only Microsoft's implementation of libc is unsafe. From
what I've heard, other systems do not have this problem.
How can be gets() implemented safely?
As well, the "old"
functions and the new ones that replace them have the same prototype, just
with a different name
Often they have different prototype.
(so they could've just easilly fixed the problems in
the "unsafe" functions, and not have to make new functions for it).
As their behaviour is different from standard's one its much better to
change their name, isn't it?
I haven't
been able to find any info on what the problem is, other than MSDN claiming
they're "unsafe" and should use other functions isntead.
http://msdn2.microsoft.com/library/8ef0s5kh(en-us,vs.80).asp
To be clear, it's not functions like sprintf that they're marking unsafe
(though I'm sure that's included). But things like fopen, printf, memcpy, and
other, as well.
sprintf is marked unsafe
--
Regards,
Michal
ICQ# 175762750