[Pasdoc-main] [pasdoc:feature-requests] #60 Follow nested record types

[Colin H. <ahy...@us...>]

Since the link tag can link to fields, should it not also be able to link to fields of nested records (which are essentially  fields of the parent record, but with a hierarchical name)? Only having to write the name of the field would make the documentation far easier to maintain.

I'd agree the two cases you've shown in your class testcase look like bugs.


---

** [feature-requests:#60] Follow nested record types**

**Status:** open
**Group:** 
**Created:** Mon Dec 31, 2018 07:01 AM UTC by Colin Haywood
**Last Updated:** Mon Dec 31, 2018 04:03 PM UTC
**Owner:** nobody


Easiest explained with an example:

~~~
  // Record Two.
  TRecord2 = record
    // An exciting value.
    a: integer;
  end;

  // Record One.
  TRecord1 = record
    // The record2.
    Two: TRecord2;

    // Must be @true if @link(Two.a) is bigger than @code(10).
    x: boolean;
  end;
~~~

The pasdoc parser complains that it can't understand the link "Two.a":

`Warning[1]: Could not resolve link "Two.a" (from description of "pasdocrecordtest.TRecord1.x")`

It seems pasdoc can only identify fields of top-level records by name, not fields of nested records. This is a shame, as it means you have to refer to nested fields by their parent types, which is much less clear for  the end-user. Hopefully it would not be too hard to add the ability to follow chains of nested records by their field names.


---

Sent from sourceforge.net because pas...@li... is subscribed to https://sourceforge.net/p/pasdoc/feature-requests/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/pasdoc/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.