Re: [Groff] understanding groff's source code

2014-09-29 Thread Ulrich Lauther
On Mon, Sep 29, 2014 at 09:05:48AM +0100, Ralph Corderoy wrote: > Hi Ulrich, > > > In case of questions, should one ask on the list > > I'd say ask here; answers would be part of the public record. These > answers are all based on a quick look; I don't know they're correct. > > > However, not

Re: [Groff] understanding groff's source code

2014-09-29 Thread Werner LEMBERG
> I am trying to read and understand groff source code, which is - at > least for me - not easy. In case of questions, should one ask on > the list or are there specialists who are able and willing to help? Please ask here. > And btw. why is node_list in input.cpp but delete_node_list() in > no

Re: [Groff] understanding groff's source code

2014-09-29 Thread Ralph Corderoy
Hi Ulrich, > In case of questions, should one ask on the list I'd say ask here; answers would be part of the public record. These answers are all based on a quick look; I don't know they're correct. > However, not so for extract(). node *node_list::extract() { node *temp = head

[Groff] understanding groff's source code

2014-09-28 Thread Ulrich Lauther
Hi, I am trying to read and understand groff source code, which is - at least for me - not easy. In case of questions, should one ask on the list or are there specialists who are able and willing to help? An example: In input.cpp there is a linked list class "node_list". Member functions are n