SET COVERAGE TO at runtime?

Hi Everyone,

Can't we "SET COVERAGE TO MyFile" at runtime? I've built an .EXE and am
trying to capture a condition that occurs only when running as an .EXE, but
no log file is ever created and no error fires saying that SET COVERAGE is
an invalid command. BTW - debug info is included in the .EXE.

Thanks.

--
William Fields
MCSD - Microsoft Visual FoxPro
MCP - Win2k Pro
US Bankruptcy Court
Phoenix, AZ

The secret to creativity is knowing how to hide your sources.

- Albert Einstein

Dan
Tue Jul 01 10:39:24 CDT 2003

Interesting.

It makes sense for coverage not to work in an exe because there's no source,
but it's not mentioned in the help file at all. Nowhere.

Dan


"William Fields" <Bill_Fields@azb.uscourts.gov> wrote in message
news:uB5Yc52PDHA.1216@TK2MSFTNGP11.phx.gbl...
> Hi Everyone,
>
> Can't we "SET COVERAGE TO MyFile" at runtime? I've built an .EXE and am
> trying to capture a condition that occurs only when running as an .EXE,
but
> no log file is ever created and no error fires saying that SET COVERAGE is
> an invalid command. BTW - debug info is included in the .EXE.
>
> Thanks.
>
> --
> William Fields
> MCSD - Microsoft Visual FoxPro
> MCP - Win2k Pro
> US Bankruptcy Court
> Phoenix, AZ
>
> The secret to creativity is knowing how to hide your sources.
>
> - Albert Einstein
>
>
>

Igor
Wed Jul 02 05:23:50 CDT 2003

Hi, Dan!
You wrote on Tue, 1 Jul 2003 08:39:24 -0700:

DF> It makes sense for coverage not to work in an exe because there's no
DF> source,

AFAIK there is no need in avaliable sources for coverage to work - it only
need SECONDS(), PROGRAM() and LINENO() so there is no insuperability in
adding this feature to runtime support dlls...

DF> but it's not mentioned in the help file at all. Nowhere.

I suppose MS have to be more specific on this point - either raise "Feature
Not Avaliable" error, either add Coverage support to runtime...

WBR, Igor

William
Wed Jul 02 11:59:11 CDT 2003

I ran across something in the help file under "Language Supported in Run
Times".

Disabled Commands that Generate No Run-Time Errors

The following table is a list of unsupported commands, which will not
generate an error when executed at run time in vfp8t.dll library. These
functions are still disabled for use in the run time; however, because of
the frequency of usage in commonly used code and class libraries between
different types of applications, they do not cause an error. When one of
these commands or functions is encountered in code, Visual FoxPro ignores
that line of code and continues executing. This includes certain SET
commands and SYS functions.

Specifically, they list SET COVERAGE as an unsupported command. That's
unfortunate, it's going to make my debugging more difficult now.


--
William Fields
MCSD - Microsoft Visual FoxPro
MCP - Win2k Pro
US Bankruptcy Court
Phoenix, AZ

The secret to creativity is knowing how to hide your sources.

- Albert Einstein


"Igor Korolyov" <k1i2v3@km.ru> wrote in message
news:%23%237Y0aIQDHA.3192@tk2msftngp13.phx.gbl...
> Hi, Dan!
> You wrote on Tue, 1 Jul 2003 08:39:24 -0700:
>
> DF> It makes sense for coverage not to work in an exe because there's no
> DF> source,
>
> AFAIK there is no need in avaliable sources for coverage to work - it only
> need SECONDS(), PROGRAM() and LINENO() so there is no insuperability in
> adding this feature to runtime support dlls...
>
> DF> but it's not mentioned in the help file at all. Nowhere.
>
> I suppose MS have to be more specific on this point - either raise
"Feature
> Not Avaliable" error, either add Coverage support to runtime...
>
> WBR, Igor
>
>