remove trailing spaces from readme.txt

This commit is contained in:
Bernd Amend 2021-05-24 21:11:12 +02:00
parent 0f37802aba
commit a1a78e9cf1

View File

@ -27,16 +27,16 @@ Introduction
[![Gitter](https://badges.gitter.im/JoinChat.svg)](https://gitter.im/ChaiScript/ChaiScript?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [![Gitter](https://badges.gitter.im/JoinChat.svg)](https://gitter.im/ChaiScript/ChaiScript?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
ChaiScript is one of the only embedded scripting language designed from the ChaiScript is one of the only embedded scripting language designed from the
ground up to directly target C++ and take advantage of modern C++ development ground up to directly target C++ and take advantage of modern C++ development
techniques, working with the developer how they would expect it to work. Being a techniques, working with the developer how they would expect it to work. Being a
native C++ application, it has some advantages over existing embedded scripting native C++ application, it has some advantages over existing embedded scripting
languages: languages:
1. It uses a header-only approach, which makes it easy to integrate with 1. It uses a header-only approach, which makes it easy to integrate with
existing projects. existing projects.
2. It maintains type safety between your C++ application and the user scripts. 2. It maintains type safety between your C++ application and the user scripts.
3. It supports a variety of C++ techniques including callbacks, overloaded 3. It supports a variety of C++ techniques including callbacks, overloaded
functions, class methods, and stl containers. functions, class methods, and stl containers.
@ -66,17 +66,17 @@ Usage
* Add the ChaiScript include directory to your project's header search path * Add the ChaiScript include directory to your project's header search path
* Add `#include <chaiscript/chaiscript.hpp>` to your source file * Add `#include <chaiscript/chaiscript.hpp>` to your source file
* Instantiate the ChaiScript engine in your application. For example, create a * Instantiate the ChaiScript engine in your application. For example, create a
new engine with the name `chai` like so: `chaiscript::ChaiScript chai` new engine with the name `chai` like so: `chaiscript::ChaiScript chai`
* The default behavior is to load the ChaiScript standard library from a * The default behavior is to load the ChaiScript standard library from a
loadable module. A second option is to compile the library into your code, loadable module. A second option is to compile the library into your code,
see below for an example. see below for an example.
Once instantiated, the engine is ready to start running ChaiScript source. You Once instantiated, the engine is ready to start running ChaiScript source. You
have two main options for processing ChaiScript source: a line at a time using have two main options for processing ChaiScript source: a line at a time using
`chai.eval(string)` and a file at a time using `chai.eval_file(fname)` `chai.eval(string)` and a file at a time using `chai.eval_file(fname)`
To make functions in your C++ code visible to scripts, they must be registered To make functions in your C++ code visible to scripts, they must be registered
with the scripting engine. To do so, call add: with the scripting engine. To do so, call add:
chai.add(chaiscript::fun(&my_function), "my_function_name"); chai.add(chaiscript::fun(&my_function), "my_function_name");
@ -86,15 +86,15 @@ Once registered the function will be visible to scripts as "my_function_name"
Examples Examples
======== ========
ChaiScript is similar to ECMAScript (aka JavaScript(tm)), but with some ChaiScript is similar to ECMAScript (aka JavaScript(tm)), but with some
modifications to make it easier to use. For usage examples see the "samples" modifications to make it easier to use. For usage examples see the "samples"
directory, and for more in-depth look at the language, the unit tests in the directory, and for more in-depth look at the language, the unit tests in the
"unittests" directory cover the most ground. "unittests" directory cover the most ground.
For examples of how to register parts of your C++ application, see For examples of how to register parts of your C++ application, see
"example.cpp" in the "samples" directory. Example.cpp is verbose and shows every "example.cpp" in the "samples" directory. Example.cpp is verbose and shows every
possible way of working with the library. For further documentation generate possible way of working with the library. For further documentation generate
the doxygen documentation in the build folder or see the website the doxygen documentation in the build folder or see the website
http://www.chaiscript.com. http://www.chaiscript.com.