http://bugzilla.lysator.liu.se/show_bug.cgi?id=341
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |1616
------- Comment #1 from ceder(a)lysator.liu.se 2014-04-22 22:41 -------
Once bug 1616 is done, there is potential to fix this using this method:
Replace the fparse_long_errors variable in ram-parse.c with a "Bool
err" field in struct dbfile. Use it consistently to report all sorts
of parse errors (and file errors?). Add dbfile_err() to check it and
dbfile_clearerr() to clear it. Make especially sure that text-store.c
uses it. Open issue: should it be named "parse_err" instead of "err"?
Probably.
--
Configure bugmail: http://bugzilla.lysator.liu.se/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1616
------- Comment #4 from ceder(a)lysator.liu.se 2014-04-09 23:08 -------
Now that the source code has been moved to Git, I'm working on this task in a
private fork of the official repo. See
http://git.lysator.liu.se/~ceder/lyskom-server/lyskom-server-1616-generation
for checkout instructions. I'm using successive branches named 1616-X; I'm
currently working on 1616-5.
(Locally, I'm using guilt to manage a patch series; the 1616-X branches are
used as backup, and they are also the way I move my work between computers if I
happen to develop on more than one computer.)
--
Configure bugmail: http://bugzilla.lysator.liu.se/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.