RetroSearch Browse

Tue Oct 2 02:10:40 CEST 2007 · http://mail.python.org/pipermail/python-dev/2007-October/074832.html

Guido van Rossum wrote:
> The best solution for IronPython is probably to have the occasional
> wrapper around .NET APIs that translates between \r\n and \n on the
> boundary between Python and .NET;

That's probably true. I was responding to the notion
that IronPython shouldn't need any wrappers. To make
that really true would require IronPython to become
a different language that has a different canonical
representation of newlines.

It's fine with me to keep things as they are.

-- 
Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	   | Carpe post meridiem!          	  |
Christchurch, New Zealand	   | (I'm not a morning person.)          |
greg.ewing at canterbury.ac.nz	   +--------------------------------------+

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2007-October/074832.html below:

New lines, carriage returns, and Windows