The philosophy is that you have a function that is called and if you have:
TEXT TO mVar <optional params> .... ENDTEXT
Internally it translate to:
mVar := __TextWhatEver(<optional params>)
So the function internally will handled based on the parameter list what needs to be done to the string.
On 2019/06/27 21:43, Stephen Russell wrote:
Am I missing something about TEXT/ENDTEXT where it just mashes up a string for you for whatever transpires within the loop?
What do you do with that output or the textmerge when you are done with it?
On Thu, Jun 27, 2019 at 10:09 AM MB Software Solutions, LLC < mbsoftwaresolutions@mbsoftwaresolutions.com> 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]