On 15/02/19 14:55, Udo Munk wrote:
> That's what ed and sed are for :)
I dunno about detail of your work, but editing is by definition an
interactive work, and sed, ed, awk and even perl can do an excellent
work on more or less static data (.ASM files) but isn't pleasant finding
having missed HBLANK or VBLANK by an handful of cycles... aside keeping
track of the differences between PAL and ntsc...
your solution is fine, even excellent, when analysing sources, but add
an IMVHO unnecessary step in the coding-assembling-debugging cycle.
add on top of it that I have always preferred size to speed (I find
gratifying having saved one 128-byte sector in a .COM file...) and I'm
not precisely well-versed in working for speed (being Italian has his
perks, if you have tasted our coffee you will get another reason for the
proverbial Italian "laziness" ;) ) and two or three more minutes of
computing was never an issue for me.