howdee, i am not quoting any text, because this note is OffTopic-ish...
i was looking at the comments from kshe regarding a full rewrite of the sed-utility... in particular, that there were obscure corner cases of tests that seemed to fail due to NULL or EOL or whatnot... apparently, sed is a Turing-complete language - and hence, given enough time/space/memory, will surely not give a single TRUE/FALSE answer to some questions... to be honest, i do not understand all of the details or theory, that are involved in the statements i _just_ made - but... since sed is a STREAM editor, and since sed-scripts are usually finite-length, then maybe there should be some way to enforce a limit (like was done for string-buffers) on the inputs... again, this is all just my pie-in-the-sky OT-commentary... sincerely, harold.
