Enhanced complex concepts handling
This commit is contained in:
@@ -891,3 +891,47 @@ So,
|
||||
* If, for a given priority there is a match, the parser with a lower priority won't be executed
|
||||
* A parser has access to the output of the parsers of higher priorities (which were executed before it)
|
||||
|
||||
2020-01-11
|
||||
**********
|
||||
|
||||
Status
|
||||
""""""
|
||||
|
||||
Last status was back in October. At that time I could
|
||||
|
||||
::
|
||||
|
||||
def concept hello name as "hello" + name
|
||||
1 + 1
|
||||
sheerka.test()
|
||||
|
||||
1. I can evaluate concepts
|
||||
|
||||
::
|
||||
|
||||
def concept hello a where a
|
||||
hello kodjo
|
||||
|
||||
2. I have worked on BNF definition of the concept
|
||||
|
||||
::
|
||||
|
||||
def concept twenties from bnf 'twenty' (one | two | three)=unit as 20 + unit
|
||||
twenty one
|
||||
eval twenty one
|
||||
|
||||
3. I can mix complex concepts (concepts with more than one word) and Python
|
||||
|
||||
::
|
||||
|
||||
twenty one + twenty two
|
||||
twenty one + one does not work :-(
|
||||
|
||||
|
||||
4. I have a basic implementation for logging. With control of the verbosity
|
||||
|
||||
5. The result of an user input evaluation is now persisted, alongside with the event
|
||||
that was used for it.
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user