At 06:36 2017-02-21, "Fernando D. Bozzo" <[email protected]> wrote:
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.
No loss for me. IMHO, Intellisense is too close to copy-paste. It is too easy to get something that looks reasonable yet might not be right. If you are not sure, look it up.
- 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
Almost never gets corrupted. I have had minor text corruption very occasionally. It is much easier to correct though.
- 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)
I code almost only with .prg files (so I do not know what most of the above means). The only exception was setting printer orientation for which I had to create two .frt files.
[snip] Sincerely, Gene Wirchenko _______________________________________________ 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/2c18770a8dac190fb261d6c5dad1fd43@mtlp000086 ** 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.
