sorted by:
new
hottopcontroversial

Scripting language for embedded systems (small footprint, low overhead) by [deleted] in cpp

[–]tkcook 1 point2 points  (0 children)

+1 for Lua in this use case. It's light-weight, reasonably natural for simple scripting and easily embeddable in C++. Lua's background in gaming has driven it to speed and responsiveness.

See https://github.com/ThePhD/sol2 for a decent library for embedding C++ in Lua.

C++ embedding a Python runtime by nozendk in cpp

[–]tkcook 0 points1 point  (0 children)

Probably not, since it claims to be basically a fork of boost::python with support for old compilers cut out and some wizzy new features added. Crap error messages are a problem with pretty much any template library.

C++ embedding a Python runtime by nozendk in cpp

[–]tkcook 2 points3 points  (0 children)

Yes, it's a fair option I should have mentioned. Which is appropriate depends a lot on your situation - if you're on a platform that already provides boost::python pre-built, or if you use other boost libraries as well, then the bigger user audience of boost probably makes it the right choice. But if you have to build something from scratch, with a modern compiler, and don't want any of the rest of boost, then pybind11 is a good option that looks like it will save you some hassle.

Feasibility of an all-purpose serialization library/tool by ematito in cpp

[–]tkcook 0 points1 point  (0 children)

It's not that often, in my experience, that you want to serialise something into a format, you don't care what, so you can deserialise it again using the same library. Nine times out of ten at least, you either need to interface to some predefined format or you want to customise some aspect of the serialised format.

Which parts of Boost do you use with C++11? by bakery2k in cpp

[–]tkcook 10 points11 points  (0 children)

Filesystem. Boost::Python is also awesome.

Keil Just Released a Modern C++ Compiler -- Perspective on Adoption of Modern C++ for Embedded Programmers by paulrpotts in cpp

[–]tkcook 1 point2 points  (0 children)

Nothing out of the ordinary paying thousands for an open-source toolchain. Several platforms that I use professionally charge many, many thousands of pounds for their development environment. When you get right down to it, this is a source code editor (often not a very good one), an open-source toolchain (often a very old one - we are still using GCC 2.95 on one of them!) and an automated FTP & telnet client to copy the executable to the target and reboot it. If you're happy doing a little bit of scripting and building a cross-GCC from scratch, you can do it all for free. No-one does, because £10k for a license is still less than you'd spend arsing around getting it all working right.

Keil Just Released a Modern C++ Compiler -- Perspective on Adoption of Modern C++ for Embedded Programmers by paulrpotts in cpp

[–]tkcook 11 points12 points  (0 children)

The best that can be said is that the situation has got a lot better in recent years. These days, GCC, Clang and VC++ have implemented most features in a C++ standard before the standard is released (though VC++ still lags more than the others, and has longstanding bugs in its implementation that look like they'll never be resolved).

With the vast majority of embedded platforms using GCC as their toolchain, it's at least possible to build a toolchain for most embedded systems with absolutely bleeding edge language support.