On Fri, Oct 1, 2010 at 18:56, Brandon McCaig <bamcc...@gmail.com> wrote: > On Fri, Oct 1, 2010 at 1:07 AM, Chas. Owens <chas.ow...@gmail.com> wrote: > >> Okay, here is what I think happened: you were print a carriage return. > > I thought that Mac OS X used UNIX newlines though (though I'm not a > Mac user). :-/ So shouldn't "\n" be interpreted as an LF (0x0A) on > Macs, the same as it would in other unices? > > -- > Brandon McCaig <bamcc...@gmail.com> > V zrna gur orfg jvgu jung V fnl. Vg qbrfa'g nyjnlf fbhaq gung jnl. > Castopulence Software <http://www.castopulence.org/> > <bamcc...@castopulence.org> >
OS X does use UNIX newlines and the \n is 0x0A on that platform. I don't know how he got a carriage return in there, but it is the only unexpected control character in his code and it fits the behavior. -- Chas. Owens wonkden.net The most important skill a programmer can have is the ability to read. -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
