On Friday 18 September 2009 07:54:55 am Paul McNett wrote: > John wrote: > > If the developer is moving from VFP it maybe easier to understand or > > read. But as the developer becomes used to reading python I see the > > opposite effect. > > Why does VFP have anything to do with this? Shorter strings, where each > communicates the same meaning, are going to be easier to read every time, > no matter what your background. > > Paul
VFP has nothing to do with this - just an example of a new developer mind set. I disagree with the last statement of easier to read. Take your example of isinstance. Any python developer will be able to recoginze what isinstance is doing - could even check the doc's. But what does isString() really do? Yes it's true that being an english reading developer I would know what it does from the name that implies description (but not how it worked or the required parameters). I have to look at the source code to know for sure. So I guess I'm saying you are replacing a python bulit-in that is well defined and understood by all with one that might might make it easier to read. Why not replace other built-ins with new names that maybe make them easier to read. Plus there is the added overhead of calling a method/function. Johnf _______________________________________________ Post Messages to: Dabo-users@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/200909180819.23159.jfabi...@yolo.com
