John Macdonald <jmm@elegant.com> writes: >Nick Ing-Simmons wrote : >|| John Macdonald <jmm@elegant.com> writes: >|| >|| >|| >|| That is far from daft. sv_gets() (the internals of readline) would know >|| >|| what it had used to find the end of the line. It could leave the >|| >|| information around for chomp to use. >|| > >|| >But as soon as you have a program that opens multiple files of >|| >differing formats, this breaks down. You end up with taint-like >|| >tracing of strings to track which form of file each string came >|| >from. >|| >|| Yes, the EOLN string would have to be annotated on the SV somewhere >|| presumably as "magic". Having chomp look for "EOLN magic" on the SV >|| would be easy to do. The 'set' part of the magic would clear the field. > >It gets messier... > > $para = "$file1_lines$file2_lines$file3_lines"; > >Which of the three EOLN magics gets assigned to $para? In my purely fictional implementation none would. -- Nick Ing-Simmons <nik@tiuk.ti.com> Via, but not speaking for: Texas Instruments Ltd.Thread Previous | Thread Next