>> > return=NULL; output=junk => out of memory >> > return=junk; output=-1 => cannot do this >> > return=pointer; output=value => did this, returned value bytes >> >> > I agree that the design is a bit questionable; >> >> It sure is. If you get both NULL and -1 returned, how are >> you supposed to know which one is the junk? > > I was about to say "by doing the tests in the prescribed order", > but you're right that it's not obvious that the function checks > that it returns the right kind of junk... (it's possible that the > junk in the second line is actually "pointer to some other ob- > ject").
footnote: it is; the table should read return=NULL; output=junk => out of memory return=old pointer; output=-1 => no need do this; returning old pointer return=new pointer; output=value => did this, returned pointer to newly allocated area containing 'value' bytes </F> _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com