Re: Ping: frozen variable objects

Nick Roberts
2007-04-18T10:22:58Z

> > > It's Eli who decides, but having -var-update reference -var-set-frozen
> > > which in turn references -var-update seems too complicated, and
> > > shouldn't be necessary if there was a natural flow.
> >
> > I'm afraid I wasn't following this sub-thread closely enough, so
> > forgive me, Vladimir, if I ask what was already said: could you please
> > explain the rationale for your change of the anchors in this patch?
>
> You've asked to add a reference to -var-update. There was already
> -var-update anchor. However, that anchor was pointing in the middle of
> -var-update documentaiton, so following the reference would land the reader
> at list of some attributes, which would be confusing. And it seems that
> calling anchor for entire -var-update docs as -var-update is more reasonable
> then using -var-update anchor for the list of fields output by -var-update.
>
> Does this clarify things?

For this case, I suggested using the existing pxref with two arguments (three
might be better still).

However, you're now adding another pxref and anchor, and the point I tried to
make above was that it shouldn't be necessary to have circular references
within a single node.

(Actually, as a rule of thumb, I would say it's a good idea not to have
references within one node at all, as it's not unreasonable to expect the
reader to, at least, skip read the whole node. If it is unresonable then the
node is probably too long. However, I'm not suggesting to take the first one
out too.)

--
Nick http://www.inet.net.nz/~nickrob