[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: changes for next PETSc release
- To: petsc-dev@xxxxxxxxxxx
- Subject: Re: changes for next PETSc release
- From: "Matthew Knepley" <knepley@xxxxxxxxx>
- Date: Mon, 17 Mar 2008 10:23:19 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=J7IULafZOtI0H61e28LtIOSpgJ/JBLPDKvuzyuW/PXM=; b=vSQSo9Q+MgNZgT1IN7Z6VDopbtuIhlpsVhLerg23XRd9wKf4kbLOqZ59R5w7CvwjWersDot93sMCLwG6JYGsmjqBM/R4B420rFVDzeNYv4CmfjjA8QAinrouGMgkdoblM3FeljGDgQNx/Z0s0JtJOY4OJVNsaD/ccgxsijazSfw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Hy9wRdUxheytDqdjPYObvDVIixgVfDEP2lH38hQG0iEOrj2vPxE+Q9tX5Pvg/OfYMteTHWZSjqa77A1QqJfVyG0NxwLMXAWOEEO5cPY2j5OaYAGUPzgP1vlBJbLFlaLvHhXkxNh7SmWWGKZbJ9lqnxUPByrNu9mbuyK0FAZXWGA=
- In-reply-to: <E9103C03-5EB9-406C-AA6E-AA918A30C2D4@mcs.anl.gov>
- References: <E9103C03-5EB9-406C-AA6E-AA918A30C2D4@mcs.anl.gov>
- Reply-to: petsc-dev@xxxxxxxxxxx
- Sender: owner-petsc-dev@xxxxxxxxxxx
On Sun, Mar 16, 2008 at 7:38 PM, Barry Smith <bsmith@xxxxxxxxxxx> 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 MatSolverSetType() -
> mat_solver_type <type> that simply
> flips the various factorization/solver functions with those
> requested and
This seems not too hard. Just a layer on top to run the code a user must
run now.
> 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 code, hence I hesitate
> to do it, but it is the right thing to do and should have been
> done originally.
I guess I still do not see the need for this. NIMROD is a not a sufficient
driver in my mind. If we really want namespaces, use a real language that
has namespaces. There are plenty. If we are still using C, I say we stick
with the old division. The imposition of this much pain on the overwhelming
majority of users seems unjustified.
Namespaces issues can be trivially fixed in say C++, which we should do.
Matt
> Maybe we can do a release in around a couple of months, it would
> be 2.4
>
> Barry
>
>
>
--
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which
their experiments lead.
-- Norbert Wiener