Native Development

[dbigham]

struct timespec start, stop;
if(clock_gettime( CLOCK_REALTIME, &start) == -1)
{
fprintf(stderr, "ERROR GETTING TIME");
}

... long execution ...

if(clock_gettime( CLOCK_REALTIME, &stop) == -1)
{
fprintf(stderr, "ERROR GETTING TIME2");
}

fprintf(stderr, "Time: %f", (double)( stop.tv_nsec - start.tv_nsec ) / (double)1000000000.0F);

Using this to surround something that's taking about 3 seconds to execute is resulting in output such as:

Time: -0.743363

What gives?

[rcmaniac25 · Accepted solution]

Are you sure tv_sec isn't needed? I might be misinterpreting it, but it seems to have the number of seconds from Epoch, followed by the number of nanoseconds till the next second. If you are just comparing nanoseconds, you could be in a different second. Ex. 10sec 5000000nano->11sec 200000nano.

[dbigham]

Ah yes.  You are exactly right.  Thanks!

[BikeAtor]

You could also give a try to Qt for Playbook :-) It's better portable (Windows/Linux/Symbian/Meego+++), easy to use, well documented etc. Qt for Playbook is alpha or beta, but most things are running fluently and Cascades will be build upon it (as I understand the things). Here is the Code for Qt:

QTimer timer;
timer.start();
... long operation
timer.elapsed();