IronPython is going to be called "Dynamic Language Foundation Whitespace Sensitive Edition", so we are not going to have this IP acronym confusion.
On Tue, Nov 18, 2008 at 12:28 PM, Michael Foord <[EMAIL PROTECTED]>wrote: > Keith J. Farmer wrote: > >> >> Respectfully: it would be less trouble overall if you made the effort to >> adapt to the group's jargon, rather than expect everyone else to adapt to >> your (temporary) state of confusion. >> >> > +1 (I'm afraid) > > From context it should be reasonably straightforward to tell whether an > acronym refers to TCP/IP or IronPython. Try finding any TLA that isn't > overloaded with multiple meanings in the computer world... > > Michael > > After all, I've never met a "simple" programmer. I'm sure you're capable >> of learning the language J >> >> *From:* [EMAIL PROTECTED] [mailto: >> [EMAIL PROTECTED] *On Behalf Of *Vernon Cole >> *Sent:* Friday, November 14, 2008 11:32 AM >> *To:* Discussion of IronPython >> *Subject:* [IronPython] Please use IPy, not IP. >> >> I am having trouble reading "subject" lines recently... >> IP is Internet Protocol as in TCP/IP. >> To keep simple folks like me from being confused, *IPy *would be a better >> acronym. >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com >> >> > > > -- > http://www.ironpythoninaction.com/ > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > -- nomadlife.org
_______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
