yes... things start to get complicated - for my situation - reading back I didn't point out
this isnt a new project - I'm maintaining a lot of existing code at high speed - or trying.
Thanks rvk - no wonder I couldnt find it - I was grep'ing for 'function readln' or procedure - damn.
My thinking on the readln idea was that readlin is already widely used in all the code
and each iteration it must already have identified an EOL. If I can patch it to store that
in a variable I dont actually have to mess with any existing code. This should be very simple
to do and can remain totally transparent to anything not using that (global) variable.
This just seemed a bit more elegant than patching in an entirely new custom function
Its just an idea - but I'll give it a go and see how it works out.
If nothing else this has reminded me to be wary of EOF markers (which had skipped
what little grey matter I have entirely).