- Boost - lists.boost.org

Call for Papers - ICITST-2019 - London, UK
by Galina Akmayeva, ICITST 20 Sep '19

20 Sep '19

CALL FOR PAPERS! ************************************************************ The 14th International Conference for Internet Technology and Secured Transactions (ICITST-2019) Venue: CCT Venues-Docklands London, UK December 9-11, 2019 www.icitst.org ************************************************************ The ICITST is an international refereed conference dedicated to the advancement of the theory and practical implementation of secured Internet transactions and to fostering discussions on information technology evolution. The ICITST aims to provide a highly professional and comparative academic research forum that promotes collaborative excellence between academia and industry. The ICITST-2019 invites research papers that encompass conceptual analysis, design implementation and performance evaluation. The topics in ICITST-2019 include but are not confined to the following areas: Internet Applications and Technology: * Internet Architecture * Internet of things * Broadband Access Technologies * Application Agents * Boundary Issues of Internet Security * Database Management * Data Models for Production Systems and Services * Artificial Intelligence and Expert Systems * IPSec Quality of Service * Knowledge Management * Embedded Systems * Defence Systems Ubi/Cloud Computing: * Authentication and Access Control for Data Protection in Ubi/Cloud Computing * Context-Awareness and its Data Mining for UbiCom * Data Grids * Distributed Information Systems * Human-Computer Interface and Interaction for UbiCom * Ubiquitous Systems * USN/RFID Service * Smart Homes and its Business Model for UbiCom Service * Security and its Data Management for UbiCom * Peer to Peer Data Management * New Novel Mechanism and Application for Ubi/Cloud Computing Information Security: * Trust, Privacy and Data Security * Network Security Issues and Protocols * Security Challenges and Content Authoring * Cryptography * Secure Communications * Authentication Techniques * Chaos-based Data Security * MANET Security * Wireless Sensor Network Security * Organization Considerations in Security Policy Formulation and Implementations * Digital Forensics and Crimes * Biometrics * Cyber Security Multimedia and Web Services: * Intelligent Multimedia and its Data Management * Multimedia Information Systems * Multimedia Security * Web Databases * Web Metrics and its Applications * Web Mining including Web Intelligence and Web 3.0. * Web Services * XML and other extensible languages * Semantic Web and Ontology Bitcoin *Challenges and its Roadmap *Crypto-Assets *Current State of Privacy in Bitcoin *Decentralised Technology *Data Licensing *Digital Currencies *Fintechs *Future Payment Implications *Standardisation-Related Issues *Technical, Business and Regulatory Aspects *Technology-based Risks Infonomics and e-Technology: * Infonomics * Information Visualization * Information Management * Information Quality * Technology-Enabled Information * e-Learning * e-Commerce * e-Business * e-Government * e-Society * System Design and Security for e-Services * Synchronizing e-Security Submissions: *You can submit your abstract via email at abstract(a)icitst.org *You can submit your extended abstract or paper online at http://icitst.org/paper-submission/ or email it to extendedabstract(a)icitst.org or papers(a)icitst.org *You can submit your poster via email at posters(a)icitst.org *You can submit your workshop or tutorial proposal via email at workshop-tutorial(a)icitst.org *You can submit your speaker's proposal online at https://icitst.org/call-for-speakers/ or via email at speakers(a)icitst.org Submission Dates: *Abstract and Extended Abstract Submission Date: September 20, 2019 *Notification of Abstract and Extended Abstract Acceptance/Rejection: September 25, 2019 *Proposal for Industrial Presentation: September 20, 2019 *Notification of Industrial Presentation Acceptance: September 25, 2019 *Full Paper Submission Date: September 27, 2019 *Notification of Paper Acceptance/Rejection: October 10, 2019 *Workshops and Tutorials Submission Date: September 20, 2019 *Notification of Workshop and Tutorial Acceptance: September 25, 2019 *Special Track Submission Date: September 20, 2019 *Notification of Special Track Acceptance: September 25, 2019 *Poster/Demo Submission Date: September 20, 2019 *Notification of Poster/Demo Acceptance: September 25, 2019 *Camera Ready Paper Due: November 15, 2019 *Early Registration Deadline: October 25, 2019 *Late Registration Deadline: November 25, 2019 *Conference Dates: December 9-11, 2019 For more details, please contact [1]info(a)icitst.org References 1. mailto:info@icitst.org

1 0

[multiprecision] how to catch both underflow and overflow
by blacksmith＠peerfreedom.org 20 Sep '19

20 Sep '19

Hello, when using boost multiprecision [1] to execute even simple math operations like addition x = x+1 or x-1 it seems on mathematical error it might throw either std::range_error or std::overflow_error or std::underflow_error . Sadly it seems that it's not the case that overflow and underflow are child classes of range_error. So, in more complex math expression to detect any math error you must write catch(....) for all 3 of them (because just catching common std::runtime_error would be too broad and might hide some unrelated error). Is there some better way for this? Perhaps boost should introduce a common type for math error and throw own under/over/range errors that inherit from std's one (for compatibility) and also inherit from boost::math_range_error to allow catch (boost::math_range_error) // either over/under flow or other math [1] for example using type like: boost::multiprecision::number< boost::multiprecision::cpp_int_backend< 64-1, 64-1, boost::multiprecision::signed_magnitude, boost::multiprecision::checked, void> > -- GPG: 31A8 55AA 07BE 5145 65EB 2292 65A6 1F7A 9781 DF89

3 2

Requesting endorsements of Boost.STLInterfaces for review
by Zach Laine 20 Sep '19

20 Sep '19

As mentioned a couple of weeks ago, I started a small library that was an updated iterator_facade. It is now a still-smallish library called stl_interfaces that includes a pre-C++20 implementation of view_interface, and analogous templates iterator_interface (a cross between Boost.Iterator's iterator_facade and iterator_adaptor), and container_interface. Each of these makes it easier to write a view, iterator, or container, respectively. Using container_interface, I was able to write a version of static_vector in which I implemented only 21 member functions, and the template provided the other 40(!) functions. The library is C++14 and later. There is an inline v1 namespace for the C++14 implementations, and an experimental non-inline v2 namespace with implementations using C++20 standard concepts. The part using C++20 concepts requires GCC 8 or 9, and cmcstl2 (more info on that on the Github page). Github page: https://github.com/tzlaine/stl_interfaces Online docs: https://tzlaine.github.io/stl_inteTherfaces/doc/html/index.html <https://tzlaine.github.io/stl_interfaces/doc/html/index.html> Oh, and if you're willing to act as review manager, please let me know. Zach

9 17

[GitHub] Checks not listed for Travis CI
by Mateusz Loskot 18 Sep '19

18 Sep '19

Hi, GitHub offers the Checks tab [1] which displays CI checks based on Travis CI, Azure Pipelines, etc. I can't find out why the Travis CI ones are not displayed for any of repositories under github.com/boostorg/ I checked Histogram, Beast, and a few others and ffor GIL only Azure Pipelines is displayed (I integrated AzP there from the marketplace fairly recently). I suspect, that is due to the fact Travis CI integration was installed long time ago, using an old way, so it does not 'recognise' new features. For example, using the old webhooks/services method now deprecated which then was automatically ported to new marketplace-based integrations. Does anyone know how to add the Checks feature to boostorg/ repos? One of interesting feature of it is that it can display "a specific line in a commit causes a check to fail" [1] [1] https://help.github.com/en/articles/about-status-checks#checks Here is example of the Checks in full: https://github.com/OSGeo/gdal/pull/1776/checks I can confirm enabling the Checks has nothing to do with the branch protection feature and enabling required statuses of PRs. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

2 2

Details of environment building release docs and website
by Mateusz Loskot 18 Sep '19

18 Sep '19

Hi, Where can I find details about the environment used to build the website and the documentation for the releases? For example, - What is the OS? (i.e. system packages can be identified then) - What is toolset and compiler version used? GCC 4.8? - What is the version of Python, Doxygen, AsciiDoc, Sphinx? I looked at these places, but it's still unclear to me https://www.boost.org/development/website_updating.html https://github.com/boostorg/website/blob/master/.travis.yml Or was I supposed to derive the answer from the Travis CI's image php:'5.3'? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

[Quickbook] VSCode Extension for syntax colouring & simple preview
by Jan Bouwer 18 Sep '19

18 Sep '19

I've built a Visual Studio Code <https://code.visualstudio.com/> extension to provide simple syntax colouring & preview generation for Boost.Quickbook source files. It is available from within the VSCode extension marketplace or at https://marketplace.visualstudio.com/items?itemName=JBouwer.boost-quickbook… - from where the GitHub repos/issue tracker can be accessed too. Perhaps somebody else may find this useful too - like I have. Regards Jan Bouwer

2 1

[program_options] Proposal: self-contained, header-only port of Boost Program Options library
by Vicram Rajagopalan 17 Sep '19

17 Sep '19

I am interested in creating a header-only implementation of the Boost Program Options library that only depends on the C++ standard library. Program Options uses several other Boost libraries, so I would have to re-implement some of it using standard library constructs. I have 2 questions for the community: 1. Would you use something like this if it were available? 2. Do you know of any implementation details of Program Options which might make some part of this difficult or impossible? To be clear, I do not intend for this to be merged into Boost in any form. Rationale: There is no portable command-line argument-parsing capability in the C++ standard library. There's getopt, but that's in unistd.h which is only available on Unix-based systems. The only widely-used C++ command-line parsing library I am aware of is Program Options, but that requires adding a dependency on Boost to your project, which seems like overkill to me. I would like to be able to simply add a project as a submodule in my Git repo and #include it without even having to add anything to my build files. The goal is to ensure that the library is as portable and easy to include as possible, because it shouldn't be difficult to parse command-line options. I appreciate any thoughts, comments, or criticisms! -Vicram Rajagopalan

9 14

[Boost.numeric.ublas] Compiler warnings when building with O2 optimizations and NDEBUG defined
by Albert Perlman 17 Sep '19

17 Sep '19

I am using boost v1.69, compiling with g++-7 for an x86 target. If I build with -O2 optimization flags when NDEBUG is defined, I get the following compiler warning: ./../boost/numeric/ublas/matrix_expression.hpp:59:20: error: ‘*((void*)&<anonymous> +8)’ is used uninitialized in this function [-Werror=uninitialized] return e_.size2 (); If I add -fno-partial-inling to the compiler flags, this makes the warning go away. This warning does not appear if NDEBUG is not defined, regardless of optimization flags. This behavior is the same with boost v1.71. I would like to build with the -fpartial-inling optimization when NDEBUG is defined. Is there a workaround to fix this warning? -- Albert -- IMPORTANT: The information contained in this transmission may be privileged, proprietary and confidential and protected from disclosure. It is intended only for the intended recipient. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you may not disclose, copy or distribute this transmission or take any action in reliance on it. If you received this transmission in error, please notify us immediately by replying to this message and please dispose of and delete this transmission. Thank you. Yaskawa America, Inc.

1 0

Write data to NAND flash file system
by JH 13 Sep '19

13 Sep '19

Hi, I am using boost::filesystem to write / remove files to NAND flash file system where it writes by pages, the system can cache and pack data upon write back to avoid segmentation if fsync(), fdatasync(), O_SYNC or a sync mounted filesystem are not used to force write. Will the boost::filesystem::ofstream and operator<< involve any of sync call? Which IO library is not using sync call? Thank you. Kind regards, - jupiter

1 0

math
by Gero Peterhoff 12 Sep '19

12 Sep '19

Hello Developers, Hello John, thanks for making the float128_t features I missed available in boost 1.71. But: - I miss in boost::math::constants log2_e (M_LOG2E); You have written in the documentation that all constants are now available; are there any other constants missing? - in boost/multiprecision/float128.hpp, the value in numeric_limits<float128_t>::is_bounded must be true Thanks and Greetings Gero

2 1