On Sat, Oct 27, 2012 at 10:41 AM, Roy Stogner wrote:
> Sorry for the mess;
>
Meh - it happens. It appears to be compiling today ;-)
Derek
--
WINDOWS 8 is here.
Millions of people. Your app in 30 days.
Visit The Window
Hi Ben,
Actually, It is not important to me. I'm trying to learn object oriented
design and meta-programming skills for scientific computing from libMesh.
Right now, I only use a very thin layer of encapsulation in my code.
Coupling is very tight there. I read some source code of libMesh and ask
s
Reviving this thread for the DiffContext accessor changes before the next
release.
Attached patch, I believe, provides accessors for everything that should be
protected in DiffContext. Wanted to get opinions before I went through the
rest of the library code. I went through and updated, I believe,
On Sun, 28 Oct 2012, Paul T. Bauman wrote:
> Reviving this thread for the DiffContext accessor changes before the next
> release.
> Attached patch, I believe, provides accessors for everything that
> should be protected in DiffContext. Wanted to get opinions before I
> went through the rest of
On 10/28/2012 07:56 PM, Roy Stogner wrote:
>
> On Sun, 28 Oct 2012, Paul T. Bauman wrote:
>
>> Reviving this thread for the DiffContext accessor changes before the next
>> release.
>> Attached patch, I believe, provides accessors for everything that
>> should be protected in DiffContext. Wanted t
Thanks for catching and fixing this. I suppose it's a holdover habit from
C/PETSc programming:
PetscNew memzeros the allocated memory, so struct members of pointer type
are effectively zero-initialized.
I guess I always assumed that pointers are zero-initialized by default.
Looking at the C++11 s
