Unnamed repository; edit this file 'description' to name the repository. https://git.adelon.net/gf-core.git/atom?h=optimize 2025-08-08T16:06:03+00:00 2025-08-08T16:06:03+00:00 Herbert Lange herbert.lange@gu.se 2025-08-08T16:06:03+00:00 urn:sha1:9e5701b13c61c4ff63df6beb9fa7200ba8a81f9f 2025-08-08T16:02:59+00:00 Herbert Lange herbert.lange@gu.se 2025-08-08T16:02:59+00:00 urn:sha1:78beac759862d330a89a5479c5dab84e5d8cd526 2025-08-08T15:43:56+00:00 Herbert Lange herbert.lange@gu.se 2025-08-08T15:43:56+00:00 urn:sha1:1c4cde7c66d0583c40dbc69e63878e7ee52b8042 2025-08-08T15:36:03+00:00 Herbert Lange herbert.lange@gu.se 2025-08-08T15:36:03+00:00 urn:sha1:e0ad7594dd510f64debc26004a6d02b0b829770a 2018-07-04T11:40:46+00:00 John J. Camilleri john@digitalgrammars.com 2018-07-04T11:40:46+00:00 urn:sha1:b9b02171601f68a8896ad2f369c700e356c8615b 2017-08-11T13:33:21+00:00 Thomas Hallgren th-github@altocumulus.org 2017-08-11T13:33:21+00:00 urn:sha1:8484dabd5b82dcc267a23a00ca55e8abdec5000b TODO: get version info from git instead. 2014-01-20T17:06:11+00:00 hallgren hallgren@chalmers.se 2014-01-20T17:06:11+00:00 urn:sha1:9d71ffc831164c7cba260d1bb3f0a968cca8c3e7 If the C run-time library is compiled and installed on your system, you can now do 'cabal configure -fc-runtime' to get the following extras: + The haskell binding to the C run-time library will be included in the PGF library (so you can import it in Haskell applications). Documentation on the new modules will be included when you run 'cabal haddock'. + The new command 'pgf-shell', implemented on top of haskell binding to the C run-time system. + Three new commands in the web API: c-parse, c-linearize and c-translate. Their interfaces are similar to the corresponding commands without the "c-" prefix, but they should be considered preliminary. 2012-11-13T14:09:15+00:00 hallgren hallgren@chalmers.se 2012-11-13T14:09:15+00:00 urn:sha1:27e675910a88fec3d7f0cc0ac6020d86f1089fe7 GF.Compile.Compute.ConcreteNew + two new modules contain a new partial evaluator intended to solve some performance problems with the old partial evalutator in GF.Compile.Compute.ConcreteLazy. It has been around for a while, but is now complete enough to compile the RGL and the Phrasebook. The old partial evaluator is still used by default. The new one can be activated in two ways: - by using the command line option -new-comp when invoking GF. - by using cabal configure -fnew-comp to make -new-comp the default. In this case you can also use the command line option -old-comp to revert to the old partial evaluator. In the GF shell, the cc command uses the old evaluator regardless of -new-comp for now, but you can use "cc -new ..." to invoke the new evaluator. With -new-comp, computations happen in GF.Compile.GeneratePMCFG instead of GF.Compile.Optimize. This is implemented by testing the flag optNewComp in both modules, to omit calls to the old partial evaluator from GF.Compile.Optimize and add calls to the new partial evaluator in GF.Compile.GeneratePMCFG. This also means that -new-comp effectively implies -noexpand. In GF.Compile.CheckGrammar, there is a check that restricted inheritance is used correctly. However, when -noexpand is used, this check causes unexpected errors, so it has been converted to generate warnings, for now. -new-comp no longer enables the new type checker in GF.Compile.Typeckeck.ConcreteNew. The GF version number has been bumped to 3.3.10-darcs 2012-10-18T20:01:22+00:00 hallgren hallgren@chalmers.se 2012-10-18T20:01:22+00:00 urn:sha1:584b6ba86d15e7ff471f94d2d120375ba3604553 ... to avoid unnecessary recompilation of other modules. 2012-05-30T15:45:45+00:00 hallgren hallgren@chalmers.se 2012-05-30T15:45:45+00:00 urn:sha1:13cda24924614b00e26ae11e109f147c616638e1 The Setup.hs script now queries darcs to create more detailed version info to include in the startup message. Note thought that with distributed version control systems like darcs, the only way to uniquely identify a version is by the set of patches included. Since the patches are not totally ordered, just looking at the last patch is not enough. For official releases, we tag the current set of patches so we can refer to it by name (e.g. RELEASE-3.3.3).