On Sep 13, 2012, at 9:25 PM, Dmitry Karpeev wrote:
>
>
> On Thu, Sep 13, 2012 at 9:12 PM, Jed Brown wrote:
> Constructor tab completion is better for DMCreateDA().
>
> But will clash with all the other methods of the form DMDAGetXXX() etc.
> I would vote for converting MatCreateSeqAIJ to Mat
le. Boy I
>> know Wolfgang will not be happy with that :-)
>>
>> Should we just fix the DM sub constructors to follow the style of all
>> the other ones?
>>
>> Barry
>>
>>
>>
>>
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120913/436f1f89/attachment.html>
> Should we just fix the DM sub constructors to follow the style of all
> the other ones?
>
> Barry
>
>
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120913/cbbd3462/attachment.html>
MatCreateSeqAIJ() etc etc etc
but
DMDACreate(), DMRedundantCreate() etc
Now given that normally we list the subclass name right after the base
class in methods, for example KSPGMRESSetRestart() not KSPSetRestartGMRES() it
might make sense to always follow the DMXXXCreat
Dear petsc-dev folks,
as I've just started at the MCS division and met only some
PETSc-developers in person, I would like to take the rather
old-fashioned step of introducing myself to non-MCS developers.
Coming from a microelectronics/numerical mathematics background, my main
work throughout
gt; user:Barry Smith
> > date:Thu Aug 23 08:03:00 2012 -0500
> > files: conf/test include/petscksp.h src/ksp/ksp/utils/schurm.c
> src/mat/interface/matregis.c
> > description:
> > added testexamples_opengl rule
> > changed MatCreateSchurComplement to use the MatCreate_SchurComplement()
> paradigm
> >
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120913/ebc974c5/attachment-0001.html>
On Sep 13, 2012, at 7:55 AM, Jed Brown wrote:
> On Thu, Sep 13, 2012 at 8:50 AM, Barry Smith wrote:
>
> On Sep 12, 2012, at 9:49 PM, Jed Brown wrote:
>
> > This patch seems to do two very unrelated things. More importantly, it
> > makes libpetscmat depend on libpetscksp, thus breaking singl
On Sep 12, 2012, at 9:49 PM, Jed Brown wrote:
> This patch seems to do two very unrelated things. More importantly, it makes
> libpetscmat depend on libpetscksp, thus breaking single-library=0. The
> register routine needs to be moved to src/ksp to fix this.
Yup. My mistake.
I don't
