A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-April/014042.html below:

[Python-Dev] s1 == (sf % (s1

[Python-Dev] s1 == (sf % (s1 / sf))? A bad idea? [Python-Dev] s1 == (sf % (s1 / sf))? A bad idea?Jeremy Hylton jeremy@alum.mit.edu
Tue, 3 Apr 2001 21:39:28 -0400 (EDT)
>>>>> "SM" == Skip Montanaro <skip@pobox.com> writes:

  Jeremy> I imagine something like this:

  Jeremy> import fileinput import scanf

  SM>     ...

  SM> Placing the functionality in a module is fine as well, but
  SM> again, "scanf" only means something if you've programmed in C
  SM> before.  I suspect there are college students graduating from CS
  SM> departments now who have used C++ but not C and wouldn't have
  SM> the slightest idea what "scanf" means.

I don't care much about the name.  scanf is fine with me ("scan with
format") but so is "scan" -- or "parrot."

I do care about it being based on a module rather than a builtin
operator or a string method.  I see scanf-based scanning as roughly
equivalent to regular expressions, which live happily in a module.

If we're going to add a scan method to strings, I can imagine people
wanting "\d+".re_match() and "\d+".re_search() methods on strings,
too. 

Jeremy



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4