On Sat, Sep 09, 2006 at 12:44:23AM -0700, Andreas Raab wrote:
> Yoshiki Ohshima wrote:
> >  Has anybody mentioned to Rich that one of the reason is that the
> >compiled methods hold integer indice into .changes and .sources files?
> 
> This is not a valid reason (as are all the others in my opinion). 
> Transparent Cr/Lf handling does not prevent byte-oriented positioning 
> which is the only requirement for indexing sources and changes file. I 
> have advocated the use of CrLfFileStream since 1997 and nobody has ever 
> brought a technical reason forward why this wouldn't be feasible. I 
> still feel just as strongly as back then and it's plain incomprehensible 
> (in particular for source code) not to do CrLf conversion upon input. 
> Why would we *knowingly* screw up the source code with Lfs intermingled?

Is this something that should be done, and that just requires something
to decide to do it? If so, I'll enter a Mantis report so it does not get
forgotten for another 5 years.

Dave