<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gf-core.git/src/compiler/GF/Compile/GetGrammar.hs, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.adelon.net/gf-core.git/atom?h=master</id>
<link rel='self' href='https://git.adelon.net/gf-core.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/'/>
<updated>2023-09-25T07:55:02+00:00</updated>
<entry>
<title>Indent each line of an error message</title>
<updated>2023-09-25T07:55:02+00:00</updated>
<author>
<name>Andreas Källberg</name>
<email>anka.213@gmail.com</email>
</author>
<published>2023-09-25T07:53:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=268a25f59cd4790ef5896ddd237f0bc48f6fad26'/>
<id>urn:sha1:268a25f59cd4790ef5896ddd237f0bc48f6fad26</id>
<content type='text'>
By indenting each line instead of just the first, we simplify
the work of the gf-lsp parser, so we can see which errors are the same
</content>
</entry>
<entry>
<title>Remove "Warning: default encoding has changed from Latin-1 to UTF-8"</title>
<updated>2018-01-23T13:55:33+00:00</updated>
<author>
<name>Thomas Hallgren</name>
<email>th-github@altocumulus.org</email>
</author>
<published>2018-01-23T13:55:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=5164951e23b0d0d5da80562a740d4b5875ef8c3f'/>
<id>urn:sha1:5164951e23b0d0d5da80562a740d4b5875ef8c3f</id>
<content type='text'>
The warning is about a change that was made in GF 3.6 (June 2014) and has
probably outlived its purpose by now.
</content>
</entry>
<entry>
<title>BNF grammars (.bnf or .cf) can have rules without semicolons, as in the GF book examples. However, if the grammar has any multiline rules, all of them must have semicolons.</title>
<updated>2016-09-05T21:15:44+00:00</updated>
<author>
<name>aarne</name>
<email>aarne@chalmers.se</email>
</author>
<published>2016-09-05T21:15:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=8729339d2603a7e18ef05a31bfd47f299084cb8f'/>
<id>urn:sha1:8729339d2603a7e18ef05a31bfd47f299084cb8f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>initial support for BNFC syntax in context-free grammars for GF. Not all features are supported yet. Based on contribution from Gleb Lobanov</title>
<updated>2016-03-21T13:27:44+00:00</updated>
<author>
<name>krasimir</name>
<email>krasimir@chalmers.se</email>
</author>
<published>2016-03-21T13:27:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=c8ebe093150509d9f01d82f0d698ef5df09bd985'/>
<id>urn:sha1:c8ebe093150509d9f01d82f0d698ef5df09bd985</id>
<content type='text'>
</content>
</entry>
<entry>
<title>More haddock documentation improvements</title>
<updated>2014-10-16T14:03:57+00:00</updated>
<author>
<name>hallgren</name>
<email>hallgren@chalmers.se</email>
</author>
<published>2014-10-16T14:03:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=c924491289259fa8a5a259ed97f2d9e817e3338c'/>
<id>urn:sha1:c924491289259fa8a5a259ed97f2d9e817e3338c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Experimental: parallel batch compilation of grammars</title>
<updated>2014-08-25T09:56:00+00:00</updated>
<author>
<name>hallgren</name>
<email>hallgren@chalmers.se</email>
</author>
<published>2014-08-25T09:56:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=d84c5ef1715c3e4aed4098ee9c847e2dcc86cba4'/>
<id>urn:sha1:d84c5ef1715c3e4aed4098ee9c847e2dcc86cba4</id>
<content type='text'>
On my laptop these changes speed up the full build of the RGL and example
grammars with 'cabal build' from ~95s to ~43s and the zero build from ~18s
to ~5s.

The main change is the introduction of the module GF.CompileInParallel that
replaces GF.Compile and the function GF.Compile.ReadFiles.getAllFiles. At
present, it is activated with the new -j flag, and it is only used when
combined with --make or --batch. In addition, to get parallel computations,
you need to add GHC run-time flags, e.g., +RTS -N -A20M -RTS, to the command
line.

The Setup.hs script has been modified to pass the appropriate flags to GF
for parallel compilation when compiling the RGL and example grammars, but you
need a recent version of Cabal for this to work (probably &gt;=1.20).

Some additonal refactoring were made during this work. A new monad is used to
avoid warnings/error messages from different modules to be intertwined when
compiling in parallel, so some functios that were hardiwred to the IO or IOE
monads have been lifted to work in arbitrary monads that are instances in
the appropriate classes.


</content>
</entry>
<entry>
<title>Fix warnings in 16 modules, mostly forward compatibility warnings from GHC 7.8</title>
<updated>2014-08-13T22:16:18+00:00</updated>
<author>
<name>hallgren</name>
<email>hallgren@chalmers.se</email>
</author>
<published>2014-08-13T22:16:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=cd5193b7e19e7ff5e49cdeafe149fdeec8e19fb0'/>
<id>urn:sha1:cd5193b7e19e7ff5e49cdeafe149fdeec8e19fb0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>refactor the compilation of CFG and EBNF grammars. Now they are parsed by using GF.Grammar.Parser just like the ordinary GF grammars. Furthermore now GF.Speech.CFG is moved to GF.Grammar.CFG. The new module is used by both the speech conversion utils and by the compiler for CFG grammars. The parser for CFG now consumes a lot less memory and can be used with grammars with more than 4 000 000 productions.</title>
<updated>2014-03-21T21:25:05+00:00</updated>
<author>
<name>kr.angelov</name>
<email>kr.angelov@gmail.com</email>
</author>
<published>2014-03-21T21:25:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=51a9ef72c7e32f06d2413a5aea5751df2780063b'/>
<id>urn:sha1:51a9ef72c7e32f06d2413a5aea5751df2780063b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Show relative file paths in error messages</title>
<updated>2013-12-06T15:43:34+00:00</updated>
<author>
<name>hallgren</name>
<email>hallgren@chalmers.se</email>
</author>
<published>2013-12-06T15:43:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=a98f4aa4be7b72a310a8b5826e3cc82c7edb8f40'/>
<id>urn:sha1:a98f4aa4be7b72a310a8b5826e3cc82c7edb8f40</id>
<content type='text'>
This is to avoid one trivial reason for failures in the test suite.
</content>
</entry>
<entry>
<title>Change how GF deals with character encodings in grammar files</title>
<updated>2013-11-25T21:12:11+00:00</updated>
<author>
<name>hallgren</name>
<email>hallgren@chalmers.se</email>
</author>
<published>2013-11-25T21:12:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.adelon.net/gf-core.git/commit/?id=9d7fdf7c9a525a3b5659a566f76d26d151dcd664'/>
<id>urn:sha1:9d7fdf7c9a525a3b5659a566f76d26d151dcd664</id>
<content type='text'>
1. The default encoding is changed from Latin-1 to UTF-8.

2. Alternate encodings should be specified as "--# -coding=enc", the old
   "flags coding=enc" declarations have no effect but are still checked for
   consistency.

3. A transitional warning is generated for files that contain non-ASCII
   characters without specifying a character encoding:

	"Warning: default encoding has changed from Latin-1 to UTF-8"

4. Conversion to Unicode is now done *before* lexing. This makes it possible
   to allow arbitrary Unicode characters in identifiers. But identifiers are
   still stored as ByteStrings, so they are limited to Latin-1 characters
   for now.

5. Lexer.hs is no longer part of the repository. We now generate the lexer
   from Lexer.x with alex&gt;=3. Some workarounds for bugs in alex-3.0 were
   needed. These bugs might already be fixed in newer versions of alex, but
   we should be compatible with what is shipped in the Haskell Platform.
</content>
</entry>
</feed>
