[Developers] should we document that CCTK_MyProc(NULL) works?

[Erik Schnetter]

On Jan 12, 2007, at 11:08:16, Jonathan Thornburg wrote:

> On Fri, 12 Jan 2007, Tom Goodale wrote:
>> The only problem is that in principle drivers could be using a  
>> different
>> processor mapping - e.g. when using MPI the driver could use a  
>> different
>> communicator - which would give a different result with NULL than  
>> with a
>> cGH, so I would prefer to not document that NULL is acceptable.   
>> It is
>> only used in the flesh in extreme cases, which are mainly before a  
>> driver
>> has been initialised.
>
> It may also be of use in thorn code, though.
> For example, I am currently using it for some debug code in
> AEIThorns/AEILocalInterp (which is not passed a GH pointer), which
> wants to generate a distinct file name for each processor so it can
> log some debugging information.

This may not work under all circumstances.  Of course, for debugging,  
you do not care about all possible circumstances.

-erik

-- 
Erik Schnetter <schnetter at cct.lsu.edu>

My email is as private as my paper mail.  I therefore support encrypting
and signing email messages.  Get my PGP key from www.keyserver.net.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://www.cactuscode.org/pipermail/developers/attachments/20070112/7faf48ee/attachment.bin