> Okay; I'll see what I can do. This is an API backwards compatibility
> issue, so I'll need to be careful. We'll definitely want a
> --with-getpot-namespace= option, and we'll be bending the rules if we
> don't default to the previous-API-compatible value for at least one
> release...
>
> Would
On Wed, 11 Oct 2017, simone wrote:
I realize that my wording has been possibly misleading (I apologize for
my English). What I meant by "forced" is not that I already have
external users, but that my library once released will be delivered to
users using the standard GetPot version, and using a
I really thank you for your availability and for your help.
> I'm afraid our email list typically strips attachments. I think I
> understand the problem from your description alone, but if I'm wrong
> then you could send to my email address specifically with the
> attachment.
>
Nevermind the atta
On Wed, 11 Oct 2017, simone via Libmesh-users wrote:
I apologize if this is not the right place to report this problem,
This is the right place to report it, yes. We had to fork from the
original GetPot after newer versions from the original software author
stopped using an open source licen
Dear Libmesh developers,
I apologize if this is not the right place to report this problem, or if
it has been already raised by someone else. I searched previous digests
for a solution, but I did not find anything similar.
I'm having trouble using GetPot library (not the one included in libMesh
i
