arbv
commented
7 years ago I believe we should upgrade to the newer version of the VS. I tracked some changes in your repo. They are very interesting and I believe they should be merged into upstream ASAP.
I was even thinking about using build system (FastBUILD) to make supporting builds with different versions of VS more simple. I am not sure it worth it, though. What do you think?
P.S. Porting the neural net application seems alike a lot of fun! I believe it will be a very interesting program to have in the examples directory.
rgcorman
I forked my own repo, and have done a bit of work in that, which I would like to merge into the sharplispers cormanlisp tree.
I have been using Visual Studio 2015 on all my workstations at this point and went ahead and updated the code base to VS 2015. I made a new solution file, but there are 10 project files that also got updated and I don't think maintaining separate project files is that great. Do we want to update the master to build with VS 2015? I've tested quite a bit and it's working well. I've also run with the community (free) version and it builds fine.
I also have a couple bugs to check in and some enhancements that add support for more Win32 library calls. I ported a neural net simulator program that's really cool--it has a bunch of minesweepers, each with a neural net as a brain, and they drive around trying to disarm the mines. At first they drive really badly, like driving in circles, but as they evolve (also uses a genetic algorithm) the neural net of each mine gets better at finding the mines. I plan to put that in the examples directory--it's all in one lisp file.
I also fixed the editor in the IDE so that it correctly saves and restores documents, positions etc. like it used to.
I'll check in all these changes, but just need to sort out the VS version issue above. Roger