From: Terablade (terablade2001_at_[hidden])
Date: 2019-09-08 13:17:11
Recently I focused on completing and releasing a public a C/C++ library for C/C++ Error Control System. I've exposed the library to public via two articles in Linked In, and especially in the "C++ Developers Groups" were I got some positive feedback (a few comments and likes). A "Senior Architect at Apple" left the following comment: "Man thatâs error traceability for a lot of readability". This made me wonder if this library deserves to be exposed more to C/C++ developers, and led me to think of boost library.
Personally I'm testing the library by integrating it in different projects, and I'm quite happy from the outcome. With very few code (increased readability) and a specific design approach for capturing and handling possible errors, it does provide a lot of customized error traceability - a feature which for me is quite important on complex projects and especially when multiple libraries mix up and need integrated error tracking through all of them.
Reading the boost guidelines I joined this mailing list to request review and opinions.As my free time is a a bit limited to convert and test the library to be supported by boost, I'd like some comments and review first.Do you believe that CECS could be a useful util for Boost? Should I go for it?
The two articles in that group (requires membership) is at:https://www.linkedin.com/feed/update/urn:li:activity:6568218380594098176https://www.linkedin.com/feed/update/urn:li:activity:6573340808068517888The articles are also in my profile:https://www.linkedin.com/pulse/cecs-cc-error-control-system-vasileios-pothos/https://www.linkedin.com/pulse/signals-tracking-cecs-vasileios-pothos/
I have also released the library on github:https://github.com/terablade2001/CECS
I'd like to note that the library has been favored till now by 7 accounts in github (8 including me) which, for me, is also a positive feedback.
Thanks for your time,V. Pothos
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk