Lennart Regebro wrote: > On Tue, Apr 3, 2012 at 08:03, Cameron Simpson <cs at zip.com.au> wrote: >> clock = get_clock(MONOTONIC|HIRES) or get_clock(MONOTONIC) >> >> If the symbol names are not the horribleness, can you qualify what API >> you would like more? > > Well, get_clock(monotonic=True, highres=True) would be a vast > improvement over get_clock(MONOTONIC|HIRES). Allowing get_clock(True, True)? Ick. My nomination would be get_clock(MONOTONIC, HIGHRES) -- easier on the eyes with no |. > I also think it should > raise an error if not found. The clarity and easy of use of the API is > much more important than how much you can do in one line. What's unclear about returning None if no clocks match? Cheers, ~Ethan~
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