VFP cursors are under discussion and will be supported, one way or the
other.
There are obviously some .NET features like DataSet/DataTable/DataReader
that are all
under scrutiny to see how these VFP specifics will/can be accommodated.
As you say, some of these we learn of everyday, same goes for me using
X#/.NET
and it is up to the community to assist in resolving these once the
public VFP support is
released. Again, first things first, get the basics in place then we as
community in
partnership with the DevTeam can sort out the outstanding more "unused"
features. It
is already clear now that the core of the language is stable, how quick
the DevTeam is
responding on fixing detected issues...
Johan
On 2019/06/27 18:53, Paul H. Tarver wrote:
I would greatly miss the speedy import capabilities of Foxpro and the CREATE
CURSOR to build temporary files to temporarily hold imported data. I also
make extensive use of Class Libraries. More and more I'm using of creating
Empty Objects and adding properties to store and manage lots of variables
including making it possible to pass a single reference to the object as a
parameter and making all of the properties available to other modules. And I
agree 100% with wanting to keep the TEXTMERGE feature.
I think I could do this all day and because it seems I'm still learning new
ways to use VFP commands and features, I think I fear losing any of them!
Paul H. Tarver
-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of Johan
Nel
Sent: Thursday, June 27, 2019 7:52 AM
To: [email protected]
Subject: [NF] What would you miss from VFP, when migrating
Hi VFPers
I have asked this question on foxite too with very little feedback, so I
am asking it here too.
If you have to summarize the 1 or 2 features of VFP that you will feel
is a step backwards when migrating to .NET or any other platform as a
move forwards.
Looking forward to your replies.
Two things that was highlighted on Foxite:
1. Macro-compilation
2. Evaluate(<script>)
From a X# perspective the FOX release already has support for:
1. DBFCDX and readonly access for VFP specific FieldTypes (AutoInc, etc)
with full support planned in the foreseeable future;
2. WITH/ENDWITH, TEXT/ENDTEXT (partially implemented);
3. Macro-compilation;
4. Script engine that can make full use of the .NET framework.
XBase greetings,
Johan Nel
FOX Member: Friends of XSharp
https://xsharp.info
George, South Africa
[excessive quoting removed by server]
_______________________________________________
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: https://leafe.com/archives
This message:
https://leafe.com/archives/byMID/[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.
