changes for next PETSc release

2008-03-17 Thread Lisandro Dalcin
On 3/16/08, Barry Smith bsmith at mcs.anl.gov 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

changes for next PETSc release

2008-03-17 Thread Matthew Knepley
On Sun, Mar 16, 2008 at 7:38 PM, Barry Smith bsmith at mcs.anl.gov 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

changes for next PETSc release

2008-03-17 Thread Aron Ahmadia
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

changes for next PETSc release

2008-03-17 Thread Richard Katz
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 changing

changes for next PETSc release

2008-03-17 Thread Barry Smith
On Mar 17, 2008, at 10:23 AM, Matthew Knepley wrote: On Sun, Mar 16, 2008 at 7:38 PM, Barry Smith bsmith at mcs.anl.gov 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

changes for next PETSc release

2008-03-17 Thread Matthew Knepley
On Mon, Mar 17, 2008 at 12:27 PM, Barry Smith bsmith at mcs.anl.gov 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

changes for next PETSc release

2008-03-17 Thread Barry Smith
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 bsmith at mcs.anl.gov wrote: 2) properly name-space PETSc by putting a Petsc in front of all PETSc objects, function names etc (this will require

changes for next PETSc release

2008-03-17 Thread Lisandro Dalcin
Well, Fortran 90 modules provide a sort of namespace support, I think. On 3/17/08, Barry Smith bsmith at mcs.anl.gov 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 bsmith at mcs.anl.gov

changes for next PETSc release

2008-03-17 Thread Matthew Knepley
On Mon, Mar 17, 2008 at 1:06 PM, Barry Smith bsmith at mcs.anl.gov 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

changes for next PETSc release

2008-03-17 Thread Boyce Griffith
Matthew Knepley wrote: On Mon, Mar 17, 2008 at 1:06 PM, Barry Smith bsmith at mcs.anl.gov 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