>
>
> Even better would be the compiler's parser for the code that would just
> split out the major 'functional' segments that the code syntax already
> defines.
>
>
I agree with this assessment that having a compiler which can spit out meta
data about code or some kind of API to understand co
On 07/10/2021 10:04, Magnus Therning wrote:
>
> skybuck2000 writes:
>
>> Here is a "real-world" example:
>>
>> The original repository is this one:
>> https://github.com/PascalCoin/PascalCoin
>>
>> My restructured repository is this one:
>> https://github.com/SkybuckFlying/PascalCoinRestructured
>
skybuck2000 writes:
Here is a "real-world" example:
The original repository is this one:
https://github.com/PascalCoin/PascalCoin
My restructured repository is this one:
https://github.com/SkybuckFlying/PascalCoinRestructured
I only took a quick glance at the two repositories, but it seems
There is the class explorer in Delphi, never used it much, just tried it
after a few clicks it crashes the IDE.
Relieing on IDE to make sense of source code is a bad idea anyway. Source
code should be editable and easily searchable by windows explorer/textpad
any editor or file exploration tool
Vice versa could also be interesting:
git init
git remote add Restructured
https://github.com/SkybuckFlying/PascalCoinRestructured
git remote add PascalCoin https://github.com/PascalCoin/PascalCoin
git fetch Restructured
git fetch PascalCoin
git merge PascalCoin/master
git merge Restructured/mast
Here is a "real-world" example:
The original repository is this one:
https://github.com/PascalCoin/PascalCoin
My restructured repository is this one:
https://github.com/SkybuckFlying/PascalCoinRestructured
The original repository is a big mess and it's very hard to find any class
in it.
While
On Sunday, September 12, 2021 at 11:20:51 AM UTC+2 philip...@iee.email
wrote:
> Have you looked at the various --pickaxe and other file-following options
> that can be set to different levels of similarity for the tracking of such
> splitting and changing.
>
No.
> Sometimes the real probl
Have you looked at the various --pickaxe and other file-following options
that can be set to different levels of similarity for the tracking of such
splitting and changing.
Sometimes the real problem is that the 'local' feature branch policies
(i.e. your corporate way of doing things) can be in
