Movatterモバイル変換

GetTickCount vs. clock for msec resolution

• Previous message (by thread):GetTickCount vs. clock for msec resolution
• Next message (by thread):best way to take vertical slices from a matrix?
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

On Fri, 20 Apr 2001 01:38:25 -0400, "Tim Peters" <tim.one at home.com>wrote:>In any case, don't mistake resolution for accuracy.  You didn't ask about>accuracy <0.5 wink>.accuracy not an issue for me at all at this point on this project.based on what i read on this thread, if accuracy or smaller resolutionwere important to me, i'd put the timing junk and the serial readsdown in a C extension. i am just about finished rewriting a C++ serial communications module,for a test instrument i am working on, into Python code. its just_incredible_ how much more understandable and sane the python code isover the C++ stuff.  doing the re-write even helped me find bugs inthe C++ serial port code that were hard to track down before. so evenif i never use the Python version, it was still worth doing. virtualfefactoring, i guess.les schaffer

• Previous message (by thread):GetTickCount vs. clock for msec resolution
• Next message (by thread):best way to take vertical slices from a matrix?
• Messages sorted by:[ date ][ thread ][ subject ][ author ]