On 05/29/2014 05:47 AM, Tom Lisjac wrote:
I'm having a little trouble understanding where new functionality is needed for your use case.
Of course you are right that I don't exactly need it. In my source code I use a {§ifdef to decide whether or not to create an instance (my current source of epiktimer.pas allows for both, I just added the code that allows for statistically using the class functions).
OTOH, the discussion in the fpc-pascal mailing list shows that the low level / arch dependent stuff should be removed from epiktimer.pas and moved into a new file that at best would finally be integrated in the rtl. My ActiveNoGUI stuff will just call this basic function(s) and hence be independent of epiktimer.pas. I will offer a version of epiktimer.pas plus an additional low level file using vDSO in Linux) as soon as I find the time to do some testing. This will not break anything !
With the existing code, you don't need to create an EpikTimer instance each time you need a new timer.
In fact I don't need any "timer" at all. I just need to read a reliable (not to be modified behind our back as GetTimeOfDay) time counter that can be read with as little overhead as possible. And finally this should be available for all archs and done by an arch independent call and (this is why a am greatly interested in "EpikTimer" be used as broadly as possible, so that it hopefully is well supported in future.
-Michael -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
