Boost :

Date view	Thread view	Subject view	Author view

Subject: Re: [boost] ASIO into the standard (was: Re: C++ committee meeting report)
From: Jonathan Wakely (jwakely.boost_at_[hidden])
Date: 2014-07-04 05:47:26

Next message: Benedek Thaler: "Re: [boost] GSoC: Boost.Pipeline -- scheduling of segments"
Previous message: Adam Romanek: "[boost] [unordered] valgrind reports "possibly lost" memory when not destroying the container"
In reply to: Felipe Magno de Almeida: "Re: [boost] ASIO into the standard (was: Re: C++ committee meeting report)"
Next in thread: Neil Groves: "Re: [boost] ASIO into the standard (was: Re: C++ committee meeting report)"
Reply: Neil Groves: "Re: [boost] ASIO into the standard (was: Re: C++ committee meeting report)"
Reply: Jeffrey Yasskin: "Re: [boost] ASIO into the standard (was: Re: C++ committee meeting report)"

On 1 July 2014 22:45, Felipe Magno de Almeida wrote:
>
> I would hope Allocators would be added to ASIO in the standard. It
> is difficult to limit memory usage without Allocators in embedded
> systems.

I hate this recurring theme of "let's take something that works well
today and then fsck it up by insisting it has allocator support"

Next message: Benedek Thaler: "Re: [boost] GSoC: Boost.Pipeline -- scheduling of segments"
Previous message: Adam Romanek: "[boost] [unordered] valgrind reports "possibly lost" memory when not destroying the container"
In reply to: Felipe Magno de Almeida: "Re: [boost] ASIO into the standard (was: Re: C++ committee meeting report)"
Next in thread: Neil Groves: "Re: [boost] ASIO into the standard (was: Re: C++ committee meeting report)"
Reply: Neil Groves: "Re: [boost] ASIO into the standard (was: Re: C++ committee meeting report)"
Reply: Jeffrey Yasskin: "Re: [boost] ASIO into the standard (was: Re: C++ committee meeting report)"

Date view	Thread view	Subject view	Author view

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk