Ryan Curtin ada6228388 Preprocessor macros are bad when they make programs perform in ways users don't expect. ...

Preprocessor macros are bad when they make programs perform in ways users don't expect.
Preprocessor macros are bad when they make programs perform in ways users don't expect.
Preprocessor macros are bad when they make programs perform in ways users don't expect.
Preprocessor macros are bad when they make programs perform in ways users don't expect.

In this case OBJECT_TRAVERSAL() had no idea what to do with a std::string, and it's generating all this weird copy constructor crap and things aren't handled right.
Todo: move away from InitCopy() everywhere.  And Init().  And InitXXX().  They make constructors for a reason, and we will assume our users are smart enough to not copy 2GB objects a bunch of times.

2010-06-16 00:36:31 +00:00

..

fastlib3

Move fastlib3 to a branch of fastlib

2010-01-31 22:37:53 +00:00

fastlib-armadillo

Remove last references to Vector class

2010-06-09 20:25:11 +00:00

fastlib-cmake

Undoing serialization for matrix as of now

2010-05-12 15:27:40 +00:00

fastlib-old

Move fastlib-old (originally 'fastlib') to fastlib/branches/fastlib-old where it

2010-01-31 22:31:55 +00:00

fastlib-stl

Preprocessor macros are bad when they make programs perform in ways users don't expect.

2010-06-16 00:36:31 +00:00