Groups > dBase > dBase programming > Re: dBASE IV Compiler




dBASE IV Compiler

dBASE IV Compiler
Fri, 11 Apr 2008 11:24:20 -040
Posted a while ago on this, but can't find that now!
But, the manual says that macro subs., eg &NDIR for C:\dir1 or so
can't be used. Pity, as I have used this quite a lot.
Now, in a @filelist, can I have:
c:\myapps\prog\menu.prg
c:\myapps\prog\another.prg
etc.
Or must I move all files to the compiler directory?
Thanks
Post Reply
Re: dBASE IV Compiler
Sun, 13 Apr 2008 10:29:55 -040
In article <tvIOdg#mIHA.1380@news-server>, georgefour@yahoo.co.uk 
says...
> Posted a while ago on this, but can't find that now!
> But, the manual says that macro subs., eg &NDIR for C:\dir1 or so
> can't be used. Pity, as I have used this quite a lot.
>

Nonsense.  Macros work just fine in the compiler as long as the entire 
command isn't a macro.  In other words:

use &myfile.

works just fine.

cmd = 'use ' + myfile
&cmd.

doesn't.

-- 
Marilyn Price
Post Reply
Re: dBASE IV Compiler
Sun, 13 Apr 2008 11:29:42 -040
Marilyn Price Wrote:

> In article <tvIOdg#mIHA.1380@news-server>, georgefour@yahoo.co.uk 
> says...
> > But, the manual says that macro subs., eg &NDIR for C:\dir1 or so
> > can't be used. > >

> Nonsense.  Macros work just fine in the compiler as long as 
> the entire  command isn't a macro.  In other words:
> 
> use &myfile.
> 
> works just fine.
> 
> cmd = 'use ' + myfile
> &cmd.
> 
> doesn't.
> 
> -- 
> Marilyn Price
> M. P. Data
Many thanks for the correction.
I misunderstood the
       " BDC does not support  macro (&) substitution of   
         dBASE 'command' verbs."
With your comment, I have now re-read it.

Thanks again!
george

Post Reply
Re: dBASE IV Compiler
Mon, 14 Apr 2008 08:01:32 -040
In article <ze1rxsXnIHA.940@news-server>, georgefour@btinternet.com 
says...
> 
> Many thanks for the correction.
> I misunderstood the
>        " BDC does not support  macro (&) substitution of   
>          dBASE 'command' verbs."
> With your comment, I have now re-read it.
> 
> Thanks again!
>

You're not the first to misinterpret that sentence.  We've been 
clarifying it for quite a while....

-- 
Marilyn Price
Post Reply
about | contact