Addition to benchmark suite

[ArashPartow]

The following question/discussion is based on a comment by @devernay and the following project

---

Issue 1

We'd like to add SeExpr to the above benchmark suite. A cursory attempt at trying to integrate the library seems like there may be issues with building the code on VS2015 (I'm probably doing something wrong). Does SeExpr build with VS2015 (sp2/3) or is it for now only VS2010 compatible?

---

Issue 2

Another issue, is that I can't seem to find any documentation or example code (perhaps a timed benchmark or test suite), for the correct usage of SeExpr in a high performance scenario. eg: evaluating an expression (such as: 2*x-3y) many times where the values for x and y will be changing between each evaluation - would there happen to be an example or a link to some documentation for this kind of scenario? (I did notice asciiGraph but I'm not sure if that is how it would be done in a real/production environment)

---

Issue 3

It seems the parser is generated using Bison, which is great. But would it be possible to have a clean vanilla seperate repo, that includes only the generated SeExpr library source code and a simple functioning example demonstrating the use of the library, that does not require 3rd party dependencies like Qt, png, zlib, python etc. I'm currently looking at asciiCalc and asciiGraph example as my basis - it in short it's really confusing. Perhaps a simple example, something like: this might be beneficial.

---

Issue 4

In order to get the LLVM backed version working, what are the actual dependencies? Is there documentation that describes getting such a build working?

[jberlin]

Good questions!

1. We've built internally against VS 2013 on Windows 7.
2. We have some internal examples of evaluating expressions with varying points, frame numbers, u-v coordinates, etc., but they are non-trivial. This would be good to add to the documentation, and we can work on making an example available.
3. We could probably accomplish what you are looking for by allowing the build of each component independently (core library, ui, demos), so that you can build the core library without the dependencies needed by the ui or demos.
4. We are encouraging the adoption of the latest version, with LLVM support, rather than continued use of the older versions. We can provide build documentation with dependencies.

I'll try to get some of this additional information out in the next few weeks -- thanks for the feedback!