Forward Inline
Original Message
Message-ID: [EMAIL PROTECTED]
Newsgroups: comp.lang.c++.moderated
Subject: Re: OO design: Is errno Exception?
References: ... [EMAIL PROTECTED]
Early Ehlinger wrote:
Alexander Terekhov [EMAIL PROTECTED] wrote:
Early Ehlinger wrote:
[...]
Beman Dawes wrote:
Providing both the fine-grained and the coarse-grained headers lets the
users decide which they prefer.
Sounds reasonable. CVS updated.
___
Unsubscribe other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Somewhere in the E.U., le 28/05/2003
Bonjour
In article [EMAIL PROTECTED],
Reece Dunn [EMAIL PROTECTED] wrote:
I have added support for output of quaternions and octonions using my I/O
Formatting Manipulators library to provide custom formatting. While testing
Thank you!
the
Russell Hind wrote:
Trevor Taylor wrote:
Who? Me?
I think Peter meant Alexander
I got the message. I'll post refcountthread_safety,
typename integer_t once I'll have some time for it. It won't include
atomic implementation(s), however. ;-)
regards,
alexander.
Hubert Holin wrote:
GNU C++ 2.95.3-5
cannot find the limits standard header file (is this me?!)
I'd like to know. I do not currently have access to an installed
copy of this compiler, but it's one for which quite some energy was
expended to make things work.
AFAIK it's a known problem
Somewhere in the E.U., le 28/05/2003
Bonjour
In article [EMAIL PROTECTED],
Marcelo E. Magallon [EMAIL PROTECTED] wrote:
[SNIP]
The patch makes a declaration for the function in 4. and pushes its
definition to the end of the file. That makes the compiler happy. I
don't think this
Hi David and Dave,
On Tue, 27 May 2003, David Abrahams wrote:
dave David Pearce [EMAIL PROTECTED] writes:
dave
dave David,
dave
dave I think I had the same problems when I implemented the reverse_graph
dave adaptor, and never found a good answer :(
dave
dave Thanks for the reply. Looking
Rozental, Gennadiy [EMAIL PROTECTED] writes:
desc.add_options()
// first argument is options name
// second argument is parameter name
// third argument is description
(output, file, output file)
;
This means that one comment line is added
I've received a few suggestions for methods to achieve non-leaking
cyclic smart pointers (henceforth called uber pointers). I've looked
into some of them. Following is a report on what I've found.
Here is my context: I want to write a library L consisting of a set of
interconnected classes,
John Torjo wrote
I have adopted a Java-style approach to enumerated-style values (don't
know
if this is the best approach, just the way that I do it now). For
example:
class WhatIsTheMatrix
{
public:
typedef unsigned char type;
public:
static const type TheWhat = 0;
-Original Message-
From: Larry Evans [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 7:29 AM
To: Boost mailing list
Subject: [boost] Re: smart_ptr suggestion: Support decrementing
shared_ptr'scount,forself-references
Schoenborn, Oliver wrote:
Circular refs are easy to
Vladimir Prus [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Gennadiy Rozental wrote:
[snip]
2. Layered design.
This has many
problems:
a. Limit number of supported styles die to bitmap limitation
The number of directly supported styles will always be limited. For
hi there,
I'm trying to load a plugin from the same directory the application was
run from, so I'm doing the following:
int main(int argc, char **argv)
{
//...
fs::path path(argv[0]);
fs::path dir(path.branch_path());
//...
but as soon as I start the application as './application', I get
Larry Evans wrote:
Chuck Messenger wrote:
[snip]
Well, it's in too much flux right now -- perhaps if I ever finish it,
I'll post it. It's a concurrency library - an implementation of the
API described in Concurrent Programming in ML.
[snip]
Thanks -- that sounds interesting, too -- I've also
At 12:37 PM 5/28/2003, Stefan Seefeld wrote:
hi there,
I'm trying to load a plugin from the same directory the application was
run from, so I'm doing the following:
int main(int argc, char **argv)
{
//...
fs::path path(argv[0]);
fs::path dir(path.branch_path());
//...
but as soon
Vladimir Prus [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I think it's better to wait for Unicode users to formulate what's needed.
It
seems, for example, that the last approach would work better for me on
Linux.
Visual C++
int
wmain( int argc, wchar_t* argv )
{
Chuck Messenger wrote:
[snip]
collections, put them in object heirarchies, etc). This freedom should
ideally apply both internally (within library L code) and most
importantly, externally (in the code of users of library L). Crucially,
Would you require the users to use a smart pointer instead
Vladimir Prus [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I think the point is that you hardly want both ascii and unicode in single
program. In that case two versions of shared library can be built: for
ascii and unicode, and you will link to the desired one. It's actually
not
On Wed, 28 May 2003 18:40:02 +0200, Beman Dawes wrote:
At 10:10 AM 5/28/2003, Daniel Frey wrote:
Hubert Holin wrote:
GNU C++ 2.95.3-5
cannot find the limits standard header file (is this me?!)
I'd like to know. I do not currently have access to an
installed
Gennadiy Rozental [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
1. Terminology
Terminology chosen by author is confusing to me. In my understanding:
term parameter - originated from 'formal parameter, formal
description of the expected value
term option -
Schoenborn, Oliver wrote:
NoPtr lib -- noptrlib.sourceforge.net
...I saw no mention of detecting dead cyclic object pools.
Can you give me a short example of how NoPtr would even need to detect that
to work correctly? I suspect that if you end up with cyclic object pool you
are using NoPtr
Larry Evans wrote:
Chuck Messenger wrote:
[snip]
collections, put them in object heirarchies, etc). This freedom
should ideally apply both internally (within library L code) and most
importantly, externally (in the code of users of library L). Crucially,
Would you require the users to use a
On Wednesday, May 28, 2003, at 01:08 PM, John Maddock wrote:
The undefind reference comes from posix_api.o . I guess that
s_match_vtable is not used in that file.
You bet it is, you would get the unresolved external if it wasn't
being used
:-)
On MacOS X using g++ version 3.3 in addition to the
I apologize if this has already been asked, but why aren't the libs/mpl/test
sources included in regresssion testing? I know some tests are missing and
some are perhaps as robust as they might be, but it seems some testing is
better than no testing.
I'd like to write an appropriate jamfile and
On Wednesday, May 28, 2003, at 13:04 America/Denver, Chuck Messenger
wrote:
Larry Evans wrote:
Chuck Messenger wrote:
[snip]
collections, put them in object heirarchies, etc). This freedom
should ideally apply both internally (within library L code) and
most importantly, externally (in the
At 03:29 PM 5/28/2003, Eric Friedman wrote:
I apologize if this has already been asked, but why aren't the
libs/mpl/test
sources included in regresssion testing? I know some tests are missing
and
some are perhaps as robust as they might be, but it seems some testing is
better than no testing.
Eric Friedman [EMAIL PROTECTED] writes:
I apologize if this has already been asked, but why aren't the libs/mpl/test
sources included in regresssion testing? I know some tests are missing and
some are perhaps as robust as they might be, but it seems some testing is
better than no testing.
There are 65 tests in that directory. Multiply that by 7 or 8 compilers,
and it would be a huge additional testing load.
IIRC they all compile-time small tests. There should not be any problems.
Gennadiy.
___
Unsubscribe other changes:
I think the names arguments and options are as good as anything else.
It may be so. But I do not understand how the library use these terms.
Vladimir wrote:
option is (name,value) pair
argument is an command line element which is not option.
These definitions unclear to me. Could you give me
David Abrahams wrote:
I'd like to write an appropriate jamfile and include it in CVS, unless
there
are objections.
There's already a Jamfile in libs/mpl/test. It's at version 1.9.
Oops, I missed this. Thanks.
Anyhow, my concern related more to the regression tables. But with Beman's
While I don't find the interface proposed by Vladimir to be offensive,
when you get a pile of function arguments of the same type together a
named parameter interface *can* be a help. I don't think I'd use
operator, though. If it's really about readability I'd tend to
sacrifice some
For a command line parser, the decoupling provided by separate
compilation seems to far outweigh the minor benefits of a header-only
implementation. Just my opinions, of course.
We do not need to sacrify decoupling to provide both header based and
offline versions.
Gennadiy.
Terje,
Also, you may want to get the latest lexical_cast version from the CVS, as
some problems were fixed after 1.30 shipped.
Thanks for the quick reply, the latest lexical_cast.hpp from the CVS fixes
the problem.
I should have checked before posting. but you know some of us guys arn't
that
Larry Evans wrote:
Chuck Messenger wrote:
[snip]
One big problem with this approach is that you end up having to scan
all of your memory. This could (and for me, would) be an outrageous
proposition, as only a tiny portion of memory relates to my object
set. Most of it will be raw data (e.g.
Eric Friedman wrote:
I apologize if this has already been asked, but why aren't the
libs/mpl/test sources included in regresssion testing? I know some
tests are missing and some are perhaps as robust as they might be,
but it seems some testing is better than no testing.
Definitely, and
At 08:19 PM 5/28/2003, Aleksey Gurtovoy wrote:
Eric Friedman wrote:
I apologize if this has already been asked, but why aren't the
libs/mpl/test sources included in regresssion testing? I know some
tests are missing and some are perhaps as robust as they might be,
but it seems some testing is
-Original Message-
From: Chuck Messenger [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 2:35 PM
To: [EMAIL PROTECTED]
Subject: [boost] Cyclic smart pointers (holy grail: the uber-pointer)
Schoenborn, Oliver wrote:
NoPtr lib -- noptrlib.sourceforge.net
...I saw no
I fixed up the I/O library I had reviewed a few months ago. It was
some little things last week, but some big documentation and testing
this week. It's in the sandbox if you want to try it out.
Besides an altered boost/io_fwd.hpp and libs/io/doc/index.html, we
got:
boost/io/array_stream.hpp
I'm trying to fix up the I/O library submission I gave a few months
ago, and came up with an issue with a copy constructor and GCC. I
explicitly wrote a copy constructor for a new stream-buffer class
template. I just added test code that used that constructor.
Everything ran fine on my
In a revamp of the I/O library reviewed a few months ago, I revised the
structure of the test programs to match that given in the Boost.Test
documentation. Is what I have alright? Someone (Beman?) mentioned the
desire for Jamfiles; but I don't use Jam, so I don't know if that's
needed for
Daryle Walker [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
In a revamp of the I/O library reviewed a few months ago, I revised the
structure of the test programs to match that given in the Boost.Test
documentation. Is what I have alright? Someone (Beman?) mentioned the
desire
Hi Misha,
Misha Bergal wrote:
Alas, this comment seems non-constructive for me. I don't think that
the question is what kind of design should be promoted. What are the
problems with the current design? Can you list some interesting things
that
would be possible if config_file were an
Hi Misha,
Misha Bergal wrote:
You've missed the word directly. You can't have all possible styles
work out of the box, because the number of possible styles is infitite.
The problem with approach taken by the library is that to support the new
style the user is advised to write a custom
Hi Misha,
Misha Bergal wrote:
Vladimir Prus [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I think it's better to wait for Unicode users to formulate what's needed.
It
seems, for example, that the last approach would work better for me on
Linux.
Visual C++
int
wmain( int
David Abrahams wrote:
parameterstd::string( output )
place_to( output_file_name )
default_value( /tmp/abc )
description( output file name )
While I don't find the interface proposed by Vladimir to be offensive,
when you get a pile of function arguments of the same
Hi Misha,
Misha Bergal wrote:
Vladimir Prus [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I think the point is that you hardly want both ascii and unicode in
single program. In that case two versions of shared library can be built:
for ascii and unicode, and you will link to
Gennadiy Rozental wrote:
I think the names arguments and options are as good as anything else.
It may be so. But I do not understand how the library use these terms.
Vladimir wrote:
option is (name,value) pair
argument is an command line element which is not option.
These definitions
And one important point: there are only three unnamed parameters. There's
a
bunch of other things that can be configured, and they all use *named*
interface:
desc.add_options()
(output, file, output file name).default_value(/tmp/abc)
;
The question arize: Why do you prefer
Consider command line
my_prog --output=/tmp/log input.cpp
Here is the option with name output and value /tmp/log. There's also
argument input.cpp.
1. Why you named namespace progrma_options it in fact you supply both.
2. How could I access argument using high level
Gennadiy Rozental wrote:
And one important point: there are only three unnamed parameters. There's
a
bunch of other things that can be configured, and they all use *named*
interface:
desc.add_options()
(output, file, output file name).default_value(/tmp/abc)
;
The
Gennadiy Rozental wrote:
Consider command line
my_prog --output=/tmp/log input.cpp
Here is the option with name output and value /tmp/log. There's also
argument input.cpp.
1. Why you named namespace progrma_options it in fact you supply both.
Because options are of a bit more
OK, I understand your opinion. I'm probably misusing you don't pay for
what
you don't use principle, but I find that 'options_and_argument' class is
important. Sometimes you really don't need typed storage.
Then just use default std::string type for parameter types - you got your
string to
Vladimir Prus [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Gennadiy Rozental wrote:
And one important point: there are only three unnamed parameters.
There's
a
bunch of other things that can be configured, and they all use *named*
interface:
desc.add_options()
Larry Evans wrote:
Chuck Messenger wrote:
The basic idea is to intercept all memory allocations -- p = new X;
--
saving the info with map[p] = sizeof(X);. To find the
interconnections between objects, you do this:
for (map_type::iterator it = map.begin(); it != map.end(); ++it)
Then it might be fixed when Apple does the next import of the main
branch of gcc3.3 . Let us wait with those changes until Apple releases
the next version of the developer tools which will probably be based on
gcc3.3
Maybe, I've been able to confirm the problem using gcc 3.1 via sourceforges
Chuck Messenger wrote:
boost/libs/smart_ptr/src/sp_collector.cpp:
There is no sample program to compile/run, so I have to guess somewhat
at how to use this one.
There is libs/smart_ptr/test/collector_test.cpp. You need to #define
BOOST_SP_ENABLE_DEBUG_HOOKS.
The basic idea of the algorithm
Schoenborn, Oliver wrote:
The above code does not make sense from a strict ownership point of view.
In other words, traditional smart pointers, such as NoPtr, are not
suitable when you need to support circular links.
Indeed because A owns the pimpl_, the line before returning doesn't make
Peter Dimov wrote:
Chuck Messenger wrote:
boost/libs/smart_ptr/src/sp_collector.cpp:
There is no sample program to compile/run, so I have to guess somewhat
at how to use this one.
There is libs/smart_ptr/test/collector_test.cpp. You need to #define
BOOST_SP_ENABLE_DEBUG_HOOKS.
OK - thanks.
58 matches
Mail list logo
