Fixed #3: Added sheerka.resolve_rule()
Fixed #5: Refactored SheerkaComparisonManager Fixed #6: Sya parser no longer works after restart
This commit is contained in:
@@ -0,0 +1,19 @@
|
||||
Debugger
|
||||
========
|
||||
|
||||
Abstract
|
||||
--------
|
||||
The purpose of the debugger is to ease to understand why Sheerka does not behave like it should.
|
||||
(yes, this could happen). I have have just started so, they are a lot of
|
||||
functionalities that we usually found in a debugger that are not yet implemented
|
||||
|
||||
I guess that the first thing to know is that I want to design a 'smart' debugger,
|
||||
which can be configured in a 'declarative' way. It means that, rather that telling
|
||||
it what to do, I would prefer tell it what is expected.
|
||||
|
||||
As of now (2021-01-11), I am far from it, so let's explain how to use the debugger,
|
||||
in an 'imperative' way.
|
||||
|
||||
First, you need to enable the debugger. As it consumes resource, it is deactivated by default ::
|
||||
|
||||
set_debug()
|
||||
Reference in New Issue
Block a user