Re: computing with characters
- From: Torsten Bronger <bronger@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Apr 2008 11:06:52 +0200
Hallöchen!
SL writes:
"Gabriel Genellina" <gagsl-py2@xxxxxxxxxxxx> schreef in bericht
news:mailman.365.1209541507.12834.python-list@xxxxxxxxxxxxx
En Wed, 30 Apr 2008 04:19:22 -0300, SL <ni@xxxxxxx> escribió: And
that's a very reasonable place to search; I think chr and ord are
builtin functions (and not str methods) just by an historical
accident. (Or is there any other reason? what's wrong with
"a".ord() or str.from_ordinal(65))?
yes when you know other OO languages you expect this. Anyone know
why builtins were chosen? Just curious
*Maybe* for aesthetical reasons. I find ord(c) more pleasent for
the eye. YMMV.
The biggest ugliness though is ",".join(). No idea why this should
be better than join(list, separator=" "). Besides, ",".join(u"x")
yields an unicode object. This is confusing (but will probably go
away with Python 3).
Tschö,
Torsten.
--
Torsten Bronger, aquisgrana, europa vetus
Jabber ID: bronger@xxxxxxxxxx
(See http://ime.webhop.org for further contact info.)
.
- Follow-Ups:
- Re: computing with characters
- From: George Sakkis
- Re: computing with characters
- From: Duncan Booth
- Re: computing with characters
- References:
- computing with characters
- From: SL
- Re: computing with characters
- From: Lutz Horn
- Re: computing with characters
- From: SL
- Re: computing with characters
- From: Gabriel Genellina
- Re: computing with characters
- From: SL
- computing with characters
- Prev by Date: Re: Simple TK Question - refreshing the canvas when not in focus
- Next by Date: Re: Sending Cntrl-C ??
- Previous by thread: Re: computing with characters
- Next by thread: Re: computing with characters
- Index(es):
Relevant Pages
|
|
