gf-core.git/src/runtime/c/pgf/literals.h, branch optimize Unnamed repository; edit this file 'description' to name the repository. https://git.adelon.net/gf-core.git/atom?h=optimize 2017-04-19T09:34:23+00:00 explicitly classify all functions in libpgf as either internal or API functions 2017-04-19T09:34:23+00:00 krasimir krasimir@chalmers.se 2017-04-19T09:34:23+00:00 urn:sha1:7d72d99c2f7fc228d71df627a10a2ff776335b2b a patch from Bjørnar Luteberget for compatibility with MSVC 2017-04-12T10:24:56+00:00 krasimir krasimir@chalmers.se 2017-04-12T10:24:56+00:00 urn:sha1:a8eaa2f2e560547e63c7976960435e1ae23a22b1 added callback in C for unknown words 2015-05-19T09:15:48+00:00 krasimir krasimir@chalmers.se 2015-05-19T09:15:48+00:00 urn:sha1:786da46a9913df3ad27e1631cf4de75d9186aeb0 change in the API for literals 2014-12-16T10:21:26+00:00 kr.angelov kr.angelov@gmail.com 2014-12-16T10:21:26+00:00 urn:sha1:9bc5349e622cf00156b46f56a940d035e000115a The API in the C runtime as well as in the Haskell, Python and Java binding is changed. Now instead of adding the literal callbacks to the concrete syntax you need to supply them every time when you need to parse. The main reason is: - referentially transparent API for Haskell - when we start using memory mapped files we will not be allowed to change anything in the grammar data structures. At that point the old API would be impossible to use. libpgf: a new implementation for literals which also allows custom literals. the same mechanism is now used for the metavariables 2012-03-12T14:25:51+00:00 kr.angelov kr.angelov@gmail.com 2012-03-12T14:25:51+00:00 urn:sha1:230f309317af6ae79f49091c9580223f756dbfb8