|
|
|
|
||||||
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 (permalink) |
|
Messages: n/a
Hébergeur: |
Hi Roland,
> > IMO, the age of 'boosted' libraries is gone. A library may be This seems quite biased. > configurable in some way as long as it provides reasonable defaults Well, that's the plan - to provide reasonable defaults. > ('convention over configuration'). But configuration via policy > template parameters introduces high, unnecessary complexity that > hardly any real-world user is willing to accept. > It all depends on ease of use. I will definitely provide defaults and easy configuration for different scenarios. Best, John -- http://John.Torjo.com -- C++ expert .... call me only if you want things done right [ See http://www.gotw.ca/resources/clcm.htm for info about ] [ comp.lang.c++.moderated. First time posters: Do this! ] |
|
|
|
#2 (permalink) |
|
Messages: n/a
Hébergeur: |
On Mon, 15 Oct 2007 03:52:23 CST, jtorjo2007@yahoo.com wrote:
>> configurable in some way as long as it provides reasonable defaults > >Well, that's the plan - to provide reasonable defaults. > >> ('convention over configuration'). But configuration via policy >> template parameters introduces high, unnecessary complexity that >> hardly any real-world user is willing to accept. > >It all depends on ease of use. I will definitely provide defaults and >easy configuration for different scenarios. The problem with policy template parameters is that they are an unavoidable part of the user interface and e.g. pop up in compiler error messages. -- Roland Pibinger "The best software is simple, elegant, and full of drama" - Grady Booch [ See http://www.gotw.ca/resources/clcm.htm for info about ] [ comp.lang.c++.moderated. First time posters: Do this! ] |
|
|
|
#3 (permalink) |
|
Messages: n/a
Hébergeur: |
> >It all depends on ease of use. I will definitely provide defaults and
> >easy configuration for different scenarios. > > The problem with policy template parameters is that they are an > unavoidable part of the user interface and e.g. pop up in compiler > error messages. > Then all I have to do is make sure there won't be any compile errors :P That is, initializing the lib will be just a few lines of code. Best, John -- http://John.Torjo.com -- C++ expert .... call me only if you want things done right [ See http://www.gotw.ca/resources/clcm.htm for info about ] [ comp.lang.c++.moderated. First time posters: Do this! ] |
|
|
|
#4 (permalink) |
|
Messages: n/a
Hébergeur: |
On Oct 15, 7:04 pm, rpbg...@yahoo.com (Roland Pibinger) wrote:
> > The problem with policy template parameters is that they are an > unavoidable part of the user interface and e.g. pop up in compiler > error messages. I agree, but care can be taken to make the error messages at least readable. I use the boost concept checking library to ensure that the template parameters passed in meet the requirements, this should produce much shorter and more immediate error messages when something is wrong with a policy. It will be improved even more with C++0x with concepts being built right into the language. Neal -- [ See http://www.gotw.ca/resources/clcm.htm for info about ] [ comp.lang.c++.moderated. First time posters: Do this! ] |
|
![]() |
| Outils de la discussion | |
|
|