- Posts: 8
- Joined: Thu Oct 05, 2017 1:17 pm
I don't understand logic of all hbatch_something
For example hbatch_mantra:
Code: Select all
from parsers import hbatch
from parsers import mantra
class hbatch_mantra(hbatch.hbatch, mantra.mantra):
hbatch.hbatch.__init__(self) # WE init str_error and str_warning from hbatch parser
mantra.mantra.__init__(self) # NOW we re-initialize them, and we lost errors and warnings from hbatch!
def do(self, data, mode):
mantra.mantra.do(self, data, mode)
hbatch.hbatch.do(self, data, mode)
I think, this combination of some parsers in one creates dangerous situations, when we lost all errors and warnings from parsers during initialization, except the last. I catch it, when I added critical error (for our network) to hbatch parser. But It doesn't work in hbatch_... parsers.
- Site Admin
- Posts: 414
- Joined: Sun Jan 15, 2017 8:40 pm
- Location: Russia, Korolev
Yes. This is a bug.
We should append errors and warnings arrays in class constructors. Not reinitialize arrays.
CGRU 2.3.1, Ubuntu 18.04 LTS, MS Windows 10 (clients only).
Who is online
Users browsing this forum: No registered users and 1 guest