Fernando D. Bozzo wrote on 2017-02-21:
> The only adventage of using VCXs over PRGs is that: - Descriptions of
> the methods and properties are shown by intellisense when you scroll
> them while using an instantiated class, which is not possible with
> PRGs, except PRG-COM classes instantiated from the registered Windows
> object. - Can be created (NewObject) from external exes/apps (with PRGs
> just the main program with SET PROCEDURE)
>
> On the other side, PRGs have plenty of adventages over VCX:
> - The text never gets corrupted
> - You can define the type of procs/funcs parameters and their returned
> values (useful for COM)
> - Better for merging in a SCM/DVCS tool
> - It is the only way to use the Session class
> - Easier for bach-replacing between a bunch of files (you can do that
with
> the tx2 versions generated by FoxBin2Prg, but then you need to regenarate
> the binaries, which is an extra step)
>
> Fernando D. Bozzo
>
>
>
Fernando,
A PRG based class can be created from an external exe.
I have a couple of executables than instantiate PRG based classes in the
main executable.
oObject = newobject({classname}, {prgfilename}, {executable})
Tracy Pearson
PowerChurch Software
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
