[openbeos] Re: Busticated posix/string.h?
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Thu, 31 Oct 2002 15:09:59 +0100 CET
Scott Mansfield <thephantom@xxxxxxx> wrote:
> As I put the finishing touches on the BNetEndpoint class I noticed
> that
> in our version of posix/string.h the strerror() function returns a
> const char*, as opposed to the POSIX return type of char*.
>
> While I think returning a const pointer in this case is a good thing
> (can't tell you how many times I've crashed a system freeing memory I
> don't own ... muahahahahahahaha) this just doesn't seem right.
>
> So is this truly busticated; or were my Cheerios spiked with illicit
> mind-altering substances?
Well, I have changed it to const (because it just feel better) - but I
am aware that POSIX dictates a char * (it would be binary compatible,
though).
We probably should stick to the POSIX standard, though, even if it
doesn't make much sense...
Adios...
Axel.
- Follow-Ups:
- [openbeos] Re: Busticated posix/string.h?
- From: Scott Mansfield
- References:
- [openbeos] Busticated posix/string.h?
- From: Scott Mansfield
Other related posts:
- » [openbeos] Busticated posix/string.h?
- » [openbeos] Re: Busticated posix/string.h?
- » [openbeos] Re: Busticated posix/string.h?
- [openbeos] Re: Busticated posix/string.h?
- From: Scott Mansfield
- [openbeos] Busticated posix/string.h?
- From: Scott Mansfield