[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PETSc-FUN3D Code
- To: petsc-dev@xxxxxxxxxxx
- Subject: Re: PETSc-FUN3D Code
- From: "Matthew Knepley" <knepley@xxxxxxxxx>
- Date: Sat, 20 Oct 2007 17:00:58 -0500
- Cc: "Dinesh Kaushik" <kaushik@xxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=7g5XmN8PlwOpFjZ2sBdCJ4fwElWUjILQsZDm0ZedKnc=; b=Phv1Cvu5TMu2wxnvbWVf8HT+Hf7qgIvL07E3CBa1YDcM0NuZpp2pJara8gFApdu8CE/rC+avYgRjj0TX8yJo5WRo002w3nuJhz5Q3vFfn0niIa5V7g2kJgPnazVfxMnVYRSx68vsFMDkgs3cRTl9Raq5VtpwV+2zAyWa0xk+mxE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JlhNXJ7eRWSqXgdYNB0dLv8Ugxaq8kazBsGdAiYZQRAl72BfcEvhHPjwLuymKT4MmfzV/ts+Q2Scv1hGxo5Q8UEXf+FIOeX0CCsJkULqxksiaDJSvDXQR+PMr/kuiuRoR1kyaeVxAkPsEtAZ/FvO7nPrTQrnIWtyzEmqfxeYImk=
- In-reply-to: <Pine.OSX.4.64.0710201647200.14706@bsmith.mcs.anl.gov>
- References: <4718B5F6.3040301@mcs.anl.gov> <Pine.LNX.4.64.0710191222010.3920@asterix> <4718F0C6.7080908@mcs.anl.gov> <Pine.LNX.4.64.0710191328580.3920@asterix> <Pine.LNX.4.64.0710191359050.3920@asterix> <Pine.LNX.4.64.0710191422350.3920@asterix> <Pine.LNX.4.64.0710191438470.3920@asterix> <47193D94.5020600@mcs.anl.gov> <Pine.LNX.4.64.0710201047000.3920@asterix> <Pine.OSX.4.64.0710201647200.14706@bsmith.mcs.anl.gov>
- Reply-to: petsc-dev@xxxxxxxxxxx
- Sender: owner-petsc-dev@xxxxxxxxxxx
I actually like the autoconf solution. If the type is not found (size_t)
then just typedef it as something.
Matt
On 10/20/07, Barry Smith <bsmith@xxxxxxxxxxx> wrote:
>
> Satish,
>
> I don't know; there are pros and cons to the two
> approaches.
>
> Why not PetscSize_T? I admit both look stupid, but the
> _ at least matches the standard C style.
>
> Any comments from the community?
>
> Barry
>
>
>
> I would like to keep size_t as the argument
>
> On Sat, 20 Oct 2007, Satish Balay wrote:
>
> > On Fri, 19 Oct 2007, Dinesh Kaushik wrote:
> >
> > > > > Perhaps need a PetscSizeT or some new datatype for this purpose that
> > > > > gets set correct for both C & fortran side..
> >
> > Barry,
> >
> > Is it ok to do this change? The prototypes of the following functions
> > will need to be changed to use PetscSizeT instead of size_t;
> >
> > [alternative is to use size_t on the C side - but PetscSizeT on the
> > fortran side - but this is inconsistant]
> >
> > thanks,
> > Satish
> >
> > -------------------
> > PetscBagCreate
> > PetscFileRetrieve
> > PetscGetArchType
> > PetscGetDate
> > PetscGetDisplay
> > PetscGetFullPath
> > PetscGetHomeDirectory
> > PetscGetHostName
> > PetscGetProgramName
> > PetscGetRelativePath
> > PetscGetTmp
> > PetscGetUserName
> > PetscGetWorkingDirectory
> > PetscLs
> > PetscMalloc
> > PetscMalloc2
> > PetscMalloc3
> > PetscMalloc4
> > PetscMalloc5
> > PetscMalloc6
> > PetscMalloc7
> > PetscMemcmp
> > PetscMemcpy
> > PetscMemmove
> > PetscMemzero
> > PetscOptionsGetenv
> > PetscOptionsGetString
> > PetscOptionsString
> > PetscSetMalloc
> > PetscSNPrintf
> > PetscStrlen
> > PetscStrncat
> > PetscStrncmp
> > PetscStrncpy
> > PetscStrreplace
> > PetscSynchronizedFGets
> > PetscVSNPrintf
> >
> >
>
>
--
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which
their experiments lead.
-- Norbert Wiener