Well, Fortran 90 modules provide a sort of namespace support, I think.
On 3/17/08, Barry Smith wrote:
>
> Fortran90 has namespaces??
>
>
> On Mar 17, 2008, at 12:59 PM, Matthew Knepley wrote:
>
> > On Mon, Mar 17, 2008 at 12:27 PM, Barry Smith
> > wrote:
> 2) properly name-space
>
>
> 2) properly name-space PETSc by putting a Petsc in front of all
> PETSc objects, function names etc
> (this will require changing a few names also to keep them below
> the 32 character limit). This will
> be very painful change for some users who are not comfortable
> ever chang
Matthew Knepley wrote:
> On Mon, Mar 17, 2008 at 1:06 PM, Barry Smith wrote:
>> Fortran90 has namespaces??
>
> Not in the way I was thinking. Damn F90. Anyway, it looks like you can
> selectively
> use interface modules, so we might be able to get away with redundant names
> by just not u
On Mon, 17 Mar 2008, Matthew Knepley wrote:
> On Mon, Mar 17, 2008 at 1:06 PM, Barry Smith wrote:
> >
> > Fortran90 has namespaces??
>
> Not in the way I was thinking. Damn F90. Anyway, it looks like you
> can selectively use interface modules, so we might be able to get
> away with redu
Yes, but you have to do the same for every Mat routine. That's the
hard part to maintaing when new functions are added.
Perhaps then a macro like the following would help to maintain the new
interface and the legacy one always up-to-date
#define PETSC_NS(DECL) \
Petsc##DECL
and then
PetscE
On Mon, Mar 17, 2008 at 1:06 PM, Barry Smith wrote:
>
> Fortran90 has namespaces??
Not in the way I was thinking. Damn F90. Anyway, it looks like you can
selectively
use interface modules, so we might be able to get away with redundant names
by just not using them together.
I jsut really
Fortran90 has namespaces??
On Mar 17, 2008, at 12:59 PM, Matthew Knepley wrote:
> On Mon, Mar 17, 2008 at 12:27 PM, Barry Smith
> wrote:
2) properly name-space PETSc by putting a Petsc in front of all
PETSc
objects, function names etc
(this will require chang
On Mon, Mar 17, 2008 at 12:27 PM, Barry Smith wrote:
> >> 2) properly name-space PETSc by putting a Petsc in front of all PETSc
> >> objects, function names etc
> >> (this will require changing a few names also to keep them below
> >> the 32 character limit). This will
> >> be very
This would be nice. Maybe we could do this with appropriate
regular expressions. Sed and awk :-)
Barry
On Mar 17, 2008, at 10:04 AM, Richard Katz wrote:
>>
>>
>> 2) properly name-space PETSc by putting a Petsc in front of all
>> PETSc objects, function names etc
>>(this will req
On Mar 17, 2008, at 10:23 AM, Matthew Knepley wrote:
> On Sun, Mar 16, 2008 at 7:38 PM, Barry Smith
> wrote:
>>
>>
>> There are two significant changes I'd like to see before the
>> next PETSc release:
>>
>> 1) remove the overly complicated (from a user perspective) matrix
>> subclassing
On 3/16/08, Barry Smith wrote:
> There are two significant changes I'd like to see before the
> next PETSc release:
>
> 1) remove the overly complicated (from a user perspective) matrix
> subclassing for the various external
> matrix solver packages and replace with MatSolverSetType
Can the namespace issue be fixed with some macro magic?
#ifdef UNIQUE_PETSC_NAMESPACE
#define Mat PetscMat
#endif
...
...
#undef Mat
This seems like it would satisfy both parties, and a compiler/build
flag could uniqueify the namespace if needed.
~A
On Mon, Mar 17, 2008 at 11:23 AM, Matthew K
On Sun, Mar 16, 2008 at 7:38 PM, Barry Smith wrote:
>
>
> There are two significant changes I'd like to see before the
> next PETSc release:
>
> 1) remove the overly complicated (from a user perspective) matrix
> subclassing for the various external
> matrix solver packages and repl
On Mar 17, 2008, at 9:43 AM, Lisandro Dalcin wrote:
> On 3/16/08, Barry Smith wrote:
>> There are two significant changes I'd like to see before the
>> next PETSc release:
>>
>> 1) remove the overly complicated (from a user perspective) matrix
>> subclassing for the various external
>>
There are two significant changes I'd like to see before the
next PETSc release:
1) remove the overly complicated (from a user perspective) matrix
subclassing for the various external
matrix solver packages and replace with MatSolverSetType() -
mat_solver_type that simply
15 matches
Mail list logo
