Hi John,
I have looked into your code. It's pretty interesting, however as I see the current
situation in Boost development, your lib ranges over 3 differnt topics which are
handled
by 3 different libraries.
(i) Unification of the interface for various sequence types, including char* variants
Hi,
On Sat, Nov 23, 2002 at 04:22:22PM +, Hugo Duncan wrote:
Sockets have come up from time to time on this list, without
concrete results. I am no expert, but based on previous
discussions, I have tried to start describing a design at:
Not sure if this point is within the scope of current socket design:
Should the functionality be a very thin wrapper over the OS calls only?
E.g, in win32, blocking sockets especially within a GUI application behaves
erratically. A common way is to use to use non-blocking sockets and use
timed
Could you please expand upon this? If serialization of fundamental type
is invoked
through a base class member virtual functions are suggesting that this
base class be built differently on a regular basis? Wouldn't this
preclude
leaving serialization code in a precompiled library? Even if
How do i access the cvs sandbox?
My win cvs window says
CVSROOT: [EMAIL PROTECTED]:/cvsroot/boost-sandbox
(password authentication)
TCL is *not* available, shell is disabled
cvs update -P (in directory C:\Packages\boost_sandbox\)
cvs server: Updating .
And i don't get anything.
Thanks
/Michel
From: Pavol Droba [EMAIL PROTECTED]
I have developed a simple cast function which I found very useful. Here it
is:
template typename T
inline T offset_cast( void* p, unsigned int offset=0 )
{
return reinterpret_cast T ( static_castunsigned char*( p )+offset );
}
template typename T
Pavol Droba [EMAIL PROTECTED] writes:
Hi,
I have developed a simple cast function which I found very useful. Here it is:
template typename T
inline T offset_cast( void* p, unsigned int offset=0 )
{
return reinterpret_cast T ( static_castunsigned char*( p
Peter Dimov [EMAIL PROTECTED] writes:
Can we add -Wno-non-virtual-dtor to g++ tests? The ability of shared_ptr to
support nonvirtual destructors is an essential feature, and the tests do
exercize it.
Can't you just add
gcc*cxxflags-Wno-non-virtual-dtor
To the requirements for that test?
On Sun, Nov 24, 2002 at 01:26:05PM +0100, Terje Sletteb? wrote:
From: Pavol Droba [EMAIL PROTECTED]
I have developed a simple cast function which I found very useful. Here it
is:
template typename T
inline T offset_cast( void* p, unsigned int offset=0 )
{
return reinterpret_cast
In my experience in attempting to develop an over-general sockets
abstraction, it is next to impossible to contrive a perfect generalization
of the many different socket types.
A good sockets implementation will at a minimum:
* Use polymorphism on a well-defined socket interface.
This will allow
From: Pavol Droba [EMAIL PROTECTED]
On Sun, Nov 24, 2002 at 01:26:05PM +0100, Terje Sletteb? wrote:
From: Pavol Droba [EMAIL PROTECTED]
I have developed a simple cast function which I found very useful.
Here it
is:
template typename T
inline T offset_cast( void* p, unsigned
On Sun, Nov 24, 2002 at 04:59:45PM +0100, Terje Sletteb? wrote:
From: Pavol Droba [EMAIL PROTECTED]
On Sun, Nov 24, 2002 at 01:26:05PM +0100, Terje Sletteb? wrote:
From: Pavol Droba [EMAIL PROTECTED]
I have developed a simple cast function which I found very useful.
Here it
is:
Fellow Boosters:
Serialization Discussion Summary
Well, I havnt actually counted up the votes but
the concensus seems pretty clear that it shouldn't
be accepted into boost as is.
Of course I'm disappointed.
Now the question becomes whether its possible to
make changes such that it would be
From: Pavol Droba [EMAIL PROTECTED]
The prerequisite I haven't mentioned is that if you wan to use a structure
to
map to such a buffer, it has to have 1 byte aligmnent. Most of the
compilers
allow this kind of specification with pragmas.
Reinterpret-cast could be avoided like this:
From: Pavol Droba [EMAIL PROTECTED]
Sorry for sending this as several mails.
template typename T
inline T offset_cast( void* p, unsigned int offset=0 )
{
return reinterpret_cast T ( static_castunsigned char*( p )+offset );
}
There is also the issue of the interface. This cast, unlike the
http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?BoostSocket/SocketSetConcept
Can we use std::set like method names...
remove - erase
add - insert
is_set - count (I'm not fussed about this one)
Also for library implementors I think we need
update_width()
To be called after the OS
On Friday, November 22, 2002, at 03:33 PM, Wesley W. Terpstra wrote:
* Some approaches, including XML, allow a practically unlimited
number of
different ways to represent the same data. The user rather than the
serialization library should choose the particular design.
XSLT will allow this. As
I have started using the boost filesystem library in our application
codes and encountered a problem that could be solved by adding either
of the three functions
bool is_relative() const;
bool is_absolute() const;
void make_absolute();
to the path class.
Let me motivate this by an example: if
After spending more time with the serialization library, implementing
an archive
for the XDR format and considering how I could read my old archive
files using this
library instead of my own one, I can now give a more detailed review of
the
serialization library. I will keep those parts that
On Sunday, November 24, 2002, at 06:40 PM, Robert Ramey wrote:
5.5 Superfast I/O
There have been requests to add more primitive virtual functions to
basic_[i|o]archive in order to permit increased efficiency.
Specifically,
the idea is to add for each primitive type a virtual function to
http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?BoostSocket/SocketErrorConcept
send and recv cannot return 0 for Success as they must return a count of
bytes read or written.
Can we have three types of non-exception return value
success 0
want_read = -???
want_write = -???
I
Emily wrote:
I did quite a bit of re-arranging and editing of the existing material,
and for this the Wiki was very useful. I'd guess that for documentation
in the early stages, with frequent major updates and rewrites, a Wiki
would be ideal. I'm not convinced it would be useful for
Hamish,
On 24 Nov 2002 19:01:01 +, Hamish Mackenzie [EMAIL PROTECTED] wrote:
http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?BoostSocket/SocketSetConcept
Can we use std::set like method names...
remove - erase
add - insert
Sure.
is_set - count (I'm not fussed about
On Sun, Nov 24, 2002 at 07:27:42PM +0100, Terje Sletteb? wrote:
From: Pavol Droba [EMAIL PROTECTED]
Reinterpret-cast could be avoided like this:
template typename T
inline T* offset_cast( void* p, unsigned int offset=0 )
{
return static_castT*(
static_cast void* (
[2002-11-24] David Abrahams wrote:
Peter Dimov [EMAIL PROTECTED] writes:
Can we add -Wno-non-virtual-dtor to g++ tests? The ability of shared_ptr
to
support nonvirtual destructors is an essential feature, and the tests do
exercize it.
Can't you just add
gcc*cxxflags-Wno-non-virtual-dtor
On Sun, 2002-11-24 at 21:22, Hugo Duncan wrote:
is_set - count (I'm not fussed about this one)
Not sure about count, how about something like active
Yes, or contains?
Also for library implementors I think we need
update_width()
To be called after the OS has updated the fd_set
I saw
Hi
Are there any plan to integrate the spirit http://spirit.sourceforge.net/
into the boost distribution?
This is really nice library and now each new distribution of boost may break
it.
(It is not yet integrated in 1.20)
//Reagrds
Daniel Yerushalmy
I think ACE is an almost perfect model for what we want. The main
I agree there are many good things about ACE.
things I would like to see done differently in boost are
1) Use namespaces.
2) Support exception handling.
3) Use std containers.
3) Use other boost libraries.
Yes and:
5)
At 02:15 PM 11/24/2002, Matthias Troyer wrote:
I have started using the boost filesystem library in our application
codes and encountered a problem that could be solved by adding either
of the three functions
bool is_relative() const;
bool is_absolute() const;
void make_absolute();
to the path
At 12:36 PM 11/19/2002, Rene Rivera wrote:
I think you did a limited search... only in the headers. There are many
more files without (C). For example most Jamfiles don't have one.
Could you post how you did the search... perhaps this is something for
Beman
to add to the list of checks for
I will try to set up another page at Boost Wiki to explain in
detail what I mean by multiplexing library.
This is interesting, but the only intersection with sockets seems
to be at the socket_stream level (which appears to be an undefined
concept in the current wiki pages, but is in the
On Sun, 2002-11-24 at 21:23, Jeff Garland wrote:
Is there a reason why we can't define a simple socket library first
as a lower layer without the complications of multiplexing and
threading and then add those on top?
That seems reasonable, since due to the great differences between the
Hi,
Just as a note to those scanning files for copyright messages, I was once
informed by lawyers at one of my former employers that the string (C)
(that is, a capital C in parenthesis) has no legal standing - only the
word copyright or the copyright symbol (not available in ASCII) legally
On Sun, 2002-11-24 at 23:22, Robert Ramey wrote:
Hmmm - what I don't understand is how this would be different that calling
void basic_oarchive::write_array(void* p, size_t count)
Incidently, this would work for any kind of archive - not just the
binary ones.
But then the serialized data
Date: Sun, 24 Nov 2002 16:28:50 +0100
From: Matthias Troyer [EMAIL PROTECTED]
3. Does not work on all platforms - solvable problem
4. Interface design: there are some show-stoppers here for now
a) primitive types: code is not portable at the moment
b) performance: need improved methods
[2002-11-24] Thomas Wenisch wrote:
Hi,
Just as a note to those scanning files for copyright messages, I was once
informed by lawyers at one of my former employers that the string (C)
(that is, a capital C in parenthesis) has no legal standing - only the
word copyright or the copyright symbol
Robert,
posts where the quoted text you are replying to is only /sometimes/
preceded with '' are very hard to follow, and make the job of review
manager very difficult, since it becomes impossible to analyze the
discussion. Would you mind re-posting this with consistent quoting?
Robert Ramey
Dave Harris wrote:
You will not need any hooks; to fully bracket the data, you can use a
type-conversion trick made concrete below.
It's a neat trick, but I'd rather not rely on tricks. I might want:
For now, I'm of the same mind. Let's use tricks when a real need is seen.
Explicit end
My tests are already arranged in a way that 'test/minimal.hpp' offers too
little functionality while a whole test framework, such as
test_execution_monitor or unit_test_framework requires me link or
include too many translation units.
Well currently Boost.Test propose three configuration:
1.
On Wednesday, November 20, 2002, at 11:39 AM, David Abrahams wrote:
Matt Hurd [EMAIL PROTECTED] writes:
1.27 is the latest on sourcefourge. Would pay to either remove it or
put
1.29 up.
How much? ;-)
I removed 1.27
Shouldn't we put 1.29 up too? The advantage of the SourceForge file
I haven't the read list is a week, so I apologize if responses to
earlier posts have been resolved already.
Someone (I think the serialization author) talked about how he didn't
like the Standard exception philosophy and tried custom classes and
enum values for exceptions instead. I was
[Apologies to the computer scientist who came up with that phrase
(w.r.t. GOTOs)]
I haven't looked at the serialization library that was just up for
review, but some of the comments I saw on this list suggested that the
archive classes use virtual operators for reading or writing the basic
I haven't looked at the serialization library that was just under
review, so my questions are based on looking at reviews on this list.
The pre-standard stream classes did everything within themselves. The
current classes don't do too much at all. The object-to-text
conversion is handled by
Could we arrange a review of the I/O stuff I currently have in the
sandbox? The files are:
boost/io/array_stream.hpp
boost/io/iomanip.hpp
boost/io/streambuf_wrapping.hpp
boost/io_fwd.hpp [updated]
libs/io/doc/array_stream.html
libs/io/doc/index.html [updated]
libs/io/doc/iomanip.html
David A. Greene wrote:
is_sequenceT::value, please expect it to appear in the
CVS in a day or two :).
Oh, fabulous! Just what I ws looking for.
It's there!
Doesn't work with Borland and GCC 2.95 (3.2 is OK), though, currently, as it
relies on 'has_begin' and 'has_tag' traits, and there
45 matches
Mail list logo
