krasimir
4d39c2623b
added libsg in the C runtime
2015-08-24 09:36:51 +00:00
krasimir
f9250c610c
retrieval of a triple
2015-08-21 16:31:43 +00:00
krasimir
b66276fda5
API for storing triples in the semantic graph
2015-08-21 16:13:03 +00:00
krasimir
c7c47fbded
add the initial sketches of the semantic graph storage
2015-08-20 13:31:43 +00:00
krasimir
e9a8e083a0
bugfix for the word prediction in the App
2015-08-06 12:51:42 +00:00
krasimir
a982a4d15f
bugfix in lookup_morpho in the C runtime
2015-08-06 11:51:23 +00:00
krasimir
a976d7e44b
make the virtual machine instructions more uniform
2015-07-16 15:43:18 +00:00
krasimir
806a33ef98
refine the GNU lightning patch to avoid generating unnecessary code
2015-07-16 15:29:14 +00:00
krasimir
2b52a1a2ea
bugfixes in the JIT compiler for x86_64. One of the fixes is actually in GNU lightning
2015-07-16 15:21:09 +00:00
krasimir
99a0b5a1d8
the reasoner's states are now closures just like the code for the def rules. This means more compact JIT compiled code and uniformity with the code for def rules
2015-07-04 15:06:34 +00:00
krasimir
85e6e017af
merge the states for reasoning and evaluation into a single structure
2015-07-03 11:53:52 +00:00
krasimir
974e152ac3
bugfix in the parser for lexical lookup
2015-06-30 12:54:19 +00:00
hallgren
4e9e7c2bdd
Documentation updates for the release of GF 3.7
2015-06-25 12:10:47 +00:00
krasimir
51c13f7aac
bugfix in the bottom-up prediction for the parser
2015-06-25 09:46:43 +00:00
hallgren
71c037b4df
runtime/c/pf/jit.c: silence warning about alloca on MINGW32
2015-06-23 15:49:31 +00:00
krasimir
324cdffc26
the orthographic tokens were broken when they appear inside a dictionary entry. Now this is fixed by treating those as syntactic rules
2015-06-12 13:03:19 +00:00
krasimir
aa87b0d272
print error message for missing abstract categories in the C runtime
2015-06-05 07:41:59 +00:00
krasimir
121fe53968
added callback in C for unknown words
2015-05-19 09:15:48 +00:00
krasimir
4347ce727a
the NERC in C is now fully up-to-date with the other NERCs. In addition the NERC in Haskell and Java now refuses to recognize names that match words in the lexicon. The latest is useful for German
2015-05-19 07:26:56 +00:00
krasimir
815d1f441f
bugfix in the NERC in C
2015-05-18 15:02:44 +00:00
krasimir
3ebadcbc3b
the callbacks in C now take the concrete syntax as a parameter
2015-05-18 14:41:33 +00:00
krasimir
8cfd46b9bb
pgf_lookup_morpho and pgf_lookup_word_prefix are now also case insensitive if case_sensitive=off
2015-05-18 14:20:35 +00:00
krasimir
472a95a844
"flags case_sensitive=off" makes the parser case insensitive
2015-05-11 14:11:42 +00:00
krasimir
3d502a76b3
added all orthographic primitives
2015-05-11 13:01:39 +00:00
krasimir
949310ef1b
implemented CAPIT in parsing
2015-05-08 18:54:50 +00:00
krasimir
7ee9edd080
fix in the dictionary lookup
2015-05-08 18:12:24 +00:00
krasimir
b87ed432a5
a new nice and elegant algorithm for dictionary lookup in the parser
2015-05-08 14:38:24 +00:00
krasimir
e600eb764a
the parser is now fully Unicode compatible
2015-05-08 09:23:29 +00:00
krasimir
5b60c3a00e
fix gu_ucs_is_space in libgu
2015-05-07 15:50:55 +00:00
krasimir
6eb15eb585
fix the NERC in C to work for PN as literal
2015-05-07 15:16:55 +00:00
krasimir
4ae661e19e
fix pgf-translate to use the NERC again
2015-05-07 14:49:30 +00:00
krasimir
77f14f3cc8
fix the UTF8 implementation in libgu
2015-05-06 15:51:12 +00:00
krasimir
79b710a6b7
added getpagesize() definition for Windows
2015-04-20 09:57:28 +00:00
krasimir
7c24ce9758
fix the compilation of gu/mem.c on Windows. For now memory mapped pools on Windows are just not supported.
2015-03-19 09:28:31 +00:00
krasimir
35c4b5f3eb
remove the meta_item variable from the parse state
2015-03-06 15:18:50 +00:00
krasimir
0764d518c7
fix some out-of-date code for the PGF_RESULT_DEBUG mode in the parser
2015-02-26 13:31:26 +00:00
krasimir
42908bd95f
use the same trick for comparison of doubles in cmp_expr_state
2015-02-26 13:10:01 +00:00
krasimir
dfd69d5d4b
bugfix in the parser which caused some items to be poped in the wrong order if their probability differ with less that 0.5
2015-02-26 12:17:59 +00:00
krasimir
79a7ae6553
remove three more uses of meta productions that were left in debugging mode
2015-02-24 10:59:18 +00:00
krasimir
8664dd80ed
implemented escape characters when reading/printing an abstract expression with string literals
2015-02-24 09:35:12 +00:00
krasimir
87c0368281
silence some warnings in GNU Lightning for i386_64
2015-02-19 12:53:52 +00:00
krasimir
2f35aadc6f
parsing with meta rules is now removed since we don't use them anymore and I would gladly remove some code.
2015-02-19 11:59:51 +00:00
krasimir
27a12ca9fb
fix in the parser for callbacks in the middle of a word
2015-02-18 16:14:29 +00:00
hallgren
2ce3e954fd
Changes for compatibility with ghc-7.10-rc2
...
2 modules: Name clashes caused by Applicative-Monad change in Prelude
2 modules: Ambiguities caused by Foldable/Traversable in Prelude
2 modules: Backwards incompatible changes in time-1.5 for defaultTimeLocale
9 modules: {-# LANGUAGE FlexibleContexts #-} (because GHC checks inferred types
now, in addition to explicitly given type signatures)
Also silenced warnings about tab characters in source files.
2015-02-16 15:05:06 +00:00
kr.angelov
e6f51d7ec6
fix in the JIT compiler that would hopefully make it work on iOS
2015-02-11 13:07:06 +00:00
kr.angelov
328d4df660
API for word alignment in the C runtime and in the Haskell binding
2014-12-29 10:59:20 +00:00
kr.angelov
4b066bde92
more compact implementation for GuStringBuf
2014-12-24 14:20:30 +00:00
kr.angelov
022849482d
added mkStr to the Haskell binding
2014-12-19 08:58:02 +00:00
kr.angelov
fdc6c9a3cd
added mkApp to the Haskell binding
2014-12-19 08:47:00 +00:00
kr.angelov
9b7e18c25e
change in the API for literals
...
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.
2014-12-16 10:21:26 +00:00