> On Jul 4, 2016, at 15:53, Dmitry Markman <dmark...@mac.com> wrote: > > Hmm > > behavior you described is good receipt to un-robust software > > IMHO, all talks about “effective", “typically" and so on and on is matter of > interpretation > > and are much less important than standard
An implementation of malloc that never returns NULL is still compliant to the standard. > first of all there is a standard and nothing more. In some cases standard > says that behavior is undefined > > but in case of “malloc" and "operator new” everything is well defined The standard says that malloc returns NULL in case of failure. It however, says nothing about what constitutes a failure, or *any* situations in which NULL must be returned.. -- Clark Smith Cox III clarkc...@gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
