July 2025 - Boost-users - lists.boost.org

Polygon - Voronoi - clip to rectangular bounding box
by neil.j.chisholm＠gmail.com 20 Jul '25

20 Jul '25

Hello I am a hobby programmer and I hope to make use of the polygon library to procedurally generate voronoi diagrams for the purpose of defining world maps in a videogame. My use case includes a requirement that the voronoi diagram be clipped to a rectangular bounding box. The corollary to this requirement is that every voronoi cell is therefore (as a result of being clipped to the bounding box where necessary) a complete convex polygon. By this I mean that an edge must not extend outside the bounding box. If the edge would extend beyond the bounding box, it must be be clipped to the bounding box creating a new vertex at the intersection of the edge and the bounding box. I believe there would also need to be a vertex created at each corner of the bounding box. In order for a voronoi cell to be a complete convex polygon, new edge(s) must be created which run between the newly created vertices. My understanding is that the polygon library does not include a method to clip edges to a bounding box. Do you have any recommendations about how to approach defining a method which does so? - It should be possible to define the rectangular bounding box dimensions similarly to how points and segments are defined - For the sake of efficiency I assume it would be appropriate only to consider edges which extend beyond the given bounding box - While a general solution should probably be able to clip parabolic edges, my use case will likely only involve sites comprised of points (no segments) so a solution clipping straight line edges only would be sufficient for my own purposes If you have any thoughts I would be very grateful to receive them. Many thanks in advance.

1 0

[release] Boost 1.89.0 beta 1 released
by Marshall Clow 17 Jul '25

17 Jul '25

Boost release 1.88.0 beta 1 is now available at: https://archives.boost.io/beta/1.89.0.beta1/source/ The SHA256 checksums are: 9ece9af2b243f90b76f679b278b512b6589c7843e4dd54cffcb719bbc0801998 boost_1_89_0_b1.tar.bz2 bf45af4a58f39c2ec374ef6e70b26859b786ba2ed087bc869d92a2b4de14e0d2 boost_1_89_0_b1.zip f255b4a31558b3fb81be1dc7e8b367fb9997dbe5e71da98a730c681377abffa9 boost_1_89_0_b1.7z 984ee193ddf192795ba635d4c73b2b43e1e596995d7ce5519a3a72fab9bc0b40 boost_1_89_0_b1_rc1.tar.gz Release notes (still need updates): https://original.boost.org/users/history/version_1_89_0.html Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. -- Boost Release Team

1 0

lowest_layer() is deprecated in boost::beast, replaced by boost::beast::get_lowest_layer(), but still in use by boost::asio:ssl::stream
by Klebsch, Mario 14 Jul '25

14 Jul '25

Hi, The boost libraries beast and asio seem to disagree on whether a socket/stream should offer the lowest_layer() method or not. Boost::beast::tcp_stream has only private versions of this method and the associated typedef lowest_layer_type, while e.g. boost::asio::ssl::stream still requires this method. The replacement get_lowest_layer() is only offered in beast. For boost::asio::ssl::stream this is handled by boost::beast::tcp_stream declaring boost::asio::ssl::stream as friend, so offering access to lowest_layer(). But I have my own ssl stream, based on a different SSL library than openssl, and this stream class is also (because it is based on boost::asio::ssl::stream) dependant on lowest_layer(). I think, boost::beast and boost::asio should agree on whether to deprecate lowest_layer() and offer get_lowest_layer(), or not. Klebsch Mario Funktion | R&D Tel: +49 (0) 531 38 701 718 Raum: Braunschweig, E20 Diese E-Mail und die an sie angehängten Dateien sind ausschließlich für Personen oder Institutionen bestimmt, deren Namen oben aufgeführt sind. Sie können Informationen enthalten, die durch das Berufsgeheimnis geschützt sind und deren Weitergabe strengstens untersagt ist. Jede elektronische Nachricht kann geändert werden. ACTIA lehnt jede Verantwortung für diese Nachricht ab. Der Inhalt dieser Nachricht stellt keine Verpflichtung seitens unseres Unternehmens dar. Wenn Sie kein Empfänger sind, weisen wir Sie darauf hin, dass das Lesen, Vervielfältigen oder Verteilen strengstens untersagt ist. Wir bitten Sie daher, uns umgehend über diesen Brief zu informieren und diese Nachricht sowie eventuell beigefügte Unterlagen aus Ihrem Postfach zu löschen. Danke. This e-mail and the files attached to it are intended exclusively for persons or institutions whose names are listed above. They may contain information that is protected by professional secrecy and the disclosure of which is strictly prohibited. Any electronic message can be modified. ACTIA declines all responsibility for this message. The content of this message does not represent a commitment on the part of our company. If you are not a recipient, we would like to point out that reading, copying or distribution is strictly prohibited. We therefore ask you to inform us immediately about this letter and to delete this message and any accompanying documents from your mailbox. Thank you.

1 0

Free threaded python support with PEP 779
by george.sykes＠connectorsubsea.com 09 Jul '25

09 Jul '25

Hi, With Python 3.14 introducing free threaded python I was wondering if anyone's had a chance to try this out with Boost Python? Seems like it should be able to help us increase performance on certain types of tasks but not sure if Boost Python supports using the functionality. If not, i'll go give it a crack and see what it's like. Best wishes George

1 0