Roy Stogner wrote:
> On Tue, 29 Sep 2009, John Peterson wrote:
> 
>> I don't think this is PETSc's bug, they are just calling getpwuid()...
> 
> Do they call endpwent() when they're done with it?

I'm not sure PETSc can call this, the user may expect it to be open.
Consider

  pw = getpwent();
  PetscInitialize();
  /* pw should be valid */
  PetscFinalize();
  /* pw should still be valid */
  endpwent();


I can't think of a reason why a user would *need* the semantics above,
but it's certainly what one would expect.  In the current
implementation, even though pw will still be valid, its value may have
changed (implementation dependent, and likely surprising).  If you think
PETSc should call endpwent(), feel free to raise the issue on the
mailing list.

Whoever wrote the pwd.h API should be tarred and feathered.


Jed

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to