4 ms·

Edit: Never mind, whartung enlightened me in a sibling comment. Leaving the egg on my face for posterity below. --- Why do you want to change all the files? T

Edit: Never mind, whartung enlightened me in a sibling comment. Leaving the egg on my face for posterity below. --- Why do you want to change all the files? The license only says you have to change the names of files that you modify. It's a pretty weird term. If for some reason you were determined to change the names of all files then you ought to be able to create a plugin that walks the tree of classes and invokes the refactoring capabilities of the IDE to make the change. It's a strange use-case though so I'm not really surprised there isn't a ready tool for it.

thangalin 4y ago
> Why do you want to change all the files? Ever pull on a thread to unravel an entire sweater? Imagine wanting to add an SVG typesetter. To do this, the interface implemented by the DVI typesetter needs to be extracted and generalized so that it works for both SVG and DVI (to maintain existing behaviour). The `Typesetter` interface is used by, for example, `BaseNode`, so any changes to that interface could touch `BaseNode`. Changes to `BaseNode` can affect all `*Node` classes, which then cascade over to `*Noad` and `*Prim` classes, and from there the rest of the source base.