OpenEuphoria

1. Regular Expression Change

• Posted by jeremy (admin) Mar 23, 2009
• 1008 views

Just so everyone is aware, as of today, the regular expression code included with Euphoria is PCRE compiled into Euphoria. include/std/pcre.e has been renamed include/std/regex.e. The old include/std/regex.e is now gone as well as it's related tests, docs and code in the backend. For those that have built upon the regex.c/.h that was in SVN for quite some time and also in the 4.0a1, 4.0a2 and 4.0a3 releases, you may need to alter your regular expressions slightly. The core of everything should work w/o issue, however, there is differences with more complex regular expressions.

So, if you are using an up-to-date eubin or compiling from SVN and your regular expressions seem to not function correctly, this is why.

Jeremy

3. Re: Regular Expression Change

• Posted by jeremy (admin) Mar 23, 2009
• 996 views

Bernie,

Here is what I understand is:

1. For Euphoria: we need to include the license file and not remove the copyright from the source files. 2. For programs written in Euphoria, if you use regular expressions, you need to include a copyright statement for the pcre library along with your copyright. Sometimes that is in a doc file, other times in a Help > About screen.

Before beta 1 is release, I'll have the doc page for PCRE updated to be of more assistence with this.

Jeremy

5. Re: Regular Expression Change

• Posted by jeremy (admin) Mar 23, 2009
• 982 views

Derek,

The third party copyright message is a good idea, but I wonder if we should include the Euphoria copyright in there as well. It would be nice for people to display an attribution to Euphoria. I wonder if we should give the user a bit of freedom here, for instance, if it were a an app I wrote using EuQT, then I would want to format the message in HTML code, they have a nice about dialog box for that. Others may want to display it in another manner. What about something in regards to:

public function get_copyright_statements() 
    return {  
        { "Euphoria v4.0", "Copyright (c) 2009 ..." }, 
        { "PCRE v7.8.4", "Copyright (c) ..." } 
    } 
end function 

That would require more work on the users part though. Just thinking aloud.

BTW, you can look at quite a few commercial apps and see the PCRE copyright message in their Help>About screens. One comes to mind right away, Apple's web browser, Safari.

Jeremy

7. Re: Regular Expression Change

• Posted by jeremy (admin) Mar 23, 2009
• 998 views
• Last edited Mar 24, 2009

Yeah, me as well. Prob needs a little planning, but a pretty easy function to whip up. Hm, built-in or library routine? Something about it smells to me that it should be a built-in, however, it seems so simple to even bother building it in. I'm waffling, but leaning to saying library routine, but then you gotta ask where?

I don't think I really care. Hm, is there a way to get the Euphoria version number from Eu code? i.e. eu_version() "4.0a3"

Jeremy

9. Re: Regular Expression Change

• Posted by euphoric (admin) Mar 23, 2009
• 1000 views
• Last edited Mar 24, 2009

It's just a simple step from this to allowing libraries to register their version numbers...

-- myinclude.e 
register({2009,1,1,X,Y,Z...}) -- lib passes version sequence in {Y,M,D,A,B,C} format 
   -- when Euphoria encounters a register() statement, it simply adds the include file ("myinclude.e") 
   -- and its associated version number sequence to a special internal list that can be called by apps 
 
-- myproggie.e 
 
require myinclude.e {2009,1,2} -- a special include that helps with version management? 
--include myinclude.e 
require win32lib.e {2008,8,12} -- wouldn't this be nice? 
 
sequence 
   regs = get_registered_libs() 
 
for t=1 to length( regs ) do 
   -- puts(1, ... ) 
end for 
 
-- etc... 

The version sequence can be anything the library user wants to use, or we can make a standard. I like using dates myself, because it's just easier. The {...A,B,C} designations can cover alpha/beta/RC version numbers.

11. Re: Regular Expression Change

• Posted by euphoric (admin) Mar 24, 2009
• 1013 views

Back in January of 2007, I added this Feature Request, which is basically the same but a bit verbose (I shouldn't have to tell the interpreter what file is registering the version sequence). I think what I posted here is an improvement over that initial idea.

Anyway, should I go ahead and add it to the Wish List also? Or should I respect DRY?