Re: Boost..

From: John Carson (donaldquixote_at_datafast.net.au)
Date: 12/20/03 

Date: Sun, 21 Dec 2003 01:02:29 +1100

"Tomas Wilhelmsson" <sys2@MoonShield.telia.com> wrote in message
news:pan.2003.12.20.12.39.50.388227@MoonShield.telia.com
> Ok, i need someone to tell me why to use this library that dont even
> seem to want to compile 3 out of 5 times :P
>
> You have to freeze the version with the release, that should make
> problems as you make new versions of the program im sure you want to
> be able to update as much as posible in the maner to just put a new
> version in and recompile, couse if you have to freeze it it atleast
> to me says something .. no standard, crappy lib ...
>
> But im sure its good in its ways but .. who would want something that
> forces you to change your code after each upgrade? :/
>
> Thanks for any answers.

As I understand it, the idea of Boost is to create libraries that fill a
need and may some day become part of the C++ standard. As such it represents
the "bleeding edge" of C++ development. If you want something stable and
standardised, then I think you are looking in the wrong place. Of course,
part of your problem may be with the degree of standard compliance of your
compiler. 

-- 
John Carson
1. To reply to email address, remove donald
2. Don't reply to email address (post here instead)

Relevant Pages

  • Re: C89, size_t, and long
    ... libraries which have useful stuff). ... So because others here can't think of a good reason to use long instead of size_t and you can't prove there is never such a reason, we must all assume there could be a good reason to not use the mechanisms provided by the standard to deal with a problem? ... If you are claiming there is a reason to avoid the mechanisms the standard provides to allow portability then it is up to *you* to prove your point, not up to others to disprove it. ... but you can hardly blame the consequences on the Standard headers. ...
    (comp.lang.c)
  • Re: C89, size_t, and long
    ... libraries which have useful stuff). ... So because others here can't think of a good reason to use long instead of size_t and you can't prove there is never such a reason, we must all assume there could be a good reason to not use the mechanisms provided by the standard to deal with a problem? ... want to have standard headers included in their own headers which ...
    (comp.lang.c)
  • Re: Any Clojure users here?
    ... ABCL and I've been contributing to it for a while (though since some ... from the CL standard or from the Java API, ... You can use CFFI-based libraries in ABCL without ... Yes, but without a Clojure standard, it's hard to know what the "core" ...
    (comp.lang.lisp)
  • Re: comparing doubles for equality
    ... AFAIK there is no ANSI/ISO standard for it. ... Fortran 95 seem to have some built-in operators but it's not clear ... LIA,GIA,ICE libraries for interval methods in C++ from Delisoft ... Actually I've been for quite some months proposing getting together ...
    (comp.programming)
  • Re: "Criticism of the C programming language ??????"
    ... "that's not in the standard, ... rewrites of the compiler. ... PH> They got all the compiler vendors to agree to a common ... or graphics libraries or threading libraries, ...
    (comp.lang.c)