Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Profiler
#1
Hi All,

In GoodLiffe's book "Code Craft", he mentions the use of a profiler to identify areas where your code is slowing down and find places to optimize efficiency.

Is there any need for this in QM?

I geuss QM wasn't originally designed for small quick macros rather than really large programming jobs (is that right?, Gintaras...) but it's all I know and I have had great success with huge collections of macros working with each other (layering over multiple progams knitted together by QM).

Stuart
#2
"...and I have had great success with huge collections of macros working with each other (layering over multiple progams knitted together by QM)."


Indeed you HAVE!
An old blog on QM coding and automation.

The Macro Hook
#3
:oops: :oops:

Didn't mean to sound immodest. It was supposed to compliment Gintaras!!

Stuart
#4
Would be useful of course. But creating a QM profiler is extremely difficult task.


Forum Jump:


Users browsing this thread: 1 Guest(s)