On Thu, Apr 30, 2009 at 01:20:02PM +0200, DOLFIN wrote: > One or more new changesets pushed to the primary dolfin repository. > A short summary of the last three changesets is included below. > > changeset: 6074:0789c3afacbac728dd35cbad3c1ca2362ac2a1a2 > tag: tip > parent: 6073:45fa9f91f8fc0e9a0ab837f8803cff74560ac7b4 > parent: 6072:0cbfb4cb4776c4585af43d984203f6c6d0868a83 > user: "Ola Skavhaug <[email protected]>" > date: Thu Apr 30 13:22:24 2009 +0200 > files: > description: > merge > > > changeset: 6073:45fa9f91f8fc0e9a0ab837f8803cff74560ac7b4 > parent: 6046:3b31498da99de25e26b25716da37cc28b4cb2b9d > user: "Ola Skavhaug <[email protected]>" > date: Thu Apr 30 13:22:14 2009 +0200 > files: dolfin/log/Logger.cpp dolfin/log/Logger.h > dolfin/log/Progress.cpp dolfin/log/log.cpp dolfin/log/log.h > dolfin/mesh/MeshPartitioning.cpp dolfin/parameter/parameters.cpp > description: > Fix some CamelCaps in logger, and asses stream_message for printing out > arbitrary length messages (the va_list today uses a stativ char buffer of > length 256, and hence long streams are trunkated. Fixed global entity > numbering.
Isn't it possible to overload message()? On a related note, I suggest that we rename the message() function to info(). That way the naming agrees with the Python logging module and also with the naming in UFL and FFC. Any objections to this? -- Anders
signature.asc
Description: Digital signature
_______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev
