Since in the side branch we're currently working on we need a newer
version of Ragel (6.6, as 6.5 crashes on our code), I've implemented
some basic version checking, so that a project can ask a minimum Ragel
version it works with.

This has one catch though: it assumes that the current scheme of x.y
with y < 10 is kept indefinitely. For obvious reasons this might not be
that absolute so I should probably look to solve this in a more sensible
way.

On the other hand it should work great on the short term, which is
exactly what I was looking for right now.

HTH,

-- 
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/

If you found a .asc file in this mail and know not what it is,
it's a GnuPG digital signature: http://www.gnupg.org/

Attachment: ragel.m4
Description: application/m4

_______________________________________________
ragel-users mailing list
[email protected]
http://www.complang.org/mailman/listinfo/ragel-users

Reply via email to