I managed to get my stuff built using all shared libraries on OS X, but
I came across the following problems:
- I had to hack "boost/format/feedargs.hpp" to remove the static
variable (I have explained in other posts why).
- I am going to work around this by only having a single include point
Martin Wille wrote:
I'm currently considering adding gcc-3.3.1/stlport to the tests.
Since we are using boost/stlport/gcc-3.3.1...
1) What kind of resources does it take to run the regression tests?
2) Would it be helpful if we ran them? Could the community make use of
our test results? How?
RUSSEL HILL wrote:
Trey Jackson <[EMAIL PROTECTED]> writes:
ps. On a related note: do people have pointers to documentation on
what bugs exist in stlport 4.5.3, i.e. what gcc has fixed?
FWIW...
Today we managed to get our project over to gcc-3.3.1,
STLport-4.5-0119, and boost 1.30.2.
There ap
Trey Jackson wrote:
Just a question I thought of while looking at the Boost regression
test results.
It appears that stlport is only used with gcc 2.95.3 (and in Windows
with Intel's C++ compiler and MS C++ 6.0).
Is boost moving away from supporting stlport?
There is no such intention.
>
On Tuesday, August 19, 2003, at 11:56 AM, David Abrahams wrote:
This release was managed by Dave Abrahams with the generous and
dedicated help of Aleksey Gurtovoy and Misha Bergal of
Meta-Communications, Inc., and of Martin Wille.
We expect this to be the last release in the 1.30.x chain; see
On Monday, August 18, 2003, at 10:31 PM, Paul A. Bristow wrote:
Agreed - but what do we do if NOT is_iec559?
Give up? #error "Can only work with IEEE 754!"
Or choose a massive amount of decimal digits? eg 40?
Why not just use what we're currently doing, use
numeric_limits<>::digits10 and hope
On Wed, 20 Aug 2003 08:30:38 +1000, Chris Trengove wrote
> "Jeff Garland" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > Yes at the moment there is really no effect because the library doesn't
> > contain any time functions. It may not stay this way. And I agree that
> the
> > p
I am using the unit test framework on Solaris 5.8 using workshop 6
I can't get BOOST_MESSAGE to print anything.
Here is the output for program:
***
Running 1 test case...
*** No errors detected
***
I was expecting "entering registr
Trey Jackson <[EMAIL PROTECTED]> writes:
ps. On a related note: do people have pointers to
documentation on
what bugs exist in stlport 4.5.3, i.e. what gcc has
fixed?
FWIW...
Today we managed to get our project over to gcc-3.3.1,
STLport-4.5-0119, and boost 1.30.2.
There appears to be a disco
Walter Landry <[EMAIL PROTECTED]> writes:
> Brian Gray <[EMAIL PROTECTED]> wrote:
>> Should we (do we?) have some spreadsheet enumerating various filesystem
>> features, quirks, and limitations for whatever systems we can find, and
>> using that as a reference regarding how to organize features
Brian Gray <[EMAIL PROTECTED]> wrote:
> Should we (do we?) have some spreadsheet enumerating various filesystem
> features, quirks, and limitations for whatever systems we can find, and
> using that as a reference regarding how to organize features like
> paths, file references, forks, or whatev
Trey Jackson <[EMAIL PROTECTED]> writes:
> All,
>
> Just a question I thought of while looking at the Boost regression
> test results.
>
> It appears that stlport is only used with gcc 2.95.3 (and in Windows
> with Intel's C++ compiler and MS C++ 6.0).
>
> Is boost moving away from supporting stlp
It surprised me a bit that leaf returns a string instead of a path.
Shouldn't
"foo/bar"/p.leaf()
work?
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
All,
Just a question I thought of while looking at the Boost regression
test results.
It appears that stlport is only used with gcc 2.95.3 (and in Windows
with Intel's C++ compiler and MS C++ 6.0).
Is boost moving away from supporting stlport? Or are the regressions
not being run for some other
David Abrahams wrote:
> This release was managed by Dave Abrahams with the generous and
> dedicated help of Aleksey Gurtovoy and Misha Bergal of
> Meta-Communications, Inc., and of Martin Wille.
>
> We expect this to be the last release in the 1.30.x chain; see our CVS
> repository or its mirrors f
Brian Gray <[EMAIL PROTECTED]> writes:
> On Tuesday, August 19, 2003, at 12:35 AM, Yitzhak Sapir wrote:
>> My feeling from all these examples is that a path string is
>> inherently specific to the system for which it was specified, and
>> can't really be ported to anywhere else. Much like a strin
"Jeff Garland" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Yes at the moment there is really no effect because the library doesn't
> contain any time functions. It may not stay this way. And I agree that
the
> polarity of this seems reversed.
For my purposes, the "split" represe
Hi all
I found remove_vertex member for vector_as_graph isn't implemented.
It's my proposal:
template
void
remove_vertex(typename EdgeList::value_type u,
std::vector& g)
{
typedef typename EdgeList::iterator iterator;
clear_vertex(u, g);
g.erase(g.begin() + u);
Philippe,
You might be interested in the following:
http://www.cuj.com/documents/s=8020/cuj0111ring/ring.htm
(MAPM, A Portable Arbitrary Precision Math Library in C)
AFAICS fairly complete and there's also a handy C++ wrapper...
Regards,
Andreas
__
On Tuesday, August 19, 2003, at 12:35 AM, Yitzhak Sapir wrote:
My feeling from all these examples is that a path string is inherently
specific to the system for which it was specified, and can't really be
ported to anywhere else. Much like a string is usually inherently
specific in its encoding
Philippe A. Bouchard wrote:
> Hi there,
>
> Like I mentionned before, it would be great for Boost to have an
> infinite precision floating point number. You can see an example
> here: http://members.lycos.co.uk/keithmbriggs/doubledouble.html. Of
> course, the doubles could be replaced by long
This release was managed by Dave Abrahams with the generous and
dedicated help of Aleksey Gurtovoy and Misha Bergal of
Meta-Communications, Inc., and of Martin Wille.
We expect this to be the last release in the 1.30.x chain; see our CVS
repository or its mirrors for new developments expected to
[2003-08-19] Douglas Gregor wrote:
>On Monday 18 August 2003 11:42 pm, Jeremy Siek wrote:
>> Hi Doug,
>>
>> Hmm, I just viewed it with a different browser (Apple's Safari instead
>> of and old version of Netscape on a Sun) and now I see lots of newlines
>> (there were none before). Is this a case
Hi,
I have a small patch to is_convertible.hpp that will allow a version of
KCC (__EDG_VERSION__ == 243) to use the *almost* ideal implementation of
is_convertible. The current design only uses the ideal implementation for
__EDG_VERSION__ >= 245, and the current choice fails to compile for me.
On Monday 18 August 2003 11:42 pm, Jeremy Siek wrote:
> Hi Doug,
>
> Hmm, I just viewed it with a different browser (Apple's Safari instead
> of and old version of Netscape on a Sun) and now I see lots of newlines
> (there were none before). Is this a case of non-portability of a html
> tag, or a b
On Tue, 19 Aug 2003 13:25:37 +1000, Chris Trengove wrote
> I have some concerns about the implementation of the "period"
> concept, as given in period.hpp. First of all, the documentation
> (for, say, date_period) talks of the constructor
>
> date_period(date begin,date last)
>
> as creating a
On Mon, 18 Aug 2003 16:28:22 -0400, Beman Dawes wrote
> FWIW, I'm both a native-speaker and familiar with convex hulls.
> Regardless, "span" sounds better to me for use in the context of a
> Date-Time library.
Ok, span it is. Updates checked into CVS
Jeff
_
On Tue, 19 Aug 2003 10:08:51 +1000, Chris Trengove wrote
> The documentation notes that BOOST_DATE_TIME_POSIX_TIME_STD_CONFIG controls
> the choice of the internal time representation, between the "split"
> (32 bit integer + 64 bit integer) and "counted" (64 bit integer only)
> varieties. The doc
Daniel Spangenberg wrote:
Daniel Frey schrieb:
You are correct. It's on my ToDo-list and I will take care of it along
with some other changes that I would like to make to the documentation
(mostly restructuring). Currently, my time doesn't permit much work on
it, but if you'd like to speed things
Hi.
I am trying to get a grip on the BGL internals for the purpose of
extending it and I want to do it the boost-way.
After reading through the source, there seems to be a lot of
non-trivial internal design decisions to implement the actual API
interface.
Does there exists any design documents,
Hello Daniel,
Daniel Frey schrieb:
> You are correct. It's on my ToDo-list and I will take care of it along
> with some other changes that I would like to make to the documentation
> (mostly restructuring). Currently, my time doesn't permit much work on
> it, but if you'd like to speed things up,
Hi there,
Like I mentionned before, it would be great for Boost to have an
infinite precision floating point number. You can see an example here:
http://members.lycos.co.uk/keithmbriggs/doubledouble.html. Of course, the
doubles could be replaced by long doubles, a muldiv() could be easily ad
Aleksey Gurtovoy wrote:
> Things to be done (at large):
[...]
> 4) After the tarballs are ready, pre-publish them, and do another round of
> regressions (on the tarballs).
The regression test results for 1.30.2 zipball are OK. They are available
at:
http://www.meta-comm.com/engineering/index.htm
Daniel Spangenberg wrote:
Since I see strong activities in overworking parts of the documentation,
I
would like to remember the open question concerning the help text
section
"Separate, Explicit Instantiation"
>
> [...]
>
among the "discussees" I think, that we can be assume, that the current
text
--- Gennaro Prota <[EMAIL PROTECTED]> wrote:
> Note that you can't work on "raw memory" in the sense
> that you ignore the type of the objects and treat them as sequences of
> unsigned chars: that's because you could end up treating padding bits = 1 as
> "real bits" (value bits).
Well, that coul
--- Alexander Nasonov <[EMAIL PROTECTED]> wrote:
> Google shows me a few links about bit_iterator.
>
> http://lists.boost.org/MailArchives/boost/msg03435.php
> http://groups.yahoo.com/group/Boost-Users/message/994
>
> Any progress since these messages have been posted?
>
> Definitely, I have an
Hello boosters,
Since I see strong activities in overworking parts of the documentation,
I
would like to remember the open question concerning the help text
section
"Separate, Explicit Instantiation"
http://www.boost.org/libs/utility/operators.htm#explicit_instantiation
During the summer pause I
Daryle Walker schrieb:
> On Sunday, August 17, 2003, at 10:33 PM, Paul A. Bristow wrote:
>
> [SNIP]
> > But you are right that it would be better to check that
> > numeric_limits::digits exists and isn't something silly before using
> > the formula. With all the built-in floating point types it s
Google shows me a few links about bit_iterator.
http://lists.boost.org/MailArchives/boost/msg03435.php
http://groups.yahoo.com/group/Boost-Users/message/994
Any progress since these messages have been posted?
Definitely, I have an interest in bit_iterator. But I don't have enough time
to implem
This discussion started off with various questions, including the following:
1) Why does it implement any restrictions, by default, on what kind of files it allows?
2) I don't understand why boost::filesystem wants to restrict me to a set of filenames
that are portable
But the discussion quickly
40 matches
Mail list logo
