January 2018 - Boost - lists.preview.boost.org

[foreach][polygon][xpressive][bimap][ptr_container][gil][assign][typeof][msm] PRs for removing executable attribute for files
by Edward Diener 08 Mar '18

08 Mar '18

The following libraries still have PRs, which I have previously submitted, for removing the executable attribute for one or more files: foreach polygon xpressive bimap ptr_container gil assign typeof msm None of these PRs affect anything other than the file attribute, so no testing is needed AFAICS since no code changes. If the maintainers of the above libraries, or someone else with write access to these libraries, can merge the appropriate PR to 'develop', and then merge 'develop' to 'master', we can get rid of having any files with their executable attribute set in the next release.

5 13

[yap] Re-announcing Yap
by Zach Laine 23 Feb '18

23 Feb '18

I posted 2-3 months ago about Yap, an expression template library I've written that I intend to propose for Boost. This is just a reminder that the library exists, and where to find it. I'm giving a talk about it at C++Now 2017, and some time after that I intend to submit it to the queue. Louis Dionne has offered to serve as review manager when the time comes. You can find the main repo on GitHub: https://github.com/tzlaine/yap And online docs are here: https://tzlaine.github.io/yap Zach

4 6

Query for interest in library: reflective enum
by Nir Friedman 23 Feb '18

23 Feb '18

Hello, I recently needed a reflective enum for work (that is an enum where you can programmatically convert to and from strings, know how many enumerators there are, and iterate over all enumerators). I looked online but I didn't find anything that met my requirements. I was surprised that there wasn't one in Boost. So I'd like to see if there is interest; I wrote an implementation that I think has several nice features. The most polished existing smart enum implementation I could find was http://aantron.github.io/better-enums/. However, the enum implemented there is not a true enum; it uses a nested member of a class kind of approach. So for example, the is_enum type trait will not recognize is as an enum. You cannot use it as a non-type template parameter. I strongly think that a good generic smart enum macro should generate the exact "vanilla" enum (or enum class) declaration. My library's syntax looks like this: WISE_ENUM(Foo, BAR, (BAZ, 3)) This generates, among other things, exactly: enum Foo { BAR, BAZ=3}; I intend this as an explicit guarantee of the library that the programmer can count on. That way when Foo is used for things unrelating to reflection, the developer can be confident that there will not be any surprises. Beyond compatability with C++ facilities for enums, and minimizing surprise, another advantage of this approach is that it's guaranteed to be backwards compatible. An existing codebase with an existing enum/enum class can switch to this smart enum with very high confidence that existing code will continue to work as before. The WISE_ENUM macro, beyond generating the vanilla enum, also generates a switch-case function for to-string conversion (for maximal efficiency), and finally it generates a constexpr function that returns a std::array<std::pair<const char*, Foo>> listing all of the arrays and their string descriptions. This constexpr function, which is found via ADL, allows writing a sequence of (constexpr) variables and functions providing the rest of the desired functionality. Usage looks like this: std::cerr << "My enum's size is : " << wise_enum::size<Foo> // this is constexpr template variable auto x = wise_enum::from_string<Foo>("BAR").value(); // from_string returns an optional auto y = wise_enum::to_string(x); // y is string literal, no heap allocation My implementation (POC level) is here: https://github.com/quicknir/wise_enum. I don't yet have separate macros to cover enum/enum class/explicit/implicit backing type combinations. It's only about 100 lines of code, leaning heavily on BOOST_PP to do the heavy lifting. It requires variadic macros, and can probably target C++11 (if it doesn't already). I probably need to "comma harden" the macros for bizarre stuff like WISE_ENUM(Foo, (BAR, my_func<3,4>())). It has the limitation that the macro cannot be used inside a class (this is hard to workaround for reflective macros). It's also unclear how repeated enumeration values would be handled (enum Foo { BAR = 1, BAZ = 1}). As it stands this will cause a compilation failure in the generated switch case of the to_string function. Can discuss more in subsequent emails. One suggested feature is an is_contiguous trait. Another reasonable bit of functionality might be an is_wise_enum trait. Version 2 of this library could target enum sets. Although it's not fancy, I think this nicely covers a piece of functionality I often need, and it does so avoiding any downside compared to using a simple enum (beyond having to use macros). Hope other people will agree! Cheers, Nir

4 5

[release notes] Linking to github issues/pull requests
by Daniel James 14 Feb '18

14 Feb '18

Hi, I've added templates for linking to github issues and pull requests from the release notes. There are two templates: [github module number] which expands to '#number' [github_pr module number] which expands to 'PR#number'. Both will be linked, they need the name of the module to link to the right place. We only really need the issue template as github redirects to the pull request if appropriate, but existing release notes have been using the PR#3 format, so I thought it should support that. You can see an example in the unordered release notes for 1.67.0: https://github.com/boostorg/website/blob/master/feed/history/boost_1_67_0.q… http://www.boost.org/users/history/in_progress.html Does that look okay? Daniel

5 17

[review] Review of Outcome v2 (Fri-19-Jan to Sun-28-Jan, 2018)
by charleyb123 . 09 Feb '18

09 Feb '18

Hi, Everyone, The formal review of Niall Douglas' Outcome (v2) library begins Fri-19-Jan and continues until Sun-28-Jan, 2018. Your participation is encouraged, as the proposed library is uncoupled and focused, and reviewers do not need to be domain experts to appreciate the potential usefulness of the library and to propose improvements. Everyone needs (and has suffered) error handling, and can compose an opinion on that topic. Outcome is a header-only C++14 library providing expressive and very lightweight 'outcome<T>' and 'result<T>' error handling, suitable for low-latency code bases. The library further provides mechanisms for wrapping '<success|error|exception>' state to safely wrap throwing APIs; and poses an idiom of, "islands of exception in a sea of noexcept". Key features: *- Makes using 'std::error_code' from C++11's <system_error> more convenient and safe *- Good focus on low-latency (with tests and benchmarks) *- Error-handling algorithmic composition with-or-without C++ exceptions enabled *- Dependency only on Boost Recall a previous Outcome (v1) Boost Review occurred 19-May to 02-June 2017: *- Outcome (v1) Review Report: *- https://lists.boost.org/Archives/boost/2017/06/235783.php This review for Outcome (v2) includes significant changes as a result of feedback from the Outcome (v1) review. For a list of changes (v1==>v2), see: *- https://github.com/ned14/outcome#changes-since-v1 Reference API docs: *- https://ned14.github.io/outcome/reference/ GitHub: *- https://github.com/ned14/boost-outcome Tarball: *- https://github.com/ned14/boost-outcome/releases/tag/v2. 0-boost-peer-review Online "play-pen" (try it out!): *- https://wandbox.org/permlink/Ji1khzyxoAR0LJQC YOUR REVIEW --------------------- Please post your comments and review to the boost mailing list (preferably), or privately to the Review Manager (to me ;-). Here are some questions you might want to answer in your review: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? And most importantly: - Do you think the library should be accepted as a Boost library? For more information about Boost Formal Review Process, see: http://www.boost.org/community/reviews.html Thank you very much for your time and efforts. --charley Outcome (v2) Review Manager

24 122

[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

[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

[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