On Fri, Jun 24, 2011 at 3:10 PM, Vijay S. Mahadevan wrote:
> Roy,
>
> I wanted to ask this to Guido in the deal.ii list but anyway here is
> my question.
>
> Is this journal for papers based on completely open source software
> alone that can be replicated/verified by anyone ? What I mean is that
Roy,
I wanted to ask this to Guido in the deal.ii list but anyway here is
my question.
Is this journal for papers based on completely open source software
alone that can be replicated/verified by anyone ? What I mean is that
if I use say petsc+libMesh+my own framework, does the journal require
me
On Jun 24, 2011, at 2:46 PM, John Peterson wrote:
> On Fri, Jun 24, 2011 at 2:25 PM, Roy Stogner wrote:
>>
>> Any preference for what we should name a macro whose behavior is
>> essentially "do what libmesh_assert() does even when NDEBUG is
>> defined"?
>
> I think this is called an "if test",
On Fri, 24 Jun 2011, John Peterson wrote:
> On Fri, Jun 24, 2011 at 2:25 PM, Roy Stogner wrote:
>>
>> Any preference for what we should name a macro whose behavior is
>> essentially "do what libmesh_assert() does even when NDEBUG is
>> defined"?
>
> I think this is called an "if test", right?
H
On Fri, Jun 24, 2011 at 2:25 PM, Roy Stogner wrote:
>
> Any preference for what we should name a macro whose behavior is
> essentially "do what libmesh_assert() does even when NDEBUG is
> defined"?
I think this is called an "if test", right?
> I'm not sure when we'd get around to using such a th
Dear libMesh users:
We are pleased to announce the launch of the Archive of Numerical
Software (ANS). ANS is a free, peer-reviewed, high quality, open-access
journal publishing research of numerical methods that are implemented
based on, or extend certain large-scale numerical libraries, includin
Any preference for what we should name a macro whose behavior is
essentially "do what libmesh_assert() does even when NDEBUG is
defined"?
I'm not sure when we'd get around to using such a thing in the library
(maybe sparingly in the MeshInput subclasses?), but in application
code at least there's
On Fri, 24 Jun 2011, Derek Gaston wrote:
> I'm thinking of changing lines in Make.common.in around 222 from:
>
> libmesh_CXXFLAGS += @CXXFLAGS_OPT@
>
> to
>
> libmesh_CXXFLAGS := @CXXFLAGS_OPT@ $libmesh_CXXFLAGS
>
> The reason is that the way it is setup now doesn't allow users to actually
> ov
I'm thinking of changing lines in Make.common.in around 222 from:
libmesh_CXXFLAGS += @CXXFLAGS_OPT@
to
libmesh_CXXFLAGS := @CXXFLAGS_OPT@ $libmesh_CXXFLAGS
The reason is that the way it is setup now doesn't allow users to actually
override the flags libMesh picks! For instance on my particul
