Thanks,
Good news is that X# in its current version is mapping TEXT/ENDTEXT to an internal function... See personal communication regarding the command with Robert.
TEXT .. ENDTEXT is also parsed and send to a function with the name "__TextSupport". That function is not included in the runtime yet, but if you include that function in your code then it works.
So in short, this will be supported by X#, the internals are just not yet implemented, but will be with the final release of VFP support. If somebody interested, it can be developed by a community member as part of the opensource runtime...
Regards,
Johan.
On 2019/06/27 17:08, MB Software Solutions, LLC wrote:
Steve Ellenoff and I were talking the other day about the beauty of TEXTMERGE (TEXT/ENDTEXT) and iirc he indicated that wasn't in DotNet (or earlier versions anyway). I use TEXT/ENDTEXT *HEAVILY* in code often.
On 6/27/2019 8:51 AM, Johan Nel wrote:
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:
- Macro-compilation
- Evaluate(<script>)
From a X# perspective the FOX release already has support for:
- 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]