I can if you'd like, but that brings up the next question...

My next patch that adds unique_ids and named entities is already making
several changes to the existing format.  It'll have a new version number,
"libmesh-0.9.2+" but will still handle version 0.7.0 formats just fine.
Since UniqueIDs are going to default to 8-bytes automatically is it time to
hit the switch and default XDR format to 64-bit?  There really isn't much
of a change when using XDA, but XDR files will be almost twice as big.  It
is 2013 and these files are still plenty small, thoughts?

Alternatively, I could allow the user to configure that option and override
it if *any* of the stored types are sized to 64-bit.  The only issue is
that we'll have the potential for people in the same organization to
produce different sized XDR/XDA files...  In that case do we need another
flag in the XDR/XDA format (since we are changing everything else anyway)
to store the "stored" encoding size?

Thoughts?
Cody


On Fri, Oct 11, 2013 at 12:56 PM, roystgnr <notifications@github.com> wrote:

> In src/mesh/xdr_io.C:
>
> > @@ -41,6 +41,7 @@
> >  namespace libMesh
> >  {
> >
> > +//#define LIBMESH_USE_64BIT_XDR
>
> I was about to say "take this back out", but actually it makes a pretty
> good shorthand for "we don't have a configure option for this yet".
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/libMesh/libmesh/pull/156/files#r6923719>
> .
>