[move_ptr] implementation and docs available
Hi All, A long time ago, I announced that I was working on an implementation of a move pointer: On Wednesday, January 21, 2004 6:30 PM, "Jonathan Turkanis" <technews@kangaroologic.com> wrote:
... My goal is to have the implementation done tonight. That means it will be done next week. :-)
Well, I actually did write the implementation, but never documented it, and finally forgot about it. Recently, Thorsten Ottosen requested a move_ptr implementation, so I cleaned up my implementation from Janurary and wrote some tests and documentation. Here it is: http://home.comcast.net/~jturkanis/move_ptr/ It's based on Daniel Wallin's adaptation of an idea of Rani Sharoni, mixed in with some ideas of Howard Hinnant and Bronek Kozicki. Best Regards, Jonathan
"Jonathan Turkanis" <technews@kangaroologic.com> writes:
Hi All,
A long time ago, I announced that I was working on an implementation of a move pointer:
On Wednesday, January 21, 2004 6:30 PM, "Jonathan Turkanis" <technews@kangaroologic.com> wrote:
... My goal is to have the implementation done tonight. That means it will be done next week. :-)
Well, I actually did write the implementation, but never documented it, and finally forgot about it. Recently, Thorsten Ottosen requested a move_ptr implementation, so I cleaned up my implementation from Janurary and wrote some tests and documentation.
Here it is: http://home.comcast.net/~jturkanis/move_ptr/
It's based on Daniel Wallin's adaptation of an idea of Rani Sharoni, mixed in with some ideas of Howard Hinnant and Bronek Kozicki.
Nice docs! QuickDoc? A nit: in References, when citing a mail message, it would be better to link to that message. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
"David Abrahams" <dave@boost-consulting.com> wrote in message news:uu0u3hcnp.fsf@boost-consulting.com...
"Jonathan Turkanis" <technews@kangaroologic.com> writes:
Hi All,
A long time ago, I announced that I was working on an implementation of a move pointer:
On Wednesday, January 21, 2004 6:30 PM, "Jonathan Turkanis" <technews@kangaroologic.com> wrote:
... My goal is to have the implementation done tonight. That means it will be done next week. :-)
Well, I actually did write the implementation, but never documented it, and finally forgot about it. Recently, Thorsten Ottosen requested a move_ptr implementation, so I cleaned up my implementation from Janurary and wrote some tests and documentation.
Here it is: http://home.comcast.net/~jturkanis/move_ptr/
It's based on Daniel Wallin's adaptation of an idea of Rani Sharoni, mixed in with some ideas of Howard Hinnant and Bronek Kozicki.
Nice docs!
Thanks.
QuickDoc?
No. I guess I'm like one of those novelists who insists on using a forty-year-old typewriter -- I still write HTML docs by hand.
A nit: in References, when citing a mail message, it would be better to link to that message.
I didn't want to link to that message because Daniel Wallin and I were in the middle of an argument -- the remark about posting the code in a week was just an aside. ;-). Jonathan
"Jonathan Turkanis" <technews@kangaroologic.com> writes:
"David Abrahams" <dave@boost-consulting.com> wrote in message
A nit: in References, when citing a mail message, it would be better to link to that message.
I didn't want to link to that message because Daniel Wallin and I were in the middle of an argument -- the remark about posting the code in a week was just an aside. ;-).
There were a few messages and NG postings in the Bibliography. I still think it's a good idea to link to specific messages. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
David Abrahams <dave@boost-consulting.com> writes:
A nit: in References, when citing a mail message, it would be better to link to that message.
Oh, nevermind: I see that you did, on second glance. I don't know why/how I missed that. I didn't expect the bracketed things to link to the target because in my Bibs they link back to the place in the text that reference the source. For those that print docs, it's probably more appropriate to spell out the URL in the Bib entry. That's the only thing I can think of that would make them more obvious. Anyway, enough nitpicking. Nice docs! -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
"David Abrahams" <dave@boost-consulting.com> wrote in message news:uisajfo67.fsf@boost-consulting.com...
David Abrahams <dave@boost-consulting.com> writes:
A nit: in References, when citing a mail message, it would be better to link to that message.
Oh, nevermind: I see that you did, on second glance. I don't know why/how I missed that. I didn't expect the bracketed things to link to the target because in my Bibs they link back to the place in the text that reference the source. For those that print docs, it's probably more appropriate to spell out the URL in the Bib entry.
I prefer that, too. It was this url that changed my mind: http://aspn.activestate.com/ASPN/Mail/Message/Attachments/boost/400DC271.106...
That's the only thing I can think of that would make them more obvious.
Anyway, enough nitpicking. Nice docs!
Thanks again! Jonathan
"Jonathan Turkanis" <technews@kangaroologic.com> writes:
"David Abrahams" <dave@boost-consulting.com> wrote in message news:uisajfo67.fsf@boost-consulting.com...
David Abrahams <dave@boost-consulting.com> writes:
A nit: in References, when citing a mail message, it would be better to link to that message.
Oh, nevermind: I see that you did, on second glance. I don't know why/how I missed that. I didn't expect the bracketed things to link to the target because in my Bibs they link back to the place in the text that reference the source. For those that print docs, it's probably more appropriate to spell out the URL in the Bib entry.
I prefer that, too. It was this url that changed my mind:
http://aspn.activestate.com/ASPN/Mail/Message/Attachments/boost/400DC271.106...
You can always use a tinyurl ;-) -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
participants (2)
-
David Abrahams -
Jonathan Turkanis