|
From: Michalis K. <ka...@us...> - 2026-03-30 01:29:23
|
We have improved parsing nesting structures and linking to them in PasDoc 1.0.0, see https://github.com/pasdoc/pasdoc/blob/master/ChangeLog.md . So this should be fixed, please retest. If anything remains missing, please report on GitHub issues, https://github.com/pasdoc/pasdoc/issues . Thank you! --- **[feature-requests:#60] Follow nested record types** **Status:** open **Group:** **Created:** Mon Dec 31, 2018 07:01 AM UTC by Colin Haywood **Last Updated:** Tue Jan 01, 2019 12:08 AM 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. |