| Re: [eigen] patch to throw std::bad_alloc |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/eigen Archives
]
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] patch to throw std::bad_alloc
- From: Kenneth Riddile <kfriddile@xxxxxxxxx>
- Date: Tue, 16 Dec 2008 10:28:56 -0800 (PST)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=BAp9iOOPuWDv2JI5qLLNb20vjb5UwGAOaAWeSeCf8nBRfWEd0GDy0jlwm0LEyidj/OzZ4UC4lBEts+419GpTfoCpiP5515mNFr0THKa+wFVVjQreq+Nzwm48WDmbXH0D+1HirC5ZIhSf6HzKZzu/Qn1bXppekCTvJtruCrkPTnE=;
--- On Tue, 12/16/08, Benoit Jacob <jacob.benoit.1@xxxxxxxxx> wrote:
> > Ah, yes, that was unintentional and simply a result of
> different coding styles. I'm more used to wrapping the
> contents of a file in the appropriate namespace blocks
> instead of wrapping the #include since it simplifies
> maintenance (reduces unintentional namespace pollution and
> ensures that moving an #include doesn't subtly alter the
> meaning of that file's contents).
>
> Sure, Eigen is just very special in this respect since so
> much code is
> in headers. The current scheme reduces a lot the amount of
> namespace{}
> statements and centralizes them all in a single place, the
> public
> headers.
Actually, being header-only isn't that special. Almost all of Boost is header-only along with most of Intel's TBB and most of STL. As long as those headers are never included somewhere else, then you don't have to worry about accidentally removing things from the Eigen namespace...but we all know that "never" really just means "just far enough in the future to forget important details" when it comes to software development :)
---