Re: [petsc-dev] configure issues
9 Feb
2011
9 Feb
'11
6:05 a.m.
On Wed, Feb 9, 2011 at 12:56, Matthew Knepley <[email protected]> wrote:
We used to have everything in the preprocessor, and we could happily edit that and never have to think about Python at all. We abandoned that approach because it was too complicated, prone to break, and we spent all of our petsc-maint time on it.
I don't know what examples you are referring to, I started with PETSc in 2004. I don't see a lot of logic currently being done on the Python side and used from C, petscconf.h does not have logic in it. No C source files or function bodies are currently generated by Python. It sounds like you want to generated imperative code in Python and call that from C. I think that would add complexity.
5662
Age (days ago)
5662
Last active (days ago)
0 comments
1 participants
participants (1)
-
Jed Brown