From today, GLUEscript uses the tracker system of Sourceforge. Report your bugs or feature request at the tracker.

When you use the MinGW compiler you need to run some extra commands before you can actually build the MySQL glue:

First get MinGW-utils and extract the binaries in the bin folder of MinGW

Open a console window and go to the library directory of MySQL:

cd C:\Program Files\MySQL\MySQL Server 5.1\lib\opt

Then use reimp to create a .def file:

reimp -d libmysql.lib

To create the .a file, dlltool is used:

dlltool --input-def libmysql.def --dllname libmysql.dll --output-lib libmysql.a

Now you can successfully link the glue MySQL.

GLUEscript uses a lot of macro's in the source code. While many developers find macro's evil, I find them useful for GLUEscript for the following reasons:

• They reduce a lot of repeating code
• They hide difficult to read code
• When something changes only the macro needs to be changed

The third reason is the most important reason for me: Between two versions of GLUEscript the prototype of a callback was changed. Instead of searching and replacing all code in the source files, I only needed to change the macro of the callback.

The last reason of using macro's is that I have a dream, that one day I write a parser that automatically translates C/C++ code into GLUEscript code. Parsing the syntax of macro's is easier then parsing C/C++ code.

GLUEscript is mentioned on the POCO blog. Read what Alex has to say about GLUEscript.

I've uploaded new Premake4 scripts in subversion to compile POCO 1.3.5 with MinGW. With these scripts you can generate workspaces for Codelite or Code::Blocks. Follow these steps:

• Get the scripts from here: http://gluescript.svn.sourceforge.net/viewvc/gluescript/trunk/src/poco.zip
• Unarchive the zip archive and copy all Lua scripts to the corresponding POCO directories
• Open a command window and go to the POCO directory
• Run premake4 and use codelite or codeblocks as action:
  premake4 codelite
  You need to run premake4 in the POCO directory!
• Open codelite and build the projects. Make sure the Foundation project selects the gcc compiler, not the g++ compiler because zlib compilation fails with g++.

Make sure you use the latest version of MinGW! Don't use the version that is shipped with Codelite or Code::Blocks

It's been more then 3 months that I'm working on the Poco JavaScript environment for SpiderMonkey. While I was converting some glues to the this new environment, I found a lot of bugs, enhancements, ... Today I think the SpiderMonkey framework is ready. The glues for cURL and SQLite are converted and they work. In the meantime I keep on converting the other glues to the Poco C++ Coding Style and to use the framework, so be patient for the next release ...

The design of the POCO SpiderMonkey framework is ready. Now I'm converting all the glues to this framework. This is alot of work, but this will be the best way to test the SpiderMonkey framework. In the meantime I change the code to follow the POCO C++ Coding Style Guide. When I feel it is ready, the framework will be contributed to POCO. You can follow everything in the Subversion repository.

The GLUEscript project will work on an JavaScript Environment for POCO. POCO already has an environment for LUA. This code is stored in the POCO sandbox, so it will not be available in the official POCO release in the near future.

The apache module uses a modified version of the Apache Connector from the POCO framework. Configure this as follows:

LoadModule poco_module c:/glue/bin/mod_poco.dll
AddPocoRequestHandler GLUERequestHandlerFactory c:/glue/bin/glue_apache.dll <path>
AddHandler glue .js

All JavaScript files in path are handled by GLUEscript.