02-01-2008, 03:04 PM
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
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