In message <9402.983047348@critter>, Poul-Henning Kamp writes: >>Well, no, but the sole available definition of "portable" says that it is >>"portable" to assume that all the memory malloc can return is really >>available. >No, this is not a guarantee. Yes, it is. If the memory isn't available, malloc returns NULL. >We also don't guarantee that you can read a file just because you >managed to open it (disk errors, nfs servers going away, forced >unmounts). Sure. And all the IO functions have return codes. -s To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: Setting memory allocators for library... Alfred Perlstein
- Re: Setting memory allocators for lib... Farooq Mela
- Re: Setting memory allocators fo... Alfred Perlstein
- Re: Setting memory allocators for library fun... Jonas Bulow
- Re: Setting memory allocators for library functions. Dag-Erling Smorgrav
- Re: Setting memory allocators for library functio... Peter Seebach
- Re: Setting memory allocators for library fun... Dag-Erling Smorgrav
- Re: Setting memory allocators for library... Dag-Erling Smorgrav
- Re: Setting memory allocators for library... Peter Seebach
- Re: Setting memory allocators for lib... Poul-Henning Kamp
- Re: Setting memory allocators fo... Peter Seebach
- Re: Setting memory allocators fo... Poul-Henning Kamp
- Re: Setting memory allocators fo... Peter Seebach
- Re: Setting memory allocators fo... Poul-Henning Kamp
- Re: Setting memory allocators fo... Peter Seebach
- Re: Setting memory allocators fo... Poul-Henning Kamp
- Re: Setting memory allocators fo... Peter Seebach
- Re: Setting memory allocators fo... Poul-Henning Kamp
- Re: Setting memory allocators fo... Peter Seebach
- Re: Setting memory allocators fo... Dag-Erling Smorgrav
- Re: Setting memory allocators fo... Peter Seebach

