Skip to main content

Runtime Coverage - another VFP 9 Rocks Feature!

Yesterday, I came across another reason why VFP 9 totally rocks above older versions.

I've been aware of it for a while but it struck me at once as to how useful this is, especially at customer sites.

SET COVERAGE TO lets you track how long each line of code is taking. It's used by the VFP Coverage Profiler for both seeing how much of your code you are using and how long it takes.

SET COVERAGE TO xxx.LOG turns it on and outputs all code execution to xxx.log
SET COVERAGE TO turns it off.

In VFP 8 and earlier, you had to be running the Development version of VFP to see the results. This has its problems - as usually, the problems never seem to occur on the Developer's machine but on the end-user's machine.

In VFP 9, however, you can issue a SET COVERAGE TO statement and it will start logging the code even in runtime!

This became extremely valuable yesterday when we were debugging a program that was running as a Windows XP service. It would stop running and we couldn't figure out why. Instead of just providing additional logging messages and overbloating the code - I issued a SET COVERAGE TO in one of the programming hooks I had put into the code and voila! instant access as to what was running and when.

You wouldn't want to do this on a regular basis - running with COVERAGE turned on can create a very large file in a matter of seconds - so be sure to turn it off. But what a benefit to have at the right time!

I also used it earlier this week to track down some performance problems that only seemed to be happening at a customer site. Many times, developers think of debugging tools as to be only accessible within the IDE. Thankfully, in VFP 9, your code can be covered just about wherever it needs to be.



powered by performancing firefox

Comments

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…