- Boost - lists.boost.org

Fwd: Changes to __PRETTY_FUNCTION__ in clang
by Mikhail Ramalho 05 Feb '18

05 Feb '18

Hi all, I recently send an email to the clang mailing list, to change how clang prints __PRETTY_FUNCTION__ [0], and one person raised a question if it would break boost. Honestly, I don't know boost's code and I could only find a few places where it's used, mainly for diagnostics, but also in CTTI and hanna; that's why I'm sending this email to ask for some help. Does boost relies on the format of these macros? The main idea is to just change how templates are printed, from: X<void>::X() [T = void] to a gcc-like style: X<T>::X() [with T = void] Thank you, [0] http://lists.llvm.org/pipermail/cfe-dev/2018-February/056766.html -- Mikhail Ramalho.

2 1

[gsoc18][boost.intrusive]
by Rishabh Arora 05 Feb '18

05 Feb '18

Hello Boost Community, I have proposed a project as a mentor for Google Summer of Code '18, as a new addition to the Boost.Intrusive library. The details about the project proposal and the competency test can be found here: https://github.com/ boostorg/boost/wiki/Boost-Google-Summer-of-Code-2018 (Project-5). All the interested candidates can contact me and send me their competency test on the following e-mail: rishabharora1997(a)gmail.com Best Regards, Rishabh

2 1

Re: [boost] [CppCMS] What can be contributed to Boost?
by Bjorn Reese 04 Feb '18

04 Feb '18

On 02/02/18 19:30, Artyom Beilis via Boost wrote: > Once I can think of is cppcms::json > > http://cppcms.com/wikipp/en/page/cppcms_1x_json > http://cppcms.com/cppcms_ref/latest/classcppcms_1_1json_1_1value.html > > Also it should be updated to C++11 and probably do some small features > updates. it is one of the fastest JSON parsers around (and yes it is > way faster and convenient than one in property tree) > > What do you think? If the Boost community wants a JSON library, then I would like to suggest another, more versatile ibrary: https://github.com/breese/trial.protocol Documentation can be found here: http://breese.github.io/trial/protocol/ This library consists of two (well, three) parts: 1. A dynamic variable which is a variant type that can contain fundamental types, arrays, and associative arrays. This can be used as a parse tree for JSON and similar binary formats like MsgPack, UBJSON, BinToken, and CBOR. But it can also be used as a data container for, say, configuration data. The dynamic variable has iterators so it works with std algorithms. It also comes with a visitor. 2. A JSON parser/generator framework. This contains an incremental pull parser (json::reader) as the basic building-block. The incremental parser is used by a Boost.Serialization archive to enable serialization directly between JSON and C++ data structures. The incremental parser is also used by a tree parser that converts JSON into the before-mentioned dynamic variable. 3. A BinToken parser/generator framework. Like the JSON framework, but for the binary BinToken format. Currently undocumented.

1 0

[CppCMS] What can be contributed to Boost?
by Artyom Beilis 02 Feb '18

02 Feb '18

Hello Dear Boost Developers, Recently I had released CppCMS - C++ Web Framework 1.2 under MIT license instead of LGPLv3 See: http://cppcms.com Since CppCMS project had already contributed some of its parts for Boost: Boost.Locale - in Boost for long time Boost.Nowide (passed review still need some my time to integrate to release) I wanted to renew the discussions of what parts may interest the community Boost outside CppCMS. Some samples I thought of: -------------------------------------------- Once I can think of is cppcms::json http://cppcms.com/wikipp/en/page/cppcms_1x_json http://cppcms.com/cppcms_ref/latest/classcppcms_1_1json_1_1value.html Also it should be updated to C++11 and probably do some small features updates. it is one of the fastest JSON parsers around (and yes it is way faster and convenient than one in property tree) What do you think? -------------------------------------- Another one that was already discussed once is CppDB: http://cppcms.com/sql/cppdb/ It also needs C++11 updates in general and is already under dual Boost/MIT License. It was discussed before but nothing moved further. ---------------------------------- Some smart pointers I find very useful especially for Pimpl implementation: hold_ptr -> similar to scope ptr but object constness is same as the pointer copy_ptr-> copies underlying object upon copy (very useful for pimpl) clone_ptr->clones objects. Regards, Artyom Beilis

2 1

[serialization] uuid test_serialization ubsan error
by James E. King, III 01 Feb '18

01 Feb '18

I'm getting a ubsan test error in uuid/test/test_serialization - is the code in that test using archive the right way? testing.capture-output ../../../bin.v2/libs/uuid/test/test_serialization.test/gcc-7/debug/link-static/threadapi-pthread/test_serialization.run ====== BEGIN OUTPUT ====== ../../../boost/archive/detail/interface_oarchive.hpp:47:16: runtime error: downcast of address 0x7ffca0c6fe30 which does not point to an object of type 'text_oarchive' 0x7ffca0c6fe30: note: object is of type 'boost::archive::text_oarchive_impl<boost::archive::text_oarchive>' 00 00 00 00 e0 2f 78 8f 48 56 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^~~~~~~~~~~~~~~~~~~~~~~ vptr for 'boost::archive::text_oarchive_impl<boost::archive::text_oarchive>' EXIT STATUS: 1 ====== END OUTPUT ====== Thanks, Jim

3 3

Re: [boost] [review] Review of Outcome v2 (Fri-19-Jan to Sun-28-Jan, 2018)
by Andrzej Krzemienski 01 Feb '18

01 Feb '18

2018-02-01 19:13 GMT+01:00 Emil Dotchevski <emildotchevski(a)gmail.com>: > On Thu, Feb 1, 2018 at 2:51 AM, Andrzej Krzemienski <akrzemi1(a)gmail.com> > wrote: > >> Boost.Outcome solves the problem decently: you get a compiler error or a >> compiler warning >> > > Do you? What if you have: > > result<void> foo(); > > void bar() > { > foo(); > } > > What compile error will that generate? > "ignoring returned value of type 'outcome_v2_f1696316::result<void>', declared with attribute nodiscard [-Werror=unused-result]" online example: https://wandbox.org/permlink/5vICxckvVG6QO0n1 > Now, in Boost.Noexcept, if the programmer forgets to test for the failure >> (with `try_`), the subsequent function is still executed with the default >> value of type `T` returned from the funciton that failed. Because in >> Boost.Noexcept when function fails it returns a default-constructed `T`. >> > > The idea in Noexcept is that since the function _must_ return something if > there is an error, it returns throw_return<T>() but that is not automatic; > the user still has to say e.g. return throw_(error()). > I understand the constraints you are under. I also acknowledge that this is the best one can do. Nonetheless, I still see the limitation of the solution. If a third party function is returning a type representing a resource, and this type does not provide a default constructor, there is no way to "throw_". You cannot even customize `throw_return<T>()` because what value would you return? You are reporting failure because you cannot acquire the resource. And because it is a third-party interface, you cannot adapt the type. So, in the end, there will be functions where you cannot apply Boost.Noexcept. > > >> And when you check it systematically it is all ok, but then you forget >> (and this is a tedious task), you violate the contracts. No compile-time >> check, no run-time check. >> > > In Noexcept there _is_ run-time check: if noexcept_::has_current_error() > is true at the time a thread terminates, it invokes std::terminate(). Not > ideal, and won't take action if the thread never terminates -- and it may > never terminate because, like in Outcome, if the caller doesn't check at > every function call, the program keeps going. > I was imprecise. you do have a run-time check, but it comes too late: it does not prevent functions to be called with failed preconditions. > > >> I consider this a serious issue. >> > > It is, programmers forget to check for errors all the time. > And Boost.Outcome helps detect these situations at compile-time (of course, at the expense of controlling the return type). > >> And taking into consideration the advantages of Boost.Noexcept you >> mention, I can only conclude that Boost.Noexcept is superior to >> Boost.Outcome in one aspect but inferior in another. >> > > The two libraries solve different problems. > Indeed. > Outcome helps you avoiding exception handling, so it assumes you can > freely use result<T,E> throughout your interfaces. > Well, it can help you avoid exceptions. But it also helps you deal with the lack of exception handling. As you say, the trade-off is that you use `result` in return type. > Noexcept helps you deal with a lack of exception handling, so it assumes > that at least some of the interfaces are beyond your control, and doesn't > impose a return type. > Yes, here the trade-off is, no altering of the return type, but unsafe consequences when you forget to check for "thrown" exceptions. And there must exist a "spare" value in the returned type. There are benefits to using a special return type (to protect against using > an invalid value), but Noexcept leaves that to the user because return > values don't transport errors, just the T; you could e.g. use > std::optional<T>. > And user may not be able to make this decision because he may not be in control of the return type. Regards, &rzej;

1 0

[GSOC18] Boost.Geometry Project 1 : Similarity between geometries
by sagarvijaygupta 31 Jan '18

31 Jan '18

I am Sagar Gupta, a student of IIT Mandi, pursuing my Bachelors in Computer Science. I want to work on the Project 1 of Similarity between Geometries. I read the source code of geometry and regarding the Frechet distance and its different variations and tried to work with it. Also I tried the competency test. Its my first time for GSOC but I have some good experience in C++ (from different projects and competitive programming). I wish to know where should I send the competency test? I wish to work on this project as it is a great learning experience which I realized while working on the implementation of Frechet Distance between linestrings. Thanks and Regards Sagar Gupta -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Dev-f2600599.html

2 2

International Conference on Information Society (i-Society 2018): Call for Submissions!
by International Conference on Information Society 30 Jan '18

30 Jan '18

Apologies for cross-postings. Please send it to interested colleagues and students. Thanks! Call for Submissions! ********************************************************************************** International Conference on Information Society (i-Society 2018) 15-18 July, 2018 Venue: Ballsbridge Hotel Dublin, Ireland www.i-society.eu ********************************************************************************* The i-Society is a global knowledge-enriched collaborative effort that has its roots from both academia and industry. The conference covers a wide spectrum of topics that relate to information society, which includes technical and non-technical research areas. The mission of i-Society 2018 conference is to provide opportunities for collaboration of professionals and researchers to share existing and generate new knowledge in the field of information society. The conference encapsulates the concept of interdisciplinary science that studies the societal and technological dimensions of knowledge evolution in digital society. The i-Society bridges the gap between academia and industry with regards to research collaboration and awareness of current development in secure information management in the digital society. The topics in i-Society 2018 include but are not confined to the following areas: *New enabling technologies - Internet technologies - Internet of Things (IoT) - Wireless applications - Mobile Applications - Cloud and iCloud - Multimedia Applications - Protocols and Standards - Ubiquitous Computing - Virtual Reality - Human Computer Interaction - Geographic information systems - e-Manufacturing - Electronic Discovery (eDiscovery) - Software Applications - Disruptive Technology *Intelligent data management - Intelligent Agents - Intelligent Systems - Intelligent Organisations - Content Development - Data Mining - Data Management Software - e-Publishing and Digital Libraries - Information Search and Retrieval - Knowledge Management - e-Intelligence - Compliance and Recovery from Data Loss - Knowledge networks - Risk Mitigation - Cost Efficiency - Quality Assurance - Information Management - Support Litigation - Complex Investigations *Secure Technologies - Internet security - Web services and performance - Secure transactions - Cryptography - Payment systems - Secure Protocols - e-Privacy - e-Trust - e-Risk - Cyber Security Investigations and Defence - Cyber law - Forensics - Information assurance - Mobile social networks - Peer-to-peer social networks - Sensor networks and social sensing - Information Security Compliance *e-Learning - Collaborative Learning - Curriculum Content Design and Development - Delivery Systems and Environments - Educational Systems Design - e-Learning Organisational Issues - Evaluation and Assessment - Virtual Learning Environments and Issues - Web-based Learning Communities - e-Learning Tools - e-Education *e-Society - Global Trends - Social Inclusion - Intellectual Property Rights - Social Infonomics - Computer-Mediated Communication - Social and Organisational Aspects - Globalisation and developmental IT - Social Software - Smart City *e-Health - Data Security Issues - e-Health Policy and Practice - e-Healthcare Strategies and Provision - Medical Research Ethics - Patient Privacy and Confidentiality - e-Medicine *e-Governance - Democracy and the Citizen - e-Administration - Policy Issues - Virtual Communities *e-Business - Digital Economies - Knowledge economy - eProcurement - National and International Economies - e-Business Ontologies and Models - Digital Goods and Services - e-Commerce Application Fields - e-Commerce Economics - e-Commerce Services - Electronic Service Delivery - e-Marketing - Gig Economy - Online Auctions and Technologies - Virtual Organisations - Teleworking - Applied e-Business - Electronic Data Interchange (EDI) - Innovative Strategies - Business Intelligence - Information Intelligence - Forensic Accounting *e-Art - Legal Issues - Patents - Enabling technologies and tools *e-Science - Natural sciences in digital society - Biometrics - Bioinformatics - Collaborative research *Industrial developments - Trends in learning - Applied research - Cutting-edge technologies - Industrial Control Systems - Communications Compliance * Research in progress - Ongoing research from undergraduates, graduates/postgraduates and professionals SUBMISSION INSTRUCTIONS: * You can submit your abstract, extended abstract or paper online at http://www.i-society.eu/paper-submission/ or email it to papers(a)i-society.eu * You can submit your speaker's proposal via email at speakers(a)i-society.eu or online at http://www.i-society.eu/format/speakers-participation/ * You can submit your poster via email at posters(a)i-society.eu * You can submit your workshop or tutorial proposal via email at workshop(a)i-society.eu or tutorial(a)i-society.eu * You can submit your panel discussion via email at pandis(a)i-society.eu IMPORTANT DATES: *Abstract Submission Date: February 10, 2018 *Notification of Abstract Acceptance / Rejection: February 17, 2018 *Extended Abstract (Work in Progress) Submission Date: February 20, 2018 *Notification of Extended Abstract Acceptance / Rejection: February 27, 2018 *Research Paper Submission Date: March 01, 2018 *Notification of Research Paper Acceptance / Rejection: March 12, 2018 *Camera Ready Paper Due: May 01, 2018 *Proposal for Workshops / Tutorials: February 25, 2018 *Notification of Workshop/Tutorials Acceptance / Rejection: March 01, 2018 *Poster / Demo Proposal Submission: March 01, 2018 *Notification of Poster / Demo Acceptance: March 12, 2018 *Early Bird Registration Deadline (Authors and Participants): April 15, 2018 *Late Bird Registration Deadline (Authors only): May 15, 2018 *Late Bird Registration Deadline (Participants only): May 30, 2018 *Conference Dates: July 15-18, 2018 For more details, please visit www.i-society.euIf you wish to unsubscribe from our newsletter, click http://r.confinfosoc.org/scyaulavbnjg.html

1 0

Interested in applying to the google summer of code
by Laouen Belloli 30 Jan '18

30 Jan '18

Hi, My name is Laouen Belloli, I'm a Computer Science student at Universidad de Buenos Aires currently doing my final thesis in Discrete Events Simulation, this is my 7th and last year on it. In the past I contributed to the cadmium project. This year, I want to join the google summer of code to contribute to Boost. In particular, I would like to work on the Boost.Real project proposed. Best regards, -- Laouen Mayal Louan Belloli. LIAA - DC - FCEyN - UBA. C.A.B.A. - Buenos Aires - Argentina. https://liaa.dc.uba.ar +54 9 11 38675694

2 2

[atomic] (op)_and_test naming
by Andrey Semashev 30 Jan '18

30 Jan '18

Hi, I would like to ask for the community opinion on the naming of the (op)_and_test functions that appeared in Boost.Atomic 1.66. As you probably know, 1.66 included a few new atomic operations, some of which have the name (op)_and_test (e.g. add_and_test, sub_and_test, etc.) These operations perform the (op) on the atomic value and test if the result is zero, so that instead of this: if (a.fetch_sub(1) - 1 == 0) one could write this: if (a.sub_and_test(1)) Also, the generated code for these operations can potentially be more efficient. Recently I received this request: https://github.com/boostorg/atomic/issues/11 which basically asks to change the result of the functions to the opposite. I can see that the current naming could be confusing, especially given that other operations like bit_test_and_set return the previous bit value (i.e. true if the bit was 1). That would be a breaking change, but the new operations were announced as experimental in the release notes, so if there is consensus that the result should indeed be changed, I'm ready to comply. Another solution is change (op)_and_test naming to something else that is more clear. In that case I could deprecate the (op)_and_test variants and provide the functionality under the new names. I would welcome suggestions for a better naming scheme, if you feel this is the right way. My only ask is that the new names be concise, if possible. Lastly, if you think the current naming is fine or there is another way to resolve the confusion, please comment as well. I would appreciate your opinion in any case. Thanks.

5 29