[petsc-dev] petsc release soon

[Stefano Zampini]

Are you planning to include pcbddc in the next release?

It works, but some parts of PCBDDC code are not fully developed as we
decided with Jed (primarly, the MatPartitioning procedure for multilevel).

In case you want to include it into the next release, how many days I have
to work on the code until the release ?

2012/3/12 Jed Brown <jedbrown at mcs.anl.gov>

> On Mon, Mar 12, 2012 at 14:40, Barry Smith <bsmith at mcs.anl.gov> wrote:
>
>>  I still like including the private in the name since it makes clear they
>> are private include files.
>
>
> Cool, glad that's out of the way.
>
> Now about namespacing all the variables in the makefiles. This is an
> opportunity to clarify/normalize variable names. I don't know what
> SL_LINKER is, for example.
>
> Also, should there be an "exported" version that makes some of the PETSC
> symbols public? (I think so, even just for internal use, because I don't
> want to type ${PETSC_MPIEXEC}, ${PETSC_DIFF}, ${PETSC_PYTHON}, etc in all
> the makefiles.)
>



-- 
Stefano
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120313/ad2df743/attachment.html>