Recent

Author Topic: Dumping preprocessed working trees  (Read 1187 times)

Чебурашка

  • Hero Member
  • *****
  • Posts: 593
  • СЛАВА УКРАЇНІ! / Slava Ukraïni!
Re: Dumping preprocessed working trees
« Reply #15 on: February 09, 2026, 04:27:58 pm »
Thanks to all for the suggestions.

Alternative: You can pre-process the sources.

Put a {$warning this is line xyz} after each {$IF}.

Then when you compile collect the warnings. And you know what was compiled.
(and that works for var/type blocks too)

At the moment I am strongly evaluating an implementation based is this suggestion.

Pipeline:

  • make a full copy of the questioned working tree (repeatable everytime master code changes)
  • preprocessing in order to add suitable and identifiable warnings in corrspondence of the beginning of each conditional branch (again freely repeatable on fresh sources)
  • build with each Master into separate compiler output log
  • stripping the output log in order to keep only the support warnings created at step 2
  • creating a proximity matrix with some distance still to be defined, could be, for every unit the number of matches/differences, I dont know yet
  • creating clusters of Master defines

We'll see.
FPC 3.2.0/Lazarus 2.0.10+dfsg-4+b2 on Debian 11.5
FPC 3.2.2/Lazarus 2.2.0 on Windows 10 Pro 21H2

 

TinyPortal © 2005-2018