<div dir="ltr">Thank you very much everybody for the prompt help.<div>Amal<br><br><div class="gmail_quote">On Mon, Sep 27, 2010 at 8:15 PM, Jed Brown <span dir="ltr"><<a href="mailto:jed@59a2.org">jed@59a2.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Agree on both points.<br>
<div><div></div><div class="h5"><br>
On Mon, Sep 27, 2010 at 19:13, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
><br>
> On Sep 27, 2010, at 12:09 PM, Jed Brown wrote:<br>
><br>
>> On Mon, Sep 27, 2010 at 19:07, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
>>> This could be done by putting into the C code the usual "case" handling for the new viewer and then have<br>
>>> it dispatch back to the python code.<br>
>><br>
>> Right, but then it sounds like you're distributing the viewer with<br>
>> PETSc (instead of petsc4py of some third-party plugin).<br>
><br>
> No, the viewer is distributed with petsc4py or some other package, but yes the PETSc source code is augmented also. In fact one could organize it so one extra "dispatcher" could support many different python viewers; essentially a shell Viewer :-)<br>
><br>
><br>
>> We had a long<br>
>> thread a while ago about making multiple dispatch runtime-extensible<br>
>> in both arguments.<br>
><br>
> I was just pointing out that something "quick and dirty" can be done now without the multiple dispatch system.<br>
><br>
> I am not opposed to a multiple dispatch system to handle this; but no one has proposed specifics for such a system that pass the "good enough for PETSc" test.<br>
><br>
> Barry<br>
><br>
>><br>
>> Jed<br>
><br>
><br>
</div></div></blockquote></div><br></div></div>