Re: [boost] Patch to make code_converter flushable
On Thu, 03 Feb 2011 17:35:56 -0700, Eddie Carle wrote:
I've attached a little patch that makes iostreams::code_converter flushable. It seems like it really should be. Is there any chance someone could look at this? I've included some test code as well that outputs the following.
Is anyone actually interested in this? I've been working on moving the fastcgi++ library over to boost iostreams but unless this patch is applied I cannot actually do so. One cannot derive from iostreams::code_converter to make it flushable because the necessary components are private and not protected. Is there any chance whatsoever of getting this patch applied or am I just wasting my time? -- Eddie Carle
In message <1297291490.10578.7.camel@localhost>, Eddie Carle <eddie@erctech.org> writes
On Thu, 03 Feb 2011 17:35:56 -0700, Eddie Carle wrote:
I've attached a little patch that makes iostreams::code_converter flushable. It seems like it really should be. Is there any chance someone could look at this? I've included some test code as well that outputs the following.
Is anyone actually interested in this? I've been working on moving the fastcgi++ library over to boost iostreams but unless this patch is applied I cannot actually do so. One cannot derive from iostreams::code_converter to make it flushable because the necessary components are private and not protected.
Is there any chance whatsoever of getting this patch applied or am I just wasting my time?
I guess that putting the library name, [bracketed] in the subject line, as per: http://www.boost.org/community/policy.html might assist in getting the attention of those interested in this. HTH, Alec -- Alec Ross
On 1:59 PM, Eddie Carle wrote:
On Thu, 03 Feb 2011 17:35:56 -0700, Eddie Carle wrote:
I've attached a little patch that makes iostreams::code_converter flushable. It seems like it really should be. Is there any chance someone could look at this? I've included some test code as well that outputs the following. Is anyone actually interested in this? I've been working on moving the fastcgi++ library over to boost iostreams but unless this patch is applied I cannot actually do so. One cannot derive from iostreams::code_converter to make it flushable because the necessary components are private and not protected.
Is there any chance whatsoever of getting this patch applied or am I just wasting my time?
It sounds interesting to me. Start with a Trac ticket <https://svn.boost.org/trac/boost/query>. (I searched for code_converter in iostreams tickets but didn't see this.) Set all the fields carefully, including Milestone and Version, and add yourself to the Cc. And (if you haven't already) adapt your test code so it fits with other tests in libs/iostreams/test. But don't stop there. Get in touch with the author (see libs/maintainers.txt in your boost distribution), and propose it to him. If his e-mail is out of date, maybe someone on this list could help find him. It's all up to the maintainer. Pitch it to him as requiring very little of his time. It appears he hasn't been around for a while, based on posts to this list. <http://www.ask.com/web?qsrc=2990&o=0&l=dir&q=Turkanis+site%3Alists.boost.org>. Hope that helps. -Jim
On Wed, 2011-02-09 at 18:21 -0600, Jim Bell wrote:
Start with a Trac ticket <https://svn.boost.org/trac/boost/query>. (I searched for code_converter in iostreams tickets but didn't see this.) Set all the fields carefully, including Milestone and Version, and add yourself to the Cc.
I guess I should have thought of that. It is done now. <http://svn.boost.org/trac/boost/ticket/5174>
But don't stop there. Get in touch with the author (see libs/maintainers.txt in your boost distribution), and propose it to him. If his e-mail is out of date, maybe someone on this list could help find him. It's all up to the maintainer. Pitch it to him as requiring very little of his time. It appears he hasn't been around for a while, based on posts to this list.
I have noticed his inactivity as well. I sent out the email and am hoping that he gets back to me. What happens if he is incognito? Would there still be any mechanism to pursue this if that is the case?
Hope that helps.
It helps a lot. Thanks for the reply. -- Eddie Carle
On 1:59 PM, Eddie Carle wrote:
Start with a Trac ticket ... But don't stop there. Get in touch with the author (see libs/maintainers.txt in your boost distribution), and propose it to him. If his e-mail is out of date, maybe someone on this list could help find him. It's all up to the maintainer. Pitch it to him as requiring very little of his time. It appears he hasn't been around for a while, based on posts to this list. I have noticed his inactivity as well. I sent out the email and am hoping that he gets back to me. What happens if he is incognito? Would
On Wed, 2011-02-09 at 18:21 -0600, Jim Bell wrote: there still be any mechanism to pursue this if that is the case?
We say "MIA", and there's lots of, um, lively discussion here about what ought to be done then. <http://www.google.com/search?q=MIA+site%3Alists.boost.org> Any maintainer can commit a change, but all are busy with their own libs & lives, and none want to commit a patch to something they're not intimately familiar with. (Understandably.) If your maintainer is MIA, your options seem to be ... * Petition to maintain it yourself (if you're sufficiently motivated). Not sure what's involved with that except that the current maintainers need to establish confidence in your abilities. * Put it on the Google SoC (Summer of Code) list for an intern to work on. Not sure the details here. * Petition the "roving hit squad" to hit it next. <http://lists.boost.org/Archives/boost/2010/12/174459.php>. They're currently working on boost.pool <http://groups.google.com/group/boostpool?hl=en>, and experimenting with the whole "roving hit squad" approach. Not sure how that's going. Hope that helps.
participants (3)
-
Alec Ross -
Eddie Carle -
Jim Bell