C++ is growing incredible fast and it will continue in next future. To get more complete library, variadic templates, lambdas, string-view, smart-pointers, move semantic, concurrency, files, initializer lists, type inference…​

To learn, to practice new features from C++, to have a toolset to complete C++ library, to program in C++ with less "undefined behavior"

Once upon a time…​

I wrote some rules and C++ tools to help colleagues with no experience in C++ to survive with it.

But later, I discover It was pleasant to work with these tools, safe, easy to use, low dependencies…​ I’m also very interested in making safe programs (no crashes)

This toolset compiles with modern C++ (and it will be), but is not fully idiomatic. Some of the tools has been added to C++ standard library (regular expressions, tuples, date time…​), and there are new ways to solve most of the problems. It was time to play and learn with new C++ and these concepts

Let’s enjoy and learn new C++. Let’s have toolkit working with new C++. Let’s create your basic tools to develop from scratch. It’s a great excuse!!!

I loved my CountPtr implementation, my old tuples worked fine…​ Now both will be replaced by std implementation. Other tools, will be rewrited with modern C++.

I know It will be necessary to update frequently some parts of the library in order to keep updated to last versions of C++. It’s part of the game.

Previously I wrote the documentation with asciidoc, muse over emacs and doxys on some projects. Now I’m going to add doxygen (I’m not a fan of these kind of tools, I prefer something like asciidoc or emacs/muse, but it’s a standard).

I’m not focused on radical performance, I prefer:

• Safety

• I don’t like undefined behaviour

• I don’t like crashes due to programming mistakes. C++ could be a dangerous language. It’s easy to have crashes, I want a library protecting and helping the programmer.

• Message driven programming

• If we have a failure processing a message, usually is better to inform about it and continue with next one.

• KISS and YAGNI

• Easy to use API (the implementation could be complex)

• I will introduce features as soon I will require

• No thousands of options, better few options, easy to use and less verbose (try to compose, please)

• Make difficult to produce "write only code" using this library. The code using this library…​

• has to be easy to read

• writting simplicity is less important

• Small

• This is about having basic features, not incredible possibilities. There are great C++ libraries for that.

• Portability (win/linux)

• zero dependency

• C++ doesn’t have a standard dependency tool. It is going to be a small library, complex dependencies will be avoided

• Easy to compile

Performance is desired but not over safety, easy api…​

I have next flags activated on gcc/g++

jle will also provide a base exception class with stack. You will have to fill the stack manually (this is C++)

Computer is a state machine. Threads are for people who can’t program state machines

Message passing in an ansynchronous way, also generates new problems. Many times we need a synchronous communication. Erlang/Elixir solves it.

As Alan Cox said, you can develop state machines. In fact, all non trivial process, has to deal with states.

I will create an external DSL to write declarative finite state machines.

For asynchronous task like reading a socket.

OK, do it, wait for asynchronous events on a dedicated thread.

You can even execute your code in a dedicated thread, but not simultaneously with other code of your own program.

Doing it, will be as easy as adding a line JLE_ASYNCHR

Do it with processes. You can communicate them with pipes, rabbitmq, RESTful…​

This way, you can use all cores and even all available machines.

Concurrency with processes…​ is share nothing communicate with messages. The right way.

I will add support for RESTfull, rabbitmq, execute process and communicate with pipes.

As before, send it to a specific process configured to work with heavy and slow tasks.

make
make help
make libs
make doc
make test
make compile_test
make compile_examples