Re: 4.0a3 - Two Regular Expression Libraries? -- We need your input!
- Posted by jimcbrown (admin) Mar 22, 2009
- 1147 views
One advantage to the "binding the dll as a resource" approach is that one can update the resource with a newer version of the dll when necessary (e.g. we need to update due to a security flaw in the older version). It is not necessary to recompile the interpreter .exe, or any bound programs, to do this.
This more I think about this, I'm for more frequent releases of Euphoria, big or small. For instance, one product I work with that I really enjoy has a 3 month cycle. New products will be released every 3 months, even if only a few bug fixes. If we manage the SVN repo right, a new relase w/fixed pcre (or any other flaw in Euphoria) should be easy to accomplish. Here's how...
When I release a version of Euphoria, I tag the svn TRUNK, for instance, http://rapideuphoria.svn.sourceforge.net/svnroot/rapideuphoria/tags
We then continue working on SVN trunk as if nothing happened. Now, we have the tag. Let's say svn trunk is 1/2 thru it's release cycle and a major flaw is found (in anything, PCRE, Euphoria std lib, Euphoria core), we tag a new version (say 4.0.1 off of tags/4.0.0) and we make the appropriate fixes to code, and run the package scripts to release 4.0.1. We then simply merge tags/4.0.1 into trunk and the changes made in 4.0.1 are then applied to our SVN trunk, where the next version of Euphoria will come from.
Jeremy
It is not clear to me what you are saying here - that we should release a new version of Euphoria when a PCRE issue is discovered and fixed (and then propagated to update our svn) ?
This also doesn't address the point for a bound app (that you can just update the resource that holds pcre.dll rather than having to rebind the app under the new version of Euphoria), although I suppose that is a minor enough detail that we don't have to worry about it.
