Re: Is it bad style to override the built-in function `type`?

2012-12-03 Thread Michael Herrmann
Hi Rusi, > Im entering this thread late (was off mail for a week), so pardon me > if someone has already said this -- but have you looked at the > difference between internal and external dsls: > http://martinfowler.com/bliki/DomainSpecificLanguage.html (and links > therein) ? > Roughly speaking

Re: Is it bad style to override the built-in function `type`?

2012-11-29 Thread Michael Herrmann
Hey everyone, this is my final mail. With all your help we have decided on names for our function. It was a surprisingly difficult process but your inputs helped tremendously. I have described our experiences (very good ones here, but somewhat mixed ones with StackOverflow) in a blog entry: ht

Re: Is it bad style to override the built-in function `type`?

2012-11-24 Thread Cameron Simpson
On 25Nov2012 04:06, Steven D'Aprano wrote: | On Sat, 24 Nov 2012 14:32:19 -0800, Michael Herrmann wrote: | > how about "write" instead of "type"? Just came to me in a flash of | > inspiration. I know it's also pretty general but at least it's not a | > built-in! | | "write" is an extremely commo

Re: Is it bad style to override the built-in function `type`?

2012-11-24 Thread Steven D'Aprano
On Sat, 24 Nov 2012 14:32:19 -0800, Michael Herrmann wrote: > Hi, > > how about "write" instead of "type"? Just came to me in a flash of > inspiration. I know it's also pretty general but at least it's not a > built-in! "write" is an extremely common operation with a signature very similar to t

RE: Is it bad style to override the built-in function `type`?

2012-11-24 Thread Graham Fielding
(This comes from my experience writing interactive fiction with the TADS workbench; YMMV) As a rule, it's generally unwise to modify built-in variables without thoroughly documenting your changes. Your modifications might not hold up if the built-in definitions are revised (which would break y

Re: Is it bad style to override the built-in function `type`?

2012-11-24 Thread Cameron Simpson
On 24Nov2012 14:32, Michael Herrmann wrote: | how about "write" instead of "type"? Just came to me in a flash of inspiration. I know it's also pretty general but at least it's not a built-in! +1 -- Cameron Simpson Cars making a sudden U-turn are the most dangerous. They may cut you off entir

Re: Is it bad style to override the built-in function `type`?

2012-11-24 Thread Michael Herrmann
Hi, how about "write" instead of "type"? Just came to me in a flash of inspiration. I know it's also pretty general but at least it's not a built-in! Thanks! Michael On Friday, November 23, 2012 11:30:18 PM UTC+1, Cameron Simpson wrote: > On 23Nov2012 10:41, Michael Herrmann <> wrote: > > [...

Re: Is it bad style to override the built-in function `type`?

2012-11-23 Thread Cameron Simpson
On 23Nov2012 10:41, Michael Herrmann wrote: [...] | I know it's a common beginner's mistake to incautiously override | built-in functions. However, we put in a lot of research and have come to | the conclusion that, if Python had not already defined it, `type` would | be the best name. We are now

Re: Is it bad style to override the built-in function `type`?

2012-11-23 Thread Terry Reedy
On 11/23/2012 11:22 AM, Joel Goldstick wrote: On Fri, Nov 23, 2012 at 11:12 AM, Michael Herrmann mailto:michael.herrm...@getautoma.com>> wrote: Hi, do you think it's bad style to override the built-in function `type`? I'm co-developing a GUI automation library called Automa (

Re: Is it bad style to override the built-in function `type`?

2012-11-23 Thread Roy Smith
In article , Michael Herrmann wrote: > do you think it's bad style to override the built-in function `type`? I'm > co-developing a GUI automation library called Automa > (http://www.getautoma.com) and 'type' would be a very fitting name for a > function that generates artificial key strokes.