ChangeLog 92 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248124912501251125212531254125512561257125812591260126112621263126412651266126712681269127012711272127312741275127612771278127912801281128212831284128512861287128812891290129112921293129412951296129712981299130013011302130313041305130613071308130913101311131213131314131513161317131813191320132113221323132413251326132713281329133013311332133313341335133613371338133913401341134213431344134513461347134813491350135113521353135413551356135713581359136013611362136313641365136613671368136913701371137213731374137513761377137813791380138113821383138413851386138713881389139013911392139313941395139613971398139914001401140214031404140514061407140814091410141114121413141414151416141714181419142014211422142314241425142614271428142914301431143214331434143514361437143814391440144114421443144414451446144714481449145014511452145314541455145614571458145914601461146214631464146514661467146814691470147114721473147414751476147714781479148014811482148314841485148614871488148914901491149214931494149514961497149814991500150115021503150415051506150715081509151015111512151315141515151615171518151915201521152215231524152515261527152815291530153115321533153415351536153715381539154015411542154315441545154615471548154915501551155215531554155515561557155815591560156115621563156415651566156715681569157015711572157315741575157615771578157915801581158215831584158515861587158815891590159115921593159415951596159715981599160016011602160316041605160616071608160916101611161216131614161516161617161816191620162116221623162416251626162716281629163016311632163316341635163616371638163916401641164216431644164516461647164816491650165116521653165416551656165716581659166016611662166316641665166616671668166916701671167216731674167516761677167816791680
  1. Ragel 6.10 - Mar 24, 2017
  2. =========================
  3. -C codegen: test P vs PE in goto/call/ret statements in EOF actions, just
  4. before re-entering. If at the end of the input block then the EOF check is
  5. jumped to. This change prevents overrunning the buffer if control flow is
  6. issued in an EOF action without fixing the input pointer first. If a program
  7. properly issues an fhold before the control flow the program won't be
  8. affected.
  9. -Updated action label generation. The previous set of conditions for
  10. generating the label didn't cover actions coming from the eofAction pointer
  11. (eof trans covered since it points into the set of transitions).
  12. -Use separate signed/unsigned values for host type min/max. Using separate
  13. values avoids the need to type cast before the data goes into FsmCtx structs.
  14. Keep it in native types until it is used.
  15. -Optionally do not generate entry point variables. Adds noentry write option
  16. for data.
  17. -Various warning elimination and build updates.
  18. Ragel 6.9 - Oct 13, 2014
  19. ========================
  20. -updated command-line synopsis
  21. -ocaml: fix missing semicolon
  22. -ocaml: support -G1
  23. -ocaml: choose a unique name for type state
  24. -ruby: reduce the amount of calls to GET_WIDE_KEY()
  25. -union test case: warning fix
  26. -omit line directives around expression-oriented write statements
  27. -use AS_IF and test command to check if the DIST file is present
  28. -added missing std:: using
  29. -go: added '//line' directive support
  30. Ragel 6.8 - Feb 11, 2013
  31. ========================
  32. -The -G2 code generator for Go1 was rewritten. Table, flat and switch-based
  33. code generators were added. (Anton Ageev)
  34. -The CXXFLAGS variable is not longer set in the configure script.
  35. Ragel 6.7 - May 22, 2011
  36. ========================
  37. -The C vim file now supports L,l on the end of literal numbers, other syntax
  38. highlighting fixes.
  39. -Added an explicit cast when modifying _trans to eliminate compiler warnings
  40. on Windows/VC++
  41. -Fix for ruby 1.9 compatibility.
  42. -Fix for include directories (-I option) on Windows/VC++
  43. -Can now rename data variable in C# code generator.
  44. -Fix for non-char alphtype in C# code generator.
  45. -Fix for signedness of wide char in C code generator. when comparing the wide
  46. type against a literal we need to pick the right signedness for the literal.
  47. -Fixed arithmetic overflow in generated C# code. The C# _acts and _nacts vars
  48. should not be typed based on the size of the array elements they point to.
  49. Fixes a bug reported by Attila Sztupák.
  50. -Made the -L option work for Ruby.
  51. -Enhanced ragel.m4 (from Diego).
  52. -Applied GO patch from Justine Tunney.
  53. -Applied D2 patch from Johannes Pfau.
  54. -Applied Ocaml patch from ygrek.
  55. Ragel 6.6 - Dec 2, 2009
  56. =======================
  57. -Applied a number of patches from Diego Elio 'Flameeyes' Pettenò. Should not
  58. be modifying the program's arguments. Problem raised by const correctness in
  59. gcc 4.4. Other const-correctness and include fixes provided.
  60. -Fixed improper allocation of checks in makeIncludePathChecks.
  61. -Fixed segfault when there are no machine instantiations.
  62. -Fixed wrong line directives. Line directives need to use the fileName stored
  63. in the InputLoc stuctures from the parse trees, not the root source file,
  64. otherwise actions in included files will have the wrong source file names
  65. associated with the text.
  66. -Made a number of build system improvements. We locate the DIST file using
  67. $srcdir and source it. It contains settings for build_parsers and
  68. build_manual. This allows the user of a dist to enable only one.
  69. -Added missing files to doc/Makefile.am and examples/Makefile.am.
  70. -Added checks for pdflatex and fig2dev is build_manual is on.
  71. -Use automake --foreign so we don't need to have INSTALL and NEWS present.
  72. -Ragel VIM syntax files should be specialized by host language. Updated the
  73. VIM syntax files.
  74. -Added examples to the dist. Added unicode2ragel.rb to EXTRA_DIST in contrib.
  75. -Moved unicode2ragel.rb to the contrib directory.
  76. Ragel 6.5 - May 18, 2009
  77. ========================
  78. -Fixed a bug in graphviz generation. Ragel crashed when using -V and -M and
  79. the specified machine referenced another machine that wasn't included in the
  80. build.
  81. -The name "CS" is in use on OpenSolaris, changed to vCS to ease compiling
  82. Ragel there.
  83. -Converted to automake.
  84. -REALLY fixed a bug that was intended to be fixed in 6.4:
  85. Fixed a problem reading hex numbers that have the high bit set when the
  86. alphabet is signed and we are on 64 bit. This was reported by _why. The
  87. fix was provided by Wialliam Morgan. The literal 0xffffffff was used for
  88. a fully set long when -1L should be used instead.
  89. A null patch (whitespace changes) must have gotten checked after I was
  90. testing with and without the critical one-line patch and I forgot to enable
  91. make sure it was enabled in the final checkin version.
  92. Ragel 6.4 - Mar 22, 2009
  93. ========================
  94. -Moved back to a single executable. The old intermediate format can still be
  95. generated using the -x option. Ragel was split into frontend and backend
  96. programs in version 5.0. This was done to encourage interoperability with
  97. other tools. Since then, ragel has been made to work with qfsm, with ragel
  98. producing the intermediate format and qfsm consuming it. However, there has
  99. been no use of Ragel as a consumer of state machine data, with Ragel used as
  100. a code generator for DFAs. This is not surprising given that much of the
  101. complexity of Ragel is in the frontend, where the regular language to DFA
  102. compilation happens. Since the full benefits of the split have not
  103. materialized, and the split increases the complexity for users, Ragel has
  104. been made once again into a single executable.
  105. -Applied a fix to the documentation Makefile from John D. Mitchell.
  106. -Use CXXFLAGS instead of CFLAGS for C++ compiling. Patch from Diego
  107. 'Flameeyes' Pettenò.
  108. -Added support for DESTDIR variable. Patch from Diego 'Flameeyes' Pettenò.
  109. -Added a script called unicode2ragel.rb for generating unicode machines to
  110. the examples directory. From Rakan El-Khalil.
  111. -Fixed a copy-paste error in the documentation that was reported by Jose
  112. Quinteiro.
  113. -Added three new write commands:
  114. write start;
  115. write first_final;
  116. write error;
  117. These generate a reference to the start, first final and error state. When
  118. there are many different machine specifications in one file it is easy to
  119. get the prefix for these wrong (especially when you do a lot of copy-pasting
  120. of boilerplate). The problem can be avoided by using write commands.
  121. -Fixed a problem reading hex numbers that have the high bit set when the
  122. alphabet is signed and we are on 64 bit. This was reported by _why. The fix
  123. was provided by Wialliam Morgan. The literal 0xffffffff was used for a fully
  124. set long when -1L should be used instead.
  125. Ragel 6.3 - Aug 29, 2008
  126. ========================
  127. -Fixed an assertion that is too strong. In the condition code we need to copy
  128. transitions that have non-empty lmActionTable arrays so we don't assert
  129. emptiness in the constructor. Lift out the assertion and copy the array in
  130. the constructor.
  131. -Fixed and improved multiple include prevention. We now track the entire
  132. include history of a parser state to prevent duplicates.
  133. -Fixed crash on failed lookup of goto/call/etc target.
  134. Ragel 6.2 - May 9, 2008
  135. =======================
  136. -Bug fix: The lm_switch actions needs to set p from tokend when there is no
  137. user action.
  138. -Bug fix: when not using indicies we can't use a transitions's id to identify
  139. the eof transition to take. Instead add the transition to the end of the
  140. transition list and store its position in a new var called pos. The pos var
  141. is then used as the index.
  142. -Bug fix: an fnext followed by an fbreak in -G2 was not working. The fbreak
  143. was not aware that the fnext causes the cs variable to be forced active. In
  144. this case fbreak does not need to save cs because it is already current.
  145. -Bug fix: need to compute the low and high character-space keys from the
  146. condition-trans overlap when computing an expansion. Can't use the range
  147. supplied from the condition overlap since they may not match. An incorrect
  148. machine that accepted 1(!cond1, !cond2) was generated for the following
  149. grammar. This bug was reported by Tim Chklovski.
  150. c = 2 @matched_c;
  151. sc1 = 1..2 when cond1;
  152. sc2 = 1..2 when cond2;
  153. main := sc1 | c | sc2;
  154. -Bug fix: error messages in start label analysis of join operations were
  155. causing assertion failures because location info was not set. Fixed by
  156. adding locations.
  157. -Include and import file searching now searches for the file name given based
  158. on the location of the current file, not ragel's current path.
  159. Additional search locations can be given using the -I option.
  160. -Rubinius code generation was updated to the latest Rubinius. Patch from Evan
  161. Phoenix.
  162. -Switched from strcasecmp to strcmp for testing long arguments.
  163. -Applied a patch from Andrei Polushin for setting the error message format.
  164. --error-format=gnu (default)
  165. --error-fromat=msvc
  166. -Now using the _WIN32 define instead of _WIN32. Other MSVC compilation
  167. improvments from Andrei Polushin.
  168. -Added the hyperref package to the manual.
  169. Ragel 6.1 - Mar 26, 2008
  170. ========================
  171. -Scanners now ensure that any leaving actions at the end of a pattern are
  172. executed. They are always executed before the pattern action.
  173. -Added an option -d for turning off the removal of duplicate actions from
  174. actions lists.
  175. -Need to unset the final state status of the start state in kleene star if it
  176. is set. It is possible to crash ragel when the warning is ignored.
  177. -In the dot file generation we need to print any actions that are in
  178. State::eofTrans. These come from scanners only.
  179. -Use @docdir@ for the docdir Makefile variable.
  180. -Check for ar and ranlib in the configure script.
  181. Ragel 6.0 - Jan 12, 2008
  182. ========================
  183. -Removed the 'noend' write option from examples/atoi.rl. This example is
  184. referenced a lot as a first example and as such it shouldn't contain a
  185. special purpose write option like 'noend'.
  186. -Introcuded the "eof" variable for indicating the end of file. The p variable
  187. is checked against eof when the processing loop reaches the end of a block.
  188. If p == eof at this time then the EOF actions are executed. The variable is
  189. required only when EOF actions have been emebedded.
  190. -The "write eof" command is no longer needed and was removed.
  191. -Scanners now use EOF actions to generate tokens. This eliminates the need to
  192. flush the last token.
  193. -Restructured the Java driver; a switch statement with fallthrough cases are
  194. now used to emulate gotos.
  195. -Ruby code generation was also restructured. Gotos are elmulated using a
  196. series of if tests.
  197. -Went back to 3.X semantics for >, % and error actions. The > operator also
  198. embeds a leaving action/priority into the start state if it is final. If EOF
  199. happens in a state with a leaving operator then the leaving action is
  200. executed. If EOF happens in a non-final state that has an error action, the
  201. error action is executed.
  202. -The "ragel" program now executes frontend and backend processes separately,
  203. connecting them with a temporary file in the current directory. Without the
  204. -x option the "ragel" program marshals arguments and calls the frontend and
  205. backend. With the -x option the "ragel" program acts as the frontend only.
  206. -Added name finding for executables. If any forward slash is found in argv0
  207. then it is assumed that the path is explicit and the path to the backend
  208. executable should be derived from that. Whe check that location and also go
  209. up one then inside a directory of the same name in case we are executing
  210. from the source tree. If no forward slash is found it is assumed the file is
  211. being run from the installed location. The PREFIX supplied during
  212. configuration is used.
  213. -On windows GetModuleFileNameEx is used to find out where the the current
  214. process's binary is. That location is searched first. If that fails then we
  215. go up one directory and look for the executable inside a directory of the
  216. same name in case we are executing from the source tree.
  217. -Changed the -l option in rlgen-cd to -L because it is covered in the
  218. frontend. Added a passthrough in the frontend for the backend options.
  219. -Dot file generation can now be invoked using the -V option to ragel. We
  220. now require an input file. If standard in is used then we don't have a file
  221. name on which to base the output.
  222. -Able to build native windows executables using Cygwin+MinGW.
  223. -Patch from David Waite: Large arrays are now created by copying in the data
  224. from smaller arrays using System.arraycopy(). This eliminates the debug data
  225. associated with explicit initialization statements. It is also much easier
  226. on the java compiler which can run out of memory compiling very large
  227. machines. The downside is that it takes slightly longer to initialize static
  228. data at run time.
  229. -The fbreak statement now advances p.
  230. -In the :> :>> and <: operators it was possible for the priority assignment
  231. to be bypassed via the zero length string. In :> this was fixed
  232. automatically with the semantics change to the entering priority operator.
  233. If the start state is final it now embeds a leaving action into it,
  234. preventing persistance through the zero length string. In :>> and <: this
  235. was fixed explicitly. With <: the entering priority operator was used and
  236. with :> a special exception was added. Since it uses the finishing
  237. transition operator it also adds a leaving priority to the start state if it
  238. is final.
  239. -Ranlib is now run on the archives. Patch from Kenny MacDermid.
  240. -The case statement syntax in ruby code generation used a form depreciated in
  241. Ruby 1.9. Updated it.
  242. -Made a number of fixes that eliminate warnings in GCC 4.3. Mostly concern
  243. the now depreciate automatic conversion of string contsants to "char*" type.
  244. Other fixes include adding parenthesis around && within ||.
  245. -The "tokstart" and "tokend" variables were changed to "ts" and "te".
  246. Ragel 5.25 - Dec 24, 2007
  247. =========================
  248. -Fixed segfault reported by Ryan Phelps. Affected Java and Ruby code
  249. generation. The dataExpr variable was not initialized.
  250. -Fixed incorrect case label in test/runtests. Caused Objective-C tests to be
  251. ignored.
  252. -Added missing include to common.cpp.
  253. Ragel 5.24 - Sep 16, 2007
  254. =========================
  255. -Applied patch from Victor Hugo Borja <vic@rubyforge.org>. This patch
  256. implements -T1 -F0 -F1 and -G0 in the ruby code generator. Goto-driven code
  257. generation is experimental and requires rubinius asm directives (specify
  258. with --rbx option). These code generators pass all the ruby tests.
  259. -If the condition embedding code runs out of available characters in the
  260. keyspace an error message is emitted.
  261. -The first example that appeared in the manual used the special-purpose
  262. 'noend' write option. This caused confusion. Now a basic example appears
  263. first.
  264. -Added two new statements: prepush and postpop. These are code blocks that
  265. are written out during call and return statements. The prepush code is
  266. written immediately before pushing the current state to the state stack
  267. during a call. The postpop code is written immediately after popping the
  268. current state during return. These can be used to implement a dynamically
  269. resizable stack.
  270. Ragel 5.23 - Jul 24, 2007
  271. =========================
  272. -Eliminated the use of callcc as an alternative to goto. Instead, the named
  273. breaks implementation used in the Java code generator is imitated using
  274. control flow variables.
  275. -Improved the error message given when there is a write statement but no
  276. machine instantiations and hence no state machine.
  277. -Documentation improvements: updates to "Machine Instantiation", "Write Init"
  278. and "Write Exports" sectons. Added the "Variables Used by Ragel" section.
  279. -Renamed "Entering Actions" to "Starting Actions."
  280. -Other documentation updates.
  281. Ragel 5.22 - June 14, 2007
  282. ==========================
  283. -Bug fix: need to isolate the start state of a scanner before setting the
  284. to-state and from-state actions which clear and set tokstart. This affected
  285. very simple scanners only. Most scanners have an isolated start state due to
  286. the pattern structure.
  287. -Bug fix: when -S or -M was given the ragel version number was not emitted,
  288. causing the backend to reject the intermediate format. From Tim Potter.
  289. -The p varialbe is now set up at the beginning of a scanner action, rather
  290. than at the end. This leaves scanner actions free to manipulate p and
  291. removes the need for the special holdTE and execTE (TE for tokend) versions
  292. of hold and exec. It also removes the need to set p = tokend-1 immediately
  293. before any control flow. We loose the ability to determine where in the
  294. input stream a scanner action is executed, however this information is of
  295. little use because it is primarily an artifact of the scanner implementation
  296. (sometimes the last char, other times later on). The gains of this change
  297. are consistency and simplicity.
  298. -The "data" variable (used in Java and Ruby code generation only) can now be
  299. overridden using the variable statement.
  300. Ragel 5.21 - May 9, 2007
  301. ========================
  302. -Fixed an inconsistency in the value of p following an error. In the C
  303. directly executable code (rlgen-cd -G2) p is left at the character where
  304. the error occurred, which is correct. In all other code generators it was
  305. left at the following character. This was fixed. Now in all code generators
  306. p is left at the character where the error occurred.
  307. -Bug fix: when fhold was used in scanner pattern actions which get executed
  308. on the last character of the pattern (pattern matches which do not require
  309. any lookahead), fhold was modifying p instead of tokend. This was fixed and
  310. the patact.rl test was modified to cover the case.
  311. -Fixed typos in the guide, improved the state action embedding operator
  312. section and added subsections on the variable, import, and export
  313. statements.
  314. -Implemented a better solution than the pri hack for resolving the '-'
  315. ambiguity: force a shortest match of term.
  316. -Fixed bugs in the binary searching for condition keys in both the Ruby and
  317. Java code generation.
  318. -Can now embed the negative sense of a condition. Added a language-
  319. independent test case for this feature and the necessary transformation
  320. support.
  321. -Added new condition embedding syntax:
  322. expr inwhen cond - The transitions into the machine (starting transitions).
  323. expr outwhen cond - The pending transitions out of the machine.
  324. -The argument to the variable statement which affects the name of the current
  325. state variable was changed from "curstate" to "cs" (the default name used
  326. for the current state)
  327. -Implemented the other variables names in the variable statement. Now all
  328. variables (p, pe, cs, top, stack, act, tokstart, tokend) can be renamed.
  329. -Parse errors in the intermediate XML file now cause the backend to exit
  330. immediately rather then forge on. The recovery infrastructure isn't there
  331. and segfaults are likely.
  332. -When no input is given to the backend program, it should not print an error
  333. message, it should just return a non-zero exit status. The assumption is
  334. that the frontend printed an error.
  335. -The version number is now included in the intermediate file. An error is
  336. emitted if there is a mismatch.
  337. -The alphabet type is now communicated from the frontend to the backend using
  338. a one-word internal name instead of an array offset.
  339. -The Ruby host language types had been just copied from Java. Reduced them to
  340. two basic types: char and int, both signed with the usual C sizes.
  341. Ragel 5.20 - Apr 7, 2007
  342. ========================
  343. -The cs variable is now always initialized, unless the "nocs" option is given
  344. to the write init command. If there is no main machine, cs is initialized to
  345. the entry point defined by the last machine instantiation.
  346. -A number of fixes were made to the Ruby code generator.
  347. -The frontend now scans ruby comments and regular expressions.
  348. -A transformation for Ruby was added to the language-independent test suite.
  349. The Ruby code generator passes on all the language-independent tests.
  350. -A new Ruby test and two language-independent tests were added.
  351. -Some portability fixes were made (Patches from Josef Goettgens and Aaron
  352. Campbell).
  353. -Fixed a make dependency bug which caused a problem for parallel building
  354. (Patch from Jeremy Hinegardner).
  355. Ragel 5.19 - Mar 14, 2007
  356. =========================
  357. -Added an import statement to ragel. This statement takes a literal string as
  358. an argument, interprets it as a file name, then scrapes the file for
  359. sequences of tokens that match the following forms. Tokens inside ragel
  360. sections are ignored. An example is in test/import1.rl
  361. name = number
  362. name = lit_string
  363. "define" name number
  364. "define" name lit_string
  365. -Added an export mechanism which writes defines for single character machines
  366. that have been tagged with the export keyword in their definition. Defines
  367. are used for C, ints for D, Java and Ruby. Examples of the export feature
  368. are in test/export*.rl.
  369. -All machine instantiations are now always generated, even if they are not
  370. referenced. In the backend, entry points for all instantiations are written
  371. out alongside start, error and first final states.
  372. -If the main machine is not present then do not emit an error. Generate the
  373. machine without a start state and do not initialize cs in the write init
  374. code.
  375. -Added an option -l to rlgen-cd which inhibits the writing of #line
  376. directives.
  377. -Added a new syntax for verbose embeddings. This adds parentheses:
  378. $from(action_name);
  379. Verbose embeddings without parentheses can make code difficult to read
  380. because they force a space in the middle of an action embedding. There is a
  381. tendency to associtate spaces with concatenation. Without syntax
  382. highlighting to make it clear that the embedding type is a keyword, the
  383. problem is especially bad. The danger is that a verbose embedding could be
  384. read as an embedding of the keyword representing the empbedding type. With
  385. parentheses, verbose embeddings read much more clearly.
  386. -Conditions now have a forced order when more than one is executed on a
  387. single character. Previously ordering relied on pointers, which caused
  388. results to vary by compiler. Ordering is now done using conditon action
  389. declaration order. This fixes the failure of cond4.rl which occured with
  390. g++ 4.1 and other compiler versions.
  391. -In the port from flex to ragel, the name separator :: in Ragel code was
  392. lost. Added it back.
  393. -In the examples directory switched from rlcodegen to rlgen-cd. Silenced a
  394. warning in statechart.rl.
  395. -In the root makefile the distclean target was fixed. It was calling clean in
  396. the subdirs. In docs, the clean target was not deleting the new manpages for
  397. the rlgen-* programs. Fixed.
  398. -Portability and other fixes from Josef Goettgens were applied.
  399. -The @datadir@ and @mandir@ variables are made use of in doc/Makefile.in for
  400. specifying where documentation should be installed. Patch from Marcus
  401. Rueckert.
  402. Ragel 5.18 - Feb 13, 2007
  403. =========================
  404. -There is now a 100% correspondence between state id numbers in the
  405. intermediate XML file, Graphviz dot files and generated code. This was
  406. achieved by moving code which determines if the error state is necessary
  407. into the frontend, and then assigning state numbers before writing out the
  408. intermediate file.
  409. -Backened class structure was reorganized to make it easier to add new code
  410. generators without having to also modify the existing code generators.
  411. -The C and D code generation executable was changed to rlgen-cd.
  412. -The Java code generation was split out into it's own exectuable (rlgen-java)
  413. to allow it to freely diverge from the C/D-based code generation.
  414. -The graphviz dot file generation was also split out to it's own executable
  415. (rlgen-dot).
  416. -The Ruby code generation patch from Victor Hugo Borja was added. This is
  417. highly experimental code and is not yet completely functional. It is in the
  418. executable rlgen-ruby.
  419. -The problem with large state machine machines in Java was fixed. This
  420. problem was discovered by Colin Fleming, who also contributed a patch.
  421. Rather than specify arrays as comma-separated lists of literals, array
  422. initialization is now done in a static function. This is the approach used
  423. by the Java compiler. Unlike the compiler Ragel is careful split large
  424. initilization functions.
  425. -The manual was expanded and reorganized somewhat.
  426. -Eliminated per-example directories in examples/.
  427. -Made some fixes to the pullscan.rl example.
  428. -In the frontend CR characters are now treated as whitespace.
  429. -Updated to the latest aapl. This completely eliminates the shallowCopy
  430. function. With that, a definitive memory leak is fixed.
  431. -Control codes with escape sequences are now printable characters (-p
  432. option). Also, the space character is now printed as SP.
  433. -Fixed the null dereference and consequential segfault which occurred when
  434. trying to create empty machines with [] and // and /a[]b/.
  435. -Fixed the segfault which occured when a machine reference failed.
  436. -Discontinuing ragel.spec. It is more appropriate for this to be written by
  437. package maintenance developers.
  438. Ragel 5.17 - Jan 28, 2007
  439. =========================
  440. -The scanners and parsers in both the frontend and backend programs were
  441. completely rewritten using Ragel and Kelbt.
  442. -The '%when condition' syntax was functioning like '$when condition'. This
  443. was fixed.
  444. -In the Vim syntax file fixes to the matching of embedding operators were
  445. made. Also, improvements to the sync patterns were made.
  446. -Added pullscan.rl to the examples directory. It is an example of doing
  447. pull-based scanning. Also, xmlscan.rl in rlcodegen is a pull scanner.
  448. -The introduction chapter of the manual was improved. The manually-drawn
  449. figures for the examples were replaced with graphviz-drawn figures.
  450. Ragel 5.16 - Nov 20, 2006
  451. =========================
  452. -Policy change: the fhold and fexec directives did not function correctly in
  453. scanner pattern actions. In this context manipulations of p may be lost or
  454. made invalid. In the previous version of Ragel they were banned because of
  455. this. Instead of banning these directives they have been fixed. The fexec
  456. and fhold directives now manipulate tokend, which is now always used to
  457. update p when the action terminates.
  458. Ragel 5.15 - Oct 31, 2006
  459. =========================
  460. -A language independent test harness was introduced. Test cases can be
  461. written using a custom mini-language in the embedded actions. This
  462. mini-language is then translated to C, D and Java when generating the
  463. language-specific test cases.
  464. -Several existing tests have been ported to the language-independent format
  465. and a number of new language-independent test cases have been added.
  466. -The state-based embedding operators which access states that are not the
  467. start state and are not final (the 'middle' states) have changed. They
  468. were:
  469. <@/ eof action into middle states
  470. <@! error action into middle states
  471. <@^ local error action into middle states
  472. <@~ to-state action into middle states
  473. <@* from-state action into middle states
  474. They are now:
  475. <>/ eof action into middle states
  476. <>! error action into middle states
  477. <>^ local error action into middle states
  478. <>~ to-state action into middle states
  479. <>* from-state action into middle states
  480. -The verbose form of embeddings using the <- operator have been removed.
  481. This syntax was difficult to remember.
  482. -A new verbose form of state-based embedding operators have been added.
  483. These are like the symbol versions, except they replace the symbols:
  484. / ! ^ ~ *
  485. with literal keywords:
  486. eof err lerr to from
  487. -The following words have been promoted to keywords:
  488. when eof err lerr to from
  489. -The write statment now gets its own lexical scope in the scanner to ensure
  490. that commands are passed through as is (not affected by keywords).
  491. -Bug fix: in the code generation of fret in scanner actions the adjustment to
  492. p that is needed in some cases (dependent on content of patterns) was not
  493. happening.
  494. -The fhold directive, which decrements p, cannot be permitted in the pattern
  495. action of a scanner item because it will not behave consistently. At the end
  496. of a pattern action p could be decremented, set to a new value or left
  497. alone. This depends on the contents of the scanner's patterns. The user
  498. cannot be expected to predict what will happen to p.
  499. -Conditions in D code require a cast to the widec type when computing widec.
  500. -Like Java, D code also needs if (true) branches for control flow in actions
  501. in order to fool the unreachable code detector. This is now abstracted in
  502. all code generators using the CTRL_FLOW() function.
  503. -The NULL_ITEM value in java code should be -1. This is needed for
  504. maintaining tokstart.
  505. Ragel 5.14 - Oct 1, 2006
  506. ========================
  507. -Fixed the check for use of fcall in actions embedded within longest match
  508. items. It was emitting an error if an item's longest-match action had an
  509. fcall, which is allowed. This bug was introduced while fixing a segfault in
  510. version 5.8.
  511. -A new minimization option was added: MinimizeMostOps (-l). This option
  512. minimizes at every operation except on chains of expressions and chains of
  513. terms (eg, union and concat). On these chains it minimizes only at the last
  514. operation. This makes test cases with many states compile faster, without
  515. killing the performance on grammars like strings2.rl.
  516. -The -l minimiziation option was made the default.
  517. -Fixes to Java code: Use of the fc value did not work, now fixed. Static data
  518. is now declared with the final keyword. Patch from Colin Fleming. Conditions
  519. now work when generating Java code.
  520. -The option -p was added to rlcodegen which causes printable characters to be
  521. printed in GraphViz output. Patch from Colin Fleming.
  522. -The "element" keyword no longer exists, removed from vim syntax file.
  523. Updated keyword highlighting.
  524. -The host language selection is now made in the frontend.
  525. -Native host language types are now used when specifying the alphtype.
  526. Previously all languages used the set defined by C, and these were mapped to
  527. the appropriate type in the backend.
  528. Ragel 5.13 - Sep 7, 2006
  529. ========================
  530. -Fixed a careless error which broke Java code generation.
  531. Ragel 5.12 - Sep 7, 2006
  532. ========================
  533. -The -o flag did not work in combination with -V. This was fixed.
  534. -The split code generation format uses only the required number of digits
  535. when writing out the number in the file name of each part.
  536. -The -T0, -F0 and -G0 codegens should write out the action list iteration
  537. variables only when there are regular, to state or from state actions. The
  538. code gens should not use anyActions().
  539. -If two states have the same EOF actions, they are written out in the finish
  540. routine as one case.
  541. -The split and in-place goto formats would sometimes generate _out when it is
  542. not needed. This was fixed.
  543. -Improved the basic partitioning in the split code gen. The last partition
  544. would sometimes be empty. This was fixed.
  545. -Use of 'fcall *' was not causing top to be initialized. Fixed.
  546. -Implemented a Java backend, specified with -J. Only the table-based format
  547. is supported.
  548. -Implemented range compression in the frontend. This has no effect on the
  549. generated code, however it reduces the work of the backend and any programs
  550. that read the intermediate format.
  551. Ragel 5.11 - Aug 10, 2006
  552. =========================
  553. -Added a variable to the configure.in script which allows the building of
  554. the parsers to be turned off (BUILD_PARSERS). Parser building is off by
  555. default for released versions.
  556. -Removed configure tests for bison defines header file. Use --defines=file
  557. instead.
  558. -Configure script doesn't test for bison, flex and gperf when building of the
  559. parsers is turned off.
  560. -Removed check for YYLTYPE structure from configure script. Since shipped
  561. code will not build parsers by default, we don't need to be as accomodating
  562. of other versions of bison.
  563. -Added a missing include that showed up with g++ 2.95.3.
  564. -Failed configure test for Objective-C compiler is now silent.
  565. Ragel 5.10 - Jul 31, 2006
  566. =========================
  567. -Moved the check for error state higher in the table-based processing loop.
  568. -Replaced naive implementations of condition searching with proper ones. In
  569. the table-based formats the searching is also table-based. In the directly
  570. executed formats the searching is also directly executable.
  571. -The minimization process was made aware of conditions.
  572. -A problem with the condition implementation was fixed. Previously we were
  573. taking pointers to transitions and then using them after a call to
  574. outTransCopy, which was a bad idea because they may be changed by the call.
  575. -Added test mailbox3.rl which is based on mailbox2.rl but includes conditions
  576. for restricting header and message body lengths.
  577. -Eliminated the initial one-character backup of p just before resuming
  578. execution.
  579. -Added the -s option to the frontend for printing statistics. This currently
  580. includes just the number of states.
  581. -Sped up the generation of the in-place goto-driven (-G2) code style.
  582. -Implemented a split version of in-place goto-driven code style. This code
  583. generation style is suitable for producing fast implementations of very
  584. large machines. Partitioning is currently naive. In the future a
  585. high-quality partitioning program will be employed. The flag for accessing
  586. this feature is -Pn, where n is the number of partitions.
  587. -Converted mailbox1.rl, strings2.rl and cppscan1.rl tests to support the
  588. split code generation.
  589. -Fixes and updates were made to the runtests script: added -c for compiling
  590. only, changed the -me option to -e, and added support for testing the split
  591. code style.
  592. Ragel 5.9 - Jul 19, 2006
  593. ========================
  594. -Fixed a bug in the include system which caused malformed output from the
  595. frontend when the include was made from a multi-line machine spec and the
  596. included file ended in a single line spec (or vice versa).
  597. -Static data is now const.
  598. -Actions which referenced states but were not embedded caused the frontend to
  599. segfault, now fixed.
  600. -Manual now built with pdflatex.
  601. -The manual was reorganized and expanded. Chapter sequence is now:
  602. Introduction, Constructing Machines, Embedding Actions, Controlling
  603. Nondeterminism and Interfacing to the Host program.
  604. Ragel 5.8 - Jun 17, 2006
  605. ========================
  606. -The internal representation of the alphabet type has been encapsulated
  607. into a class and all operations on it have been defined as C++ operators.
  608. -The condition implementation now supports range transitions. This allows
  609. conditions to be embedded into arbitrary machines. Conditions are still
  610. exprimental.
  611. -More condition embedding operators were added
  612. 1. Isolate the start state and embed a condition into all transitions
  613. leaving it:
  614. >when cond OR >?cond
  615. 2. Embed a condition into all transitions:
  616. when cond OR $when cond OR $?cond
  617. 3. Embed a condition into pending out transitions:
  618. %when cond OR %?cond
  619. -Improvements were made to the determinization process to support pending out
  620. conditions.
  621. -The Vim sytax file was fixed so that :> doesn't cause the match of a label.
  622. -The test suite was converted to a single-file format which uses less disk
  623. space than the old directory-per-test format.
  624. Ragel 5.7 - May 14, 2006
  625. ========================
  626. -Conditions will not be embedded like actions because they involve a
  627. manipulation of the state machine they are specified in. They have therefore
  628. been taken out of the verbose action embedding form (using the <- compound
  629. symbol). A new syntax for specifying conditions has been created:
  630. m = '\n' when {i==4};
  631. -Fixed a bug which prevented state machine commands like fcurs, fcall, fret,
  632. etc, from being accounted for in from-state actions and to-state actions.
  633. This prevented some necessary support code from being generated.
  634. -Implemented condition testing in remaining code generators.
  635. -Configure script now checks for gperf, which is required for building.
  636. -Added support for case-insensitive literal strings (in addition to regexes).
  637. A case-insensitive string is made by appending an 'i' to the literal, as in
  638. 'cmd'i or "cmd"i.
  639. -Fixed a bug which caused all or expressions inside of all regular
  640. expressions to be case-insensitive. For example /[fo]o bar/ would make the
  641. [fo] part case-insensitive even though no 'i' was given following the
  642. regular expression.
  643. Ragel 5.6 - Apr 1, 2006
  644. =======================
  645. -Added a left-guarded concatenation operator. This operator <: is equivalent
  646. to ( expr1 $1 . expr2 >0 ). It is useful if you want to prefix a sequence
  647. with a sequence of a subset of the characters it matches. For example, one
  648. can consume leading whitespace before tokenizing a sequence of whitespace
  649. separated words: ( ' '* <: ( ' '+ | [a-z]+ )** )
  650. -Removed context embedding code, which has been dead since 5.0.
  651. Ragel 5.5 - Mar 28, 2006
  652. ========================
  653. -Implemented a case-insensitive option for regular expressions: /get/i.
  654. -If no input file is given to the ragel program it reads from standard input.
  655. -The label of the start state has been changed from START to IN to save on
  656. required screen space.
  657. -Bug fix: \0 was not working in literal strings, due to a change that reduced
  658. memory usage by concatenating components of literal strings. Token data
  659. length is now passed from the scanner to the paser so that we do not need to
  660. rely on null termination.
  661. Ragel 5.4 - Mar 12, 2006
  662. ========================
  663. -Eliminated the default transition from the frontend implementation. This
  664. default transition was a space-saving optimization that at best could reduce
  665. the number of allocated transitions by one half. Unfortunately it
  666. complicated the implementation and this stood in the way of introducing
  667. conditionals. The default transition may be reintroduced in the future.
  668. -Added entry-guarded concatenation. This operator :>, is syntactic sugar
  669. for expr1 $0 . expr >1. This operator terminates the matching of the first
  670. machine when a first character of the second machine is matched. For
  671. example in any* . ';' we never leave the any* machine. If we use any* :> ';'
  672. then the any* machine is terminiated upon matching the semi-colon.
  673. -Added finish-guarded concatenation. This operator :>>, is syntactic sugar
  674. for expr1 $0 . expr @1. This operator is like entry guarded concatenation
  675. except the first machine is terminated when the second machine enters a
  676. final state. This is useful for delaying the guard until a full pattern is
  677. matched. For example as in '/*' any* :>> '*/'.
  678. -Added strong subtraction. Where regular subtraction removes from the first
  679. machine any strings that are matched by the second machine, strong
  680. subtraction removes any strings from the first that contain any strings of
  681. the second as a substring. Strong subtraction is syntactic sugar for
  682. expr1 - ( any* expr2 any* ).
  683. -Eliminated the use of priorities from the examples. Replaced with
  684. subtraction, guarded concatenation and longest-match kleene star.
  685. -Did some initial work on supporting conditional transitions. Far from
  686. complete and very buggy. This code will only be active when conditionals are
  687. used.
  688. Ragel 5.3 - Jan 27, 2006
  689. ========================
  690. -Added missing semi-colons that cause the build to fail when using older
  691. versions of Bison.
  692. -Fix for D code: if the contents of an fexec is a single word, the generated
  693. code will get interpreted as a C-style cast. Adding two brackets prevents
  694. this. Can now turn eliminate the "access this.;" in cppscan5 that was used to
  695. get around this problem.
  696. -Improved some of the tag names in the intermediate format.
  697. -Added unsigned long to the list of supported alphabet types.
  698. -Added ids of actions and action lists to XML intermediate format. Makes it
  699. more human readable.
  700. -Updated to latest Aapl package.
  701. Ragel 5.2 - Jan 6, 2006
  702. ========================
  703. -Ragel emits an error if the target of fentry, fcall, fgoto or fnext is inside
  704. a longest match operator, or if an action embedding in a longest match
  705. machine uses fcall. The fcall command can still be used in pattern actions.
  706. -Made improvements to the clang, rlscan, awkemu and cppscan examples.
  707. -Some fixes to generated label names: they should all be prefixed with _.
  708. -A fix to the Vim syntax highlighting script was made
  709. -Many fixes and updates to the documentation. All important features and
  710. concepts are now documented. A second chapter describing Ragel's use
  711. was added.
  712. Ragel 5.1 - Dec 22, 2005
  713. ========================
  714. -Fixes to the matching of section delimiters in Vim syntax file.
  715. -If there is a longest match machine, the tokend var is now initialized by
  716. write init. This is not necessary for correct functionality, however
  717. prevents compiler warnings.
  718. -The rlscan example was ported to the longest match operator and changed to
  719. emit XML data.
  720. -Fix to the error handling in the frontend: if there are errors in the lookup
  721. of names at machine generation time then do not emit anything.
  722. -If not compiling the full machine in the frontend (by using -M), avoid
  723. errors and segfaults caused by names that are not part of the compiled
  724. machine.
  725. -Longest match bug fix: need to init tokstart when returing from fsm calls
  726. that are inside longest match actions.
  727. -In Graphviz drawing, the arrow into the start state is not a real
  728. transition, do not draw to-state actions on the label.
  729. -A bug fix to the handling of non-tag data within an XML tag was made.
  730. -Backend exit value fixed: since the parser now accepts nothing so as to
  731. avoid a redundant parse error when the frontend dies, we must force an
  732. error. The backend should now be properly reporting errors.
  733. -The longest match machine now has it's start state set final. An LM machine
  734. is in a final state when it has not matched anything, when it has matched
  735. and accepted a token and is ready for another, and when it has matched a
  736. token but is waiting for some lookahead before determining what to do about
  737. it (similar to kleene star).
  738. -Element statement removed from some tests.
  739. -Entry point names are propagated to the backend and used to label the entry
  740. point arrows in Graphviz output.
  741. Ragel 5.0 - Dec 17, 2005
  742. ========================
  743. (additional details in V5 release notes)
  744. -Ragel has been split into two executables: A frontend which compiles
  745. machines and emits them in an XML format, and a backend which generates code
  746. or a Graphviz dot file from the XML input. The purpose of this split is to
  747. allow Ragel to interface with other tools by means of the XML intermediate
  748. format and to reduce complexity by strictly separating the previously
  749. entangled phases. The intermediate format will provide a better platform
  750. inspecting compiled machines and for extending Ragel to support other host
  751. languages.
  752. -The host language interface has been reduced significantly. Ragel no longer
  753. expects the machine to be implemented as a structure or class and does not
  754. generate functions corresponding to initialization, execution and EOF.
  755. Instead, Ragel just generates the code of these components, allowing all of
  756. them to be placed in a single function if desired. The user specifies a
  757. machine in the usual manner, then indicates at which place in the program
  758. text the state machine code is to be generated. This is done using the write
  759. statement. It is possible to specify to Ragel how it should access the
  760. variables it needs (such as the current state) using the access statement.
  761. -The host language embedding delimiters have been changed. Single line
  762. machines start with '%%' and end at newline. Multiline machines start with
  763. '%%{' and end with '}%%'. The machine name is given with the machine
  764. statement at the very beginning of the specification. This purpose of this
  765. change is to make it easier separate Ragel code from the host language. This
  766. will ease the addition of supported host languages.
  767. -The structure and class parsing which was previously able to extract a
  768. machine's name has been removed since this feature is dependent on the host
  769. language and inhibits the move towards a more language-independent frontend.
  770. -The init, element and interface statements have been made obsolete by the
  771. new host language interface and have been removed.
  772. -The fexec action statement has been changed to take only the new position to
  773. move to. This statement is more useful for moving backwards and reparsing
  774. input than for specifying a whole new buffer entirely and has been shifted
  775. to this new use. Giving it only one argument also simplifies the parsing of
  776. host code embedded in a Ragel specification. This will ease the addition of
  777. supported host languages.
  778. -Introduced the fbreak statement, which allows one to stop processing data
  779. immediately. The machine ends up in the state that the current transition
  780. was to go to. The current character is not changed.
  781. -Introduced the noend option for writing the execute code. This inhibits
  782. checking if we have reached pe. The machine will run until it goes into the
  783. error state or fbreak is hit. This allows one to parse null-terminate
  784. strings without first computing the length.
  785. -The execute code now breaks out of the processing loop when it moves into
  786. the error state. Previously it would run until pe was hit. Breaking out
  787. makes the noend option useful when an error is encountered and allows
  788. user code to determine where in the input the error occured. It also
  789. eliminates needlessly iterating the input buffer.
  790. -Introduced the noerror, nofinal and noprefix options for writing the machine
  791. data. The first two inhibit the writing of the error state and the
  792. first-final state should they not be needed. The noprefix eliminates the
  793. prefixing of the data items with the machine name.
  794. -Support for the D language has been added. This is specified in the backend
  795. with the -D switch.
  796. -Since the new host language interface has been reduced considerably, Ragel
  797. no longer needs to distinguish between C-based languages. Support for C, C++
  798. and Objective-C has been folded into one option in the backend: -C
  799. -The code generator has been made independent of the languages that it
  800. supports by pushing the language dependent apsects down into the lower
  801. levels of the code generator.
  802. -Many improvements to the longest match construction were made. It is no
  803. longer considered experimental. A longest match machine must appear at the
  804. top level of a machine instantiation. Since it does not generate a pure
  805. state machine (it may need to backtrack), it cannot be used as an operand to
  806. other operators.
  807. -References to the current character and current state are now completely
  808. banned in EOF actions.
  809. Ragel 4.2 - Sep 16, 2005
  810. ========================
  811. (additional details in V4 release notes)
  812. -Fixed a bug in the longest match operator. In some states it's possible that
  813. we either match a token or match nothing at all. In these states we need to
  814. consult the LmSwitch on error so it must be prepared to execute an error
  815. handler. We therefore need to init act to this error value (which is zero).
  816. We can compute if we need to do this and the code generator emits the
  817. initialization only if necessary.
  818. -Changed the definition of the token end of longest match actions. It now
  819. points to one past the last token. This makes computing the token length
  820. easier because you don't have to add one. The longest match variables token
  821. start, action identifier and token end are now properly initialized in
  822. generated code. They don't need to be initialized in the user's code.
  823. -Implemented to-state and from-state actions. These actions are executed on
  824. transitions into the state (after the in transition's actions) and on
  825. transitions out of the state (before the out transition's actions). See V4
  826. release notes for more information.
  827. -Since there are no longer any action embedding operators that embed both on
  828. transitions and on EOF, any actions that exist in both places will be there
  829. because the user has explicitly done so. Presuming this case is rare, and
  830. with code duplication in the hands of the user, we therefore give the EOF
  831. actions their own action switch in the finish() function. This is further
  832. motivated by the fact that the best solution is to do the same for to-state
  833. and from-state actions in the main loop.
  834. -Longest match actions can now be specified using a named action. Since a
  835. word following a longest match item conflicts with the concatenation of a
  836. named machine, the => symbol must come immediately before a named action.
  837. -The longest match operator permits action and machine definitions in the
  838. middle of a longest match construction. These are parsed as if they came
  839. before the machine definition they are contained in. Permitting action and
  840. machine definitions in a longest match construction allows objects to be
  841. defined closer to their use.
  842. -The longest match operator can now handle longest match items with no
  843. action, where previously Ragel segfaulted.
  844. -Updated to Aapl post 2.12.
  845. -Fixed a bug in epsilon transition name lookups. After doing a name lookup
  846. the result was stored in the parse tree. This is wrong because if a machine
  847. is used more than once, each time it may resolve to different targets,
  848. however it will be stored in the same place. We now store name resolutions
  849. in a separated data structure so that each walk of a parse tree uses the
  850. name resolved during the corresponding walk in the name lookup pass.
  851. -The operators used to embed context and actions into states have been
  852. modified. The V4 release notes contain the full details.
  853. -Added zlen builtin machine to represent the zero length machine. Eventually
  854. the name "null" will be phased out in favour of zlen because it is unclear
  855. whether null matches the zero length string or if it does not match any
  856. string at all (as does the empty builtin).
  857. -Added verbose versions of action, context and priority embedding. See the V4
  858. release notes for the full details. A small example:
  859. machine <- all exec { foo(); } <- final eof act1
  860. -Bugfix for machines with epsilon ops, but no join operations. I had
  861. wrongfully assumed that because epsilon ops can only increase connectivity,
  862. that no states are ever merged and therefore a call to fillInStates() is not
  863. necessary. In reality, epsilon transitions within one machine can induce the
  864. merging of states. In the following, state 2 follows two paths on 'i':
  865. main := 'h' -> i 'i h' i: 'i';
  866. -Changed the license of the guide from a custom "do not propagate modified
  867. versions of this document" license to the GPL.
  868. Ragel 4.1 - Jun 26, 2005
  869. ========================
  870. (additional details in V4 release notes)
  871. -A bug in include processing was fixed. Surrounding code in an include file
  872. was being passed through to the output when it should be ignored. Includes
  873. are only for including portions of another machine into he current. This
  874. went unnoticed because all tested includes were wrapped in #ifndef ...
  875. #endif directives and so did not affect the compilation of the file making
  876. the include.
  877. -Fixes were made to Vim syntax highlighting file.
  878. -Duplicate actions are now removed from action lists.
  879. -The character-level negation operator ^ was added. This operator produces a
  880. machine that matches single characters that are not matched by the machine
  881. it is applied to. This unary prefix operator has the same precedence level
  882. as !.
  883. -The use of + to specify the a positive literal number was discontinued.
  884. -The parser now assigns the subtraction operator a higher precedence than
  885. the negation of literal number.
  886. Ragel 4.0 - May 26, 2005
  887. ========================
  888. (additional details in V4 release notes)
  889. -Operators now strictly embed into a machine either on a specific class of
  890. characters or on EOF, but never both. This gives a cleaner association
  891. between the operators and the physical state machine entitites they operate
  892. on. This change is made up of several parts:
  893. 1. '%' operator embeds only into leaving characters.
  894. 2. All global and local error operators only embed on error character
  895. transitions, their action will not be triggerend on EOF in non-final
  896. states.
  897. 3. EOF action embedding operators have been added for all classes of states
  898. to make up for functionality removed from other operators. These are
  899. >/ $/ @/ %/.
  900. 4. Start transition operator '>' no longer implicitly embeds into leaving
  901. transtions when start state is final.
  902. -Ragel now emits warnings about the improper use of statements and values in
  903. action code that is embedded as an EOF action. Warnings are emitted for fpc,
  904. fc, fexec, fbuf and fblen.
  905. -Added a longest match construction operator |* machine opt-action; ... *|.
  906. This is for repetition where an ability to revert to a shorter, previously
  907. matched item is required. This is the same behaviour as flex and re2c. The
  908. longest match operator is not a pure FSM construction, it introduces
  909. transitions that implicitly hold the current character or reset execution to
  910. a previous location in the input. Use of this operator requires the caller
  911. of the machine to occasionally hold onto data after a call to the exectute
  912. routine. Use of machines generated with this operator as the input to other
  913. operators may have undefined results. See examples/cppscan for an example.
  914. This is very experimental code.
  915. -Action ids are only assigned to actions that are referenced in the final
  916. constructed machine, preventing gaps in the action id sequence. Previously
  917. an action id was assigned if the action was referenced during parsing.
  918. -Machine specifications now begin with %% and are followed with an optional
  919. name and either a single Ragel statement or a sequence of statements
  920. enclosed in {}.
  921. -Ragel no longer generates the FSM's structure or class. It is up to the user
  922. to declare the structure and to give it a variable named curs of type
  923. integer. If the machine uses the call stack the user must also declare a
  924. array of integers named stack and an integer variable named top.
  925. -In the case of Objective-C, Ragel no longer generates the interface or
  926. implementation directives, allowing the user to declare additional methods.
  927. -If a machine specification does not have a name then Ragel tries to find a
  928. name for it by first checking if the specification is inside a struct, class
  929. or interface. If it is not then it uses the name of the previous machine
  930. specification. If still no name is found then this is an error.
  931. -Fsm specifications now persist in memory and statements accumulate.
  932. -Ragel now has an include statement for including the statements of a machine
  933. spec in another file (perhaps because it is the corresponding header file).
  934. The include statement can also be used to draw in the statements of another
  935. fsm spec in the current file.
  936. -The fstack statement is now obsolete and has been removed.
  937. -A new statement, simply 'interface;', indicates that ragel should generate
  938. the machine's interface. If Ragel sees the main machine it generates the
  939. code sections of the machine. Previously, the header portion was generated
  940. if the (now removed) struct statement was found and code was generated if
  941. any machine definition was found.
  942. -Fixed a bug in the resolution of fsm name references in actions. The name
  943. resolution code did not recurse into inline code items with children
  944. (fgoto*, fcall*, fnext*, and fexec), causing a segfault at code generation
  945. time.
  946. -Cleaned up the code generators. FsmCodeGen was made into a virtual base
  947. class allowing for the language/output-style specific classes to inherit
  948. both a language specific and style-specific base class while retaining only
  949. one copy of FsmCodeGen. Language specific output can now be moved into the
  950. language specific code generators, requiring less duplication of code in the
  951. language/output-style specific leaf classes.
  952. -Fixed bugs in fcall* implementation of IpgGoto code generation.
  953. -If the element type has not been defined Ragel now uses a constant version
  954. of the alphtype, not the exact alphtype. In most cases the data pointer of
  955. the execute routine should be const. A non-const element type can still be
  956. defined with the element statement.
  957. -The fc special value now uses getkey for retrieving the current char rather
  958. than *_p, which is wrong if the element type is a structure.
  959. -User guide converted to TeX and updated for new 4.0 syntax and semantics.
  960. Ragel 3.7 - Oct 31, 2004
  961. ========================
  962. -Bug fix: unreferenced machine instantiations causing segfault due to name
  963. tree and parse tree walk becomming out of syncronization.
  964. -Rewrote representation of inline code blocks using a tree data structure.
  965. This allows special keywords such as fbuf to be used as the operatands of
  966. other fsm commands.
  967. -Documentation updates.
  968. -When deciding whether or not to generate machine instantiations, search the
  969. entire name tree beneath the instantiation for references, not just the
  970. root.
  971. -Removed stray ';' in keller2.rl
  972. -Added fexec for restarting the machine with new buffer data (state stays the
  973. same), fbuf for retrieving the the start of the buf, and fblen for
  974. retrieving the orig buffer length.
  975. -Implemented test/cppscan2 using fexec. This allows token emitting and restart
  976. to stay inside the execute routine, instead of leaving and re-entering on
  977. every token.
  978. -Changed examples/cppscan to use fexec and thereby go much faster.
  979. -Implemented flex and re2c versions of examples/cppscan. Ragel version
  980. goes faster than flex version but not as fast as re2c version.
  981. -Merged in Objective-C patch from Erich Ocean.
  982. -Turned off syncing with stdio in C++ tests to make them go faster.
  983. -Renamed C++ code generaion classes with the Cpp Prefix instead of CC to make
  984. them easier to read.
  985. -In the finish function emit fbuf as 0 cast to a pointer to the element type
  986. so it's type is not interpreted as an integer.
  987. -The number -128 underflows char alphabets on some architectures. Removed
  988. uses of it in tests.
  989. -Disabled the keller2 test because it causes problems on many architectures
  990. due to its large size and compilation requirements.
  991. Ragel 3.6 - Jul 10, 2004
  992. ========================
  993. -Many documentation updates.
  994. -When resolving names, return a set of values so that a reference in an
  995. action block that is embedded more than once won't report distinct entry
  996. points that are actually the same.
  997. -Implemented flat tables. Stores a linear array of indicies into the
  998. transition array and only a low and high key value. Faster than binary
  999. searching for keys but not usable for large alphabets.
  1000. -Fixed bug in deleting of transitions leftover from converstion from bst to
  1001. list implementation of transitions. Other code cleanup.
  1002. -In table based output calculate the cost of using an index. Don't use if
  1003. cheaper.
  1004. -Changed fstate() value available in init and action code to to fentry() to
  1005. reflect the fact that the values returned are intended to be used as targets
  1006. in fgoto, fnext and fcall statements. The returned state is not a unique
  1007. state representing the label. There can be any number of states representing
  1008. a label.
  1009. -Added keller2 test, C++ scanning tests and C++ scanning example.
  1010. -In table based output split up transitions into targets and actions. This
  1011. allows actions to be omitted.
  1012. -Broke the components of the state array into separate arrays. Requires
  1013. adding some fields where they could previously be omitted, however allows
  1014. finer grained control over the sizes of items and an overal size reduction.
  1015. Also means that state numbers are not an offset into the state array but
  1016. instead a sequence of numbers, meaning the context array does not have any
  1017. wasted bits.
  1018. -Action lists and transition also have their types chosen to be the smallest
  1019. possible for accomodating the contained values.
  1020. -Changed curs state stored in fsm struct from _cs to curs. Keep fsm->curs ==
  1021. -1 while in machine. Added tests curs1 and curs2.
  1022. -Implemented the notion of context. Context can be embedded in states using
  1023. >:, $:, @: and %: operators. These embed a named context into start states,
  1024. all states, non-start/non-final and final states. If the context is declared
  1025. using a context statment
  1026. context name;
  1027. then the context can be quered for any state using fsm_name_ctx_name(state)
  1028. in C code and fsm_name::ctx_name(state) in C++ code. This feature makes it
  1029. possible to determine what "part" of the machine is currently active.
  1030. -Fixed crash on machine generation of graphs with no final state. If there
  1031. is no reference to a final state in a join operation, don't generate one.
  1032. -Updated Vim sytax: added labels to inline code, added various C++ keywords.
  1033. Don't highlight name separations as labels. Added switch labels, improved
  1034. alphtype, element and getkey.
  1035. -Fixed line info in error reporting of bad epsilon trans.
  1036. -Fixed fstate() for tab code gen.
  1037. -Removed references to malloc.h.
  1038. Ragel 3.5 - May 29, 2004
  1039. ========================
  1040. -When parse errors occur, the partially generated output file is deleted and
  1041. an non-zero exit status is returned.
  1042. -Updated Vim syntax file.
  1043. -Implemented the setting of the element type that is passed to the execute
  1044. routine as well as method for specifying how ragel should retrive the key
  1045. from the element type. This lets ragel process arbitrary structures inside
  1046. of which is the key that is parsed.
  1047. element struct Element;
  1048. getkey fpc->character;
  1049. -The current state is now implemented with an int across all machines. This
  1050. simplifies working with current state variables. For example this allows a
  1051. call stack to be implemented in user code.
  1052. -Implemented a method for retrieving the current state, the target state, and
  1053. any named states.
  1054. fcurs -retrieve the current state
  1055. ftargs -retrieve the target state
  1056. fstate(name) -retrieve a named state.
  1057. -Implemented a mechanism for jumping to and calling to a state stored in a
  1058. variable.
  1059. fgoto *<expr>; -goto the state returned by the C/C++ expression.
  1060. fcall *<expr>; -call the state returned by the C/C++ expression.
  1061. -Implemented a mechanism for specifying the next state without immediately
  1062. transfering control there (any code following statement is executed).
  1063. fnext label; -set the state pointed to by label as the next state.
  1064. fnext *<expr>; -set the state returned by the C/C++ expression as the
  1065. next.
  1066. -Action references are determined from the final machine instead of during
  1067. the parse tree walk. Some actions can be referenced in the parse tree but not
  1068. show up in the final machine. Machine analysis is now done based on this new
  1069. computation.
  1070. -Named state lookup now employs a breadth-first search in the lookup and
  1071. allows the user to fully qualify names, making it possible to specify
  1072. jumps/calls into parts of the machine deep in the name hierarchy. Each part
  1073. of name (separated by ::) employs a breadth first search from it's starting
  1074. point.
  1075. -Name references now must always refer to a single state. Since references to
  1076. multiple states is not normally intended, it no longer happens
  1077. automatically. This frees the programmer from thinking about whether or not
  1078. a state reference is unique. It also avoids the added complexity of
  1079. determining when to merge the targets of multiple references. The effect of
  1080. references to multiple states can be explicitly created using the join
  1081. operator and epsilon transitions.
  1082. -M option was split into -S and -M. -S specifies the machine spec to generate
  1083. for graphviz output and dumping. -M specifies the machine definition or
  1084. instantiation.
  1085. -Machine function parameters are now prefixed with and underscore to
  1086. avoid the hiding of class members.
  1087. Ragel 3.4 - May 8, 2004
  1088. =======================
  1089. -Added the longest match kleene star operator **, which is synonymous
  1090. with ( ( <machine> ) $0 %1 ) *.
  1091. -Epsilon operators distinguish between leaving transitions (going to an
  1092. another expression in a comma separated list) and non-leaving transitions.
  1093. Leaving actions and priorities are appropriately transferred.
  1094. -Relative priority of following ops changed to:
  1095. 1. Action/Priority
  1096. 2. Epsilon
  1097. 3. Label
  1098. If label is done first then the isolation of the start state in > operators
  1099. will cause the label to point to the old start state that doesn't have the
  1100. new action/priority.
  1101. -Merged >! and >~, @! and @~, %! and %~, and $! and $~ operators to have one
  1102. set of global error action operators (>!, @!, %! and $!) that are invoked on
  1103. error by unexpected characters as well as by unexepected EOF.
  1104. -Added the fpc keyword for use in action code. This is a pointer to the
  1105. current character. *fpc == fc. If an action is invoked on EOF then fpc == 0.
  1106. -Added >^, @^, %^, and $^ local error operators. Global error operators (>!,
  1107. @!, $!, and %!) cause actions to be invoked if the final machine fails.
  1108. Local error actions cause actions to be invoked if if the current machine
  1109. fails.
  1110. -Changed error operators to mean embed global/local error actions in:
  1111. >! and !^ -the start state.
  1112. @! and @^ -states that are not the start state and are not final.
  1113. %! and %^ -final states.
  1114. $! and $^ -all states.
  1115. -Added >@! which is synonymous >! then @!
  1116. -Added >@^ which is synonymous >^ then @^
  1117. -Added @%! which is synonymous @! then %!
  1118. -Added @%^ which is synonymous >^ then @^
  1119. -FsmGraph representation of transition lists was changed from a mapping of
  1120. alphabet key -> transition objects using a BST to simply a list of
  1121. transition objects. Since the transitions are no longer divided by
  1122. single/range, the fast finding of transition objects by key is no longer
  1123. required functionality and can be eliminated. This new implementation uses
  1124. the same amount of memory however causes less allocations. It also make more
  1125. sense for supporting error transitions with actions. Previously an error
  1126. transition was represented by a null value in the BST.
  1127. -Regular expression ranges are checked to ensure that lower <= upper.
  1128. -Added printf-like example.
  1129. -Added atoi2, erract2, and gotcallret to the test suite.
  1130. -Improved build test to support make -jN and simplified the compiling and
  1131. running of tests.
  1132. Ragel 3.3 - Mar 7, 2004
  1133. =======================
  1134. -Portability bug fixes were made. Minimum and maximum integer values are
  1135. now taken from the system. An alignment problem on 64bit systems
  1136. was fixed.
  1137. Ragel 3.2 - Feb 28, 2004
  1138. ========================
  1139. -Added a Vim syntax file.
  1140. -Eliminated length var from generated execute code in favour of an end
  1141. pointer. Using length requires two variables be read and written. Using an
  1142. end pointer requires one variable read and written and one read. Results in
  1143. more optimizable code.
  1144. -Minimization is now on by default.
  1145. -States are ordered in output by depth first search.
  1146. -Bug in minimization fixed. States were not being distinguished based on
  1147. error actions.
  1148. -Added null and empty builtin machines.
  1149. -Added EOF error action operators. These are >~, >@, $~, and %~. EOF error
  1150. operators embed actions to take if the EOF is seen and interpreted as an
  1151. error. The operators correspond to the following states:
  1152. -the start state
  1153. -any state with a transition to a final state
  1154. -any state with a transiion out
  1155. -a final state
  1156. -Fixed bug in generation of unreference machine vars using -M. Unreferenced
  1157. vars don't have a name tree built underneath when starting from
  1158. instantiations. Need to instead build the name tree starting at the var.
  1159. -Calls, returns, holds and references to fc in out action code are now
  1160. handled for ipgoto output.
  1161. -Only actions referenced by an instantiated machine expression are put into
  1162. the action index and written out.
  1163. -Added rlscan, an example that lexes Ragel input.
  1164. Ragel 3.1 - Feb 18, 2004
  1165. ========================
  1166. -Duplicates in OR literals are removed and no longer cause an assertion
  1167. failure.
  1168. -Duplicate entry points used in goto and call statements are made into
  1169. deterministic entry points.
  1170. -Base FsmGraph code moved from aapl into ragel, as an increasing amount
  1171. of specialization is required. Too much time was spent attempting to
  1172. keep it as a general purpose template.
  1173. -FsmGraph code de-templatized and heirarchy squashed to a single class.
  1174. -Single transitions taken out of FsmGraph code. In the machine construction
  1175. stage, transitions are now implemented only with ranges and default
  1176. transtions. This reduces memory consumption, simplifies code and prevents
  1177. covered transitions. However it requires the automated selection of single
  1178. transitions to keep goto-driven code lean.
  1179. -Machine reduction completely rewritten to be in-place. As duplicate
  1180. transitions and actions are found and the machine is converted to a format
  1181. suitable for writing as C code or as GraphViz input, the memory allocated
  1182. for states and transitions is reused, instead of newly allocated.
  1183. -New reduction code consolodates ranges, selects a default transition, and
  1184. selects single transitions with the goal of joining ranges that are split by
  1185. any number of single characters.
  1186. -Line directive changed from "# <num> <file>" to the more common format
  1187. "#line <num> <file>".
  1188. -Operator :! changed to @!. This should have happened in last release.
  1189. -Added params example.
  1190. Ragel 3.0 - Jan 22, 2004
  1191. ========================
  1192. -Ragel now parses the contents of struct statements and action code.
  1193. -The keyword fc replaces the use of *p to reference the current character in
  1194. action code.
  1195. -Machine instantiations other than main are allowed.
  1196. -Call, jump and return statements are now available in action code. This
  1197. facility makes it possible to jump to an error handling machine, call a
  1198. sub-machine for parsing a field or to follow paths through a machine as
  1199. determined by arbitrary C code.
  1200. -Added labels to the language. Labels can be used anywhere in a machine
  1201. expression to define an entry point. Also references to machine definitions
  1202. cause the implicit creation of a label.
  1203. -Added epsilon transitions to the language. Epsilon operators may reference
  1204. labels in the current name scope resolved when join operators are evaluated
  1205. and at the root of the expression tree of machine assignment/instantiation.
  1206. -Added the comma operator, which joins machines together without drawing any
  1207. transitions between them. This operator is useful in combination with
  1208. labels, the epsilon operator and user code transitions for defining machines
  1209. using the named state and transition list paradigm. It is also useful for
  1210. invoking transitions based on some analysis of the input or on the
  1211. environment.
  1212. -Added >!, :!, $!, %! operators for specifying actions to take should the
  1213. machine fail. These operators embed actions to execute if the machine
  1214. fails in
  1215. -the start state
  1216. -any state with a transition to a final state
  1217. -any state with a transiion out
  1218. -a final state
  1219. The general rule is that if an action embedding operator embeds an action
  1220. into a set of transitions T, then the error-counterpart with a ! embeds an
  1221. action into the error transition taken when any transition T is a candidate,
  1222. but does not match the input.
  1223. -The finishing augmentation operator ':' has been changed to '@'. This
  1224. frees the ':' symbol for machine labels and avoids hacks to the parser to
  1225. allow the use of ':' for both labels and finishing augmentations. The best
  1226. hack required that label names be distinct from machine definition names as
  1227. in main := word : word; This restriction is not good because labels are
  1228. local to the machine that they are used in whereas machine names are global
  1229. entities. Label name choices should not be restricted by the set of names
  1230. that are in use for machines.
  1231. -Named priority syntax now requires parenthesis surrounding the name and
  1232. value pair. This avoids grammar ambiguities now that the ',' operator has
  1233. been introduced and makes it more clear that the name and value are an
  1234. asscociated pair.
  1235. -Backslashes are escaped in line directive paths.
  1236. Ragel 2.2 - Oct 6, 2003
  1237. =======================
  1238. -Added {n}, {,n}, {n,} {n,m} repetition operators.
  1239. <expr> {n} -- exactly n repetitions
  1240. <expr> {,n} -- zero to n repetitions
  1241. <expr> {n,} -- n or more repetitions
  1242. <expr> {n,m} -- n to m repetitions
  1243. -Bug in binary search table in Aapl fixed. Fixes crashing on machines that
  1244. add to action tables that are implicitly shared among transitions.
  1245. -Tests using obsolete minimization algorithms are no longer built and run by
  1246. default.
  1247. -Added atoi and concurrent from examples to the test suite.
  1248. Ragel 2.1 - Sep 22, 2003
  1249. ========================
  1250. -Bug in priority comparison code fixed. Segfaulted on some input with many
  1251. embedded priorities.
  1252. -Added two new examples.
  1253. Ragel 2.0 - Sep 7, 2003
  1254. =======================
  1255. -Optional (?), One or More (+) and Kleene Star (*) operators changed from
  1256. prefix to postfix. Rationale is that postfix version is far more common in
  1257. regular expression implementations and will be more readily understood.
  1258. -All priority values attached to transitions are now accompanied by a name.
  1259. Transitions no longer have default priority values of zero assigned
  1260. to them. Only transitions that have different priority values assigned
  1261. to the same name influence the NFA-DFA conversion. This scheme reduces
  1262. side-effects of priorities.
  1263. -Removed the %! statement for unsetting pending out priorities. With
  1264. named priorities, it is not necessary to clear the priorities of a
  1265. machine with $0 %! because non-colliding names can be used to avoid
  1266. side-effects.
  1267. -Removed the clear keyword, which was for removing actions from a machine.
  1268. Not required functionality and it is non-intuitive to have a language
  1269. feature that undoes previous definitions.
  1270. -Removed the ^ modifier to repetition and concatenation operators. This
  1271. undocumented feature prevented out transitions and out priorities from being
  1272. transfered from final states to transitions leaving machines. Not required
  1273. functionality and complicates the language unnecessarily.
  1274. -Keyword 'func' changed to 'action' as a part of the phasing out of the term
  1275. 'function' in favour of 'action'. Rationale is that the term 'function'
  1276. implies that the code is called like a C function, which is not necessarily
  1277. the case. The term 'action' is far more common in state machine compiler
  1278. implementations.
  1279. -Added the instantiation statement, which looks like a standard variable
  1280. assignment except := is used instead of =. Instantiations go into the
  1281. same graph dictionary as definitions. In the the future, instantiations
  1282. will be used as the target for gotos and calls in action code.
  1283. -The main graph should now be explicitly instantiated. If it is not,
  1284. a warning is issued.
  1285. -Or literal basic machines ([] outside of regular expressions) now support
  1286. negation and ranges.
  1287. -C and C++ interfaces lowercased. In the C interface an underscore now
  1288. separates the fsm machine and the function name. Rationale is that lowercased
  1289. library and generated routines are more common.
  1290. C output:
  1291. int fsm_init( struct clang *fsm );
  1292. int fsm_execute( struct clang *fsm, char *data, int dlen );
  1293. int fsm_finish( struct clang *fsm );
  1294. C++ output:
  1295. int fsm::init( );
  1296. int fsm::execute( char *data, int dlen );
  1297. int fsm::finish( );
  1298. -Init, execute and finish all return -1 if the machine is in the error state
  1299. and can never accept, 0 if the machine is in a non-accepting state that has a
  1300. path to a final state and 1 if the machine is in an accepting state.
  1301. -Accept routine eliminated. Determining whether or not the machine accepts is
  1302. done by examining the return value of the finish routine.
  1303. -In C output, fsm structure is no longer a typedef, so referencing requires
  1304. the struct keyword. This is to stay in line with C language conventions.
  1305. -In C++ output, constructor is no longer written by ragel. As a consequence,
  1306. init routine is not called automatically. Allows constructor to be supplied
  1307. by user as well as the return value of init to be examined without calling it
  1308. twice.
  1309. -Static start state and private structures are taken out of C++ classes.
  1310. Ragel 1.5.4 - Jul 14, 2003
  1311. ==========================
  1312. -Workaround for building with bison 1.875, which produces an
  1313. optimization that doesn't build with newer version gcc.
  1314. Ragel 1.5.3 - Jul 10, 2003
  1315. ==========================
  1316. -Fixed building with versions of flex that recognize YY_NO_UNPUT.
  1317. -Fixed version numbers in ragel.spec file.
  1318. Ragel 1.5.2 - Jul 7, 2003
  1319. =========================
  1320. -Transition actions and out actions displayed in the graphviz output.
  1321. -Transitions on negative numbers handled in graphviz output.
  1322. -Warning generated when using bison 1.875 now squashed.
  1323. Ragel 1.5.1 - Jun 21, 2003
  1324. ==========================
  1325. -Bugs fixed: Don't delete the output objects when writing to standard out.
  1326. Copy mem into parser buffer with memcpy, not strcpy. Fixes buffer mem errror.
  1327. -Fixes for compiling with Sun WorkShop 6 compilers.
  1328. Ragel 1.5.0 - Jun 10, 2003
  1329. ==========================
  1330. -Line directives written to the output so that errors in the action code
  1331. are properly reported in the ragel input file.
  1332. -Simple graphviz dot file output format is supported. Shows states and
  1333. transitions. Does not yet show actions.
  1334. -Options -p and -f dropped in favour of -d output format.
  1335. -Added option -M for specifying the machine to dump with -d or the graph to
  1336. generate with -V.
  1337. -Error recovery implemented.
  1338. -Proper line and column number tracking implemented in the scanner.
  1339. -All action/function code is now embedded in the main Execute routine. Avoids
  1340. duplication of action code in the Finish routine and the need to call
  1341. ExecFuncs which resulted in huge code bloat. Will also allow actions to
  1342. modify cs when fsm goto, call and return is supported in action code.
  1343. -Fsm spec can have no statements, nothing will be generated.
  1344. -Bug fix: Don't accept ] as the opening of a .-. range a reg exp.
  1345. -Regular expression or set ranges (ie /[0-9]/) are now handled by the parser
  1346. and consequently must be well-formed. The following now generates a parser
  1347. error: /[+-]/ and must be rewritten as /[+\-]/. Also fixes a bug whereby ]
  1348. might be accepted as the opening of a .-. range causing /[0-9]-[0-9]/ to
  1349. parse incorrectly.
  1350. -\v, \f, and \r are now treated as whitespace in an fsm spec.
  1351. Ragel 1.4.1 - Nov 19, 2002
  1352. ==========================
  1353. -Compile fixes. The last release (integer alphabets) was so exciting
  1354. that usual portability checks got bypassed.
  1355. Ragel 1.4.0 - Nov 19, 2002
  1356. ==========================
  1357. -Arbitrary integer alphabets are now fully supported! A new language
  1358. construct:
  1359. 'alphtype <type>' added for specifying the type of the alphabet. Default
  1360. is 'char'. Possible alphabet types are:
  1361. char, unsigned char, short, unsigned short, int, unsigned int
  1362. -Literal machines specified in decimal format can now be negative when the
  1363. alphabet is a signed type.
  1364. -Literal machines (strings, decimal and hex) have their values checked for
  1365. overflow/underflow against the size of the alphabet type.
  1366. -Table driven and goto driven output redesigned to support ranges. Table
  1367. driven uses a binary search for locating single characters and ranges. Goto
  1368. driven uses a switch statement for single characters and nested if blocks for
  1369. ranges.
  1370. -Switch driven output removed due to a lack of consistent advantages. Most of
  1371. the time the switch driven FSM is of no use because the goto FSM makes
  1372. smaller and faster code. Under certain circumstances it can produce smaller
  1373. code than a goto driven fsm and be almost as fast, but some sporadic case
  1374. does not warrant maintaining it.
  1375. -Many warnings changed to errors.
  1376. -Added option -p for printing the final fsm before minimization. This lets
  1377. priorities be seen. Priorties are all reset to 0 before minimization. The
  1378. exiting option -f prints the final fsm after minimization.
  1379. -Fixed a bug in the clang test and example that resulted in redundant actions
  1380. being executed.
  1381. Ragel 1.3.4 - Nov 6, 2002
  1382. =========================
  1383. -Fixes to Chapter 1 of the guide.
  1384. -Brought back the examples and made them current.
  1385. -MSVC is no longer supported for compiling windows binaries because its
  1386. support for the C++ standard is frustratingly inadequate, it will cost money
  1387. to upgrade if it ever gets better, and MinGW is a much better alternative.
  1388. -The build system now supports the --host= option for building ragel
  1389. for another system (used for cross compiling a windows binary with MinGW).
  1390. -Various design changes and fixes towards the goal of arbitrary integer
  1391. alphabets and the handling of larger state machines were made.
  1392. -The new shared vector class is now used for action lists in transitions and
  1393. states to reduce memory allocations.
  1394. -An avl tree is now used for the reduction of transitions and functions of an
  1395. fsm graph before making the final machine. The tree allows better scalability
  1396. and performance by not requiring consecutively larger heap allocations.
  1397. -Final stages in the separation of fsm graph code from action embedding and
  1398. priority assignment is complete. Makes the base graph leaner and easier to reuse
  1399. in other projects (like Keller).
  1400. Ragel 1.3.3 - Oct 22, 2002
  1401. ==========================
  1402. -More diagrams were added to section 1.7.1 of the user guide.
  1403. -FSM Graph code was reworked to spearate the regex/nfa/minimizaion graph
  1404. algorithms from the manipulation of state and transition properties.
  1405. -An rpm spec file from Cris Bailiff was added. This allows an rpm for ragel
  1406. to be built with the command 'rpm -ta ragel-x.x.x.tar.gz'
  1407. -Fixes to the build system and corresponding doc updates in the README.
  1408. -Removed autil and included the one needed source file directly in the top
  1409. level ragel directory.
  1410. -Fixed a bug that nullified the 20 times speedup in large compilations
  1411. claimed by the last version.
  1412. -Removed awk from the doc build (it was added with the last release -- though
  1413. not mentioned in the changelog).
  1414. -Install of man page was moved to the doc dir. The install also installs the
  1415. user guide to $(PREFIX)/share/doc/ragel/
  1416. Ragel 1.3.2 - Oct 16, 2002
  1417. ==========================
  1418. -Added option -v (or --version) to show version information.
  1419. -The subtract operator no longer removes transition data from the machine
  1420. being subtracted. This is left up to the user for the purpose of making it
  1421. possible to transfer transitions using subtract and also for speeding up the
  1422. subtract routine. Note that it is possible to explicitly clear transition
  1423. data before a doing a subtract.
  1424. -Rather severe typo bug fixed. Bug was related to transitions with higher
  1425. priorities taking precedence. A wrong ptr was being returned. It appears to
  1426. have worked most of the time becuase the old ptr was deleted and the new one
  1427. allocated immediatly after so the old ptr often pointed to the same space.
  1428. Just luck though.
  1429. -Bug in the removing of dead end paths was fixed. If the start state
  1430. has in transitions then those paths were not followed when finding states to
  1431. keep. Would result in non-dead end states being removed from the graph.
  1432. -In lists and in ranges are no longer maintained as a bst with the key as the
  1433. alphabet character and the value as a list of transitions coming in on that
  1434. char. There is one list for each of inList, inRange and inDefault. Now that
  1435. the required functionality of the graph is well known it is safe to remove
  1436. these lists to gain in speed and footprint. They shouldn't be needed.
  1437. -IsolateStartState() runs on modification of start data only if the start
  1438. state is not already isolated, which is now possible with the new in list
  1439. representation.
  1440. -Concat, Or and Star operators now use an approximation to
  1441. removeUnreachableStates that does not require a traversal of the entire
  1442. graph. This combined with an 'on-the-fly' management of final bits and final
  1443. state status results is a dramatic speed increase when compiling machines
  1444. that use those operators heavily. The strings2 test goes 20 times faster.
  1445. -Before the final minimization, after all fsm operations are complete,
  1446. priority data is reset which enables better minimization in cases where
  1447. priorities would otherwise separate similar states.
  1448. Ragel 1.3.1 - Oct 2, 2002
  1449. =========================
  1450. -Range transitions are now used to implement machines made with /[a-z]/ and
  1451. the .. operator as well as most of the builtin machines. The ranges are not
  1452. yet reflected in the output code, they are expanded as if they came from the
  1453. regular single transitions. This is one step closer to arbitrary integer
  1454. output.
  1455. -The builtin machine 'any' was added. It is equiv to the builtin extend,
  1456. matching any characters.
  1457. -The builtin machine 'cntrl' now includes newline.
  1458. -The builtin machine 'space' now includes newline.
  1459. -The builtin machine 'ascii' is now the range 0-127, not all characters.
  1460. -A man page was written.
  1461. -A proper user guide was started. Chapter 1: Specifying Ragel Programs
  1462. was written. It even has some diagrams :)
  1463. Ragel 1.3.0 - Sep 4, 2002
  1464. =========================
  1465. -NULL keyword no longer used in table output.
  1466. -Though not yet in use, underlying graph structure changed to support range
  1467. transitions. As a result, most of the code that walks transition lists is now
  1468. implemented with an iterator that hides the complexity of the transition
  1469. lists and ranges. Range transitions will be used to implement /[a-z]/ style
  1470. machines and machines made with the .. operator. Previously a single
  1471. transition would be used for each char in the range, which is very costly.
  1472. Ranges eliminate much of the space complexity and allow for the .. operator
  1473. to be used with very large (integer) alphabets.
  1474. -New minimization similar to Hopcroft's alg. It does not require n^2 space and
  1475. runs close to O(n*log(n)) (an exact analysis of the alg is very hard). It is
  1476. much better than the stable and approx minimization and obsoletes them both.
  1477. An exact implementation of Hopcroft's alg is desirable but not possible
  1478. because the ragel implementation does not assume a finite alphabet, which
  1479. Hopcroft's requires. Ragel will support arbitrary integer alphabets which
  1480. must be treated as an infinite set for implementation considerations.
  1481. -New option -m using above described minimization to replace all previous
  1482. minimization options. Old options sill work but are obsolete and not
  1483. advertised with -h.
  1484. -Bug fixed in goto style output. The error exit set the current state to 0,
  1485. which is actually a valid state. If the machine was entered again it would go
  1486. into the first state, very wrong. If the first state happened to be final then
  1487. an immediate finish would accept when in fact it should fail.
  1488. -Slightly better fsm minimization now capable due to clearing of the
  1489. transition ordering numbers just prior to minimization.
  1490. Ragel 1.2.2 - May 25, 2002
  1491. ==========================
  1492. -Configuration option --prefix now works when installing.
  1493. -cc file extension changed to cpp for better portability.
  1494. -Unlink of output file upon error no longer happens, removes dependency on
  1495. unlink system command.
  1496. -All multiline strings removed: not standard c++.
  1497. -Awk build dependency removed.
  1498. -MSVC 6.0 added to the list of supported compilers (with some tweaking of
  1499. bison and flex output).
  1500. Ragel 1.2.1 - May 13, 2002
  1501. ==========================
  1502. -Automatic dependencies were fixed, they were not working correctly.
  1503. -Updated AUTHORS file to reflect contributors.
  1504. -Code is more C++ standards compliant: compiles with g++ 3.0
  1505. -Fixed bugs that only showed up in g++ 3.0
  1506. -Latest (unreleased) Aapl.
  1507. -Configuration script bails out if bison++ is installed. Ragel will not
  1508. compile with bison++ because it is coded in c++ and bison++ automatically
  1509. generates a c++ parser. Ragel uses a c-style bison parser.
  1510. Ragel 1.2.0 - May 3, 2002
  1511. =========================
  1512. -Underlying graph structure now supports default transitions. The result is
  1513. that a transition does not need to be made for each char of the alphabet
  1514. when making 'extend' or '/./' machines. Ragel compiles machines that
  1515. use the aforementioned primitives WAY faster.
  1516. -The ugly hacks needed to pick default transitions now go away due to
  1517. the graph supporting default transitions directly.
  1518. -If -e is given, but minimization is not turned on, print a warning.
  1519. -Makefiles use automatic dependencies.
  1520. Ragel 1.1.0 - Apr 15, 2002
  1521. ==========================
  1522. -Added goto fsm: much faster than any other fsm style.
  1523. -Default operator (if two machines are side by side with no operator
  1524. between them) is concatenation. First showed up in 1.0.4.
  1525. -The fsm machine no longer auotmatically builds the flat table for
  1526. transition indicies. Instead it keeps the key,ptr pair. In tabcodegen
  1527. the flat table is produced. This way very large alphabets with sparse
  1528. transitions will not consume large amounts of mem. This is also in prep
  1529. for fsm graph getting a default transition.
  1530. -Generated code contains a statement explicitly stating that ragel fsms
  1531. are NOT covered by the GPL. Technically, Ragel copies part of itself
  1532. to the output to make the generic fsm execution routine (for table driven
  1533. fsms only) and so the output could be considered under the GPL. But this
  1534. code is very trivial and could easlily be rewritten. The actual fsm data
  1535. is subject to the copyright of the source. To promote the use of Ragel,
  1536. a special exception is made for the part of the output copied from Ragel:
  1537. it may be used without restriction.
  1538. -Much more elegant code generation scheme is employed. Code generation
  1539. class members need only put the 'codegen' keyword after their 'void' type
  1540. in order to be automatically registerd to handle macros of the same name.
  1541. An awk script recognises this keyword and generates an appropriate driver.
  1542. -Ragel gets a test suite.
  1543. -Postfunc and prefunc go away because they are not supported by non
  1544. loop-driven fsms (goto, switch) and present duplicate functionality.
  1545. Universal funcs can be implemented by using $ operator.
  1546. -Automatic dependencies used in build system, no more make depend target.
  1547. -Code generation section in docs.
  1548. -Uses the latests aapl.
  1549. Ragel 1.0.5 - Mar 3, 2002
  1550. =========================
  1551. -Bugfix in SetErrorState that caused an assertion failure when compiling
  1552. simple machines that did not have full transition tables (and thus did
  1553. not show up on any example machines). Assertion failure did not occur
  1554. when using the switch statement code as ragel does not call SetErrorState
  1555. in that case.
  1556. -Fixed some missing includes, now compiles on redhat.
  1557. -Moved the FsmMachTrans Compare class out of FsmMachTrans. Some compilers
  1558. don't deal with nested classes in templates too well.
  1559. -Removed old unused BASEREF in fsmgraph and ragel now compiles using
  1560. egcs-2.91.66 and presumably SUNWspro. The baseref is no longer needed
  1561. because states do not support being elements in multiple lists. I would
  1562. rather be able to support more compilers than have this feature.
  1563. -Started a README with compilation notes. Started an AUTHORS file.
  1564. -Started the user documentation. Describes basic machines and operators.
  1565. Ragel 1.0.4 - Mar 1, 2002
  1566. =========================
  1567. -Ported to the version of Aapl just after 2.2.0 release. See
  1568. http://www.ragel.ca/aapl/ for details on aapl.
  1569. -Fixed a bug in the clang example: the newline machine was not stared.
  1570. -Added explanations to the clang and mailbox examples. This should
  1571. help people that want to learn the lanuage as the manual is far from
  1572. complete.
  1573. Ragel 1.0.3 - Feb 2, 2002
  1574. =========================
  1575. -Added aapl to the ragel tree. No longer requires you to download
  1576. and build aapl separately. Should avoid discouraging impatient users
  1577. from compiling ragel.
  1578. -Added the examples to the ragel tree.
  1579. -Added configure script checks for bison and flex.
  1580. -Fixed makefile so as not to die with newer versions of bison that
  1581. write the header of the parser to a .hh file.
  1582. -Started ChangeLog file.
  1583. Ragel 1.0.2 - Jan 30, 2002
  1584. ==========================
  1585. -Bug fix in calculating highIndex for table based code. Was using
  1586. the length of out tranisition table rather than the value at the
  1587. end.
  1588. -If high/low index are at the limits, output a define in their place,
  1589. not the high/low values themselves so as not to cause compiler warnings.
  1590. -If the resulting machines don't have any indicies or functions, then
  1591. omit the empty unrefereced static arrays so as not to cause compiler
  1592. warnings about unused static vars.
  1593. -Fixed variable sized indicies support. The header cannot have any
  1594. reference to INDEX_TYPE as that info is not known at the time the header
  1595. data is written. Forces us to use a void * for pointers to indicies. In
  1596. the c++ versions we are forced to make much of the data non-member
  1597. static data in the code portion for the same reason.
  1598. Ragel 1.0.1 - Jan 28, 2002
  1599. ==========================
  1600. -Exe name change from reglang to ragel.
  1601. -Added ftabcodegen output code style which uses a table for states and
  1602. transitions but uses a switch statement for the function execution.
  1603. -Reformatted options in usage dump to look better.
  1604. -Support escape sequences in [] sections of regular expressions.
  1605. Ragel 1.0 - Jan 25, 2002
  1606. ========================
  1607. -Initial release.