Re: [Boost-users] Could sprintf be replaced with snprintf?
Has there been any movement on having someone else maintain ODEINT? I don't know that I would be of much use, but I'm willing to help where I can. There is one other issue that isn't critical, but it would save our group from having to do some hand editing of ODEINT for use with our project. Some of the paths are long enough that after they're included in our project they have nonportable lengths, requiring use to rename them. I made an issue last year: https://github.com/boostorg/odeint/issues/54. Changing the names would surely break code, and I don't know if this is a feasible change. Given that it's pretty easy for people to update include directives though, maybe it's not too intrusive. If it's a welcome change, I can submit a PR on GitHub. Best wishes, Justin ________________________________________ From: McGrath, Justin M <jmcgrath@illinois.edu> Sent: Monday, December 4, 2023 11:53 AM To: Matt Borland; Karsten Ahnert Cc: mario.mulansky@gmx.net; Nick Thompson Subject: Re: [Boost-users] Could sprintf be replaced with snprintf? Thank you everyone. It would be great if someone could continue managing the package. It's a great resource. Best wishes, Justin ________________________________________ From: Matt Borland <matt@mattborland.com> Sent: Friday, December 1, 2023 2:04 AM To: Karsten Ahnert Cc: McGrath, Justin M; mario.mulansky@gmx.net; Nick Thompson Subject: Re: [Boost-users] Could sprintf be replaced with snprintf?
On Nov 30, 2023, at 9:27 PM, Karsten Ahnert <karsten.ahnert@gmx.de> wrote:
Merged the pull request. We are not actively maintaining the library anymore.
But I will keep an eye on any upcoming changes.
Karsten, Thanks. Would you be interested in new maintainers stepping in for the library? Nick Thompson (cced) and I are maintainers on several other Boost libraries (math, multiprecision, random, and test), and we would be interested in helping out. He’s a mathematician, and I am a full-time Boost developer. If you would like to schedule a call or anything to discuss we can do that. Matt
On Dec 11, 2023, at 8:59 PM, McGrath, Justin M <jmcgrath@illinois.edu> wrote:
Has there been any movement on having someone else maintain ODEINT? I don't know that I would be of much use, but I'm willing to help where I can.
I have not heard anything back, but Nick and I remain interested in being added as maintainers.
There is one other issue that isn't critical, but it would save our group from having to do some hand editing of ODEINT for use with our project. Some of the paths are long enough that after they're included in our project they have nonportable lengths, requiring use to rename them. I made an issue last year: https://github.com/boostorg/odeint/issues/54.
Changing the names would surely break code, and I don't know if this is a feasible change. Given that it's pretty easy for people to update include directives though, maybe it's not too intrusive. If it's a welcome change, I can submit a PR on GitHub.
You could move all the code to new headers that have a path that supports R. In the current headers remove everything, and just #include the new ones and add BOOST_HEADER_DEPRECATED(“<boost/new/header/path>") so nothing breaks. Matt
On Tue, Dec 12, 2023 at 1:56 AM Matt Borland via Boost-users < boost-users@lists.boost.org> wrote:
On Dec 11, 2023, at 8:59 PM, McGrath, Justin M <jmcgrath@illinois.edu> wrote:
Has there been any movement on having someone else maintain ODEINT? I don't know that I would be of much use, but I'm willing to help where I can.
I have not heard anything back, but Nick and I remain interested in being added as maintainers.
Please post the request to be added as a maintainer to the development list and describe the context and someone can take care of it. Jeff
participants (4)
-
Jeff Garland -
Matt Borland -
McGrath, Justin M