xsharp.eu

FoxProMatt_MattSlay wrote: Remember, in FoxPro, these DBFs do not have to be open first... If there is no Alias already alive with these table names, VFP will do a USE to open the DBFs, and leave them open.

robert wrote:Thomas,
You are right, Roslyn provides that. We also have "X# Sscript" support, but the scripting does not support dialects yet (so it runs in pure X# Core).
I'll discuss with Nikos if we can add dialect support in the scripting engine. When we can then we can certainly support compile() and execscript().

#R "XSharp.Core"
#R "XSharp.RT"
#R "XSharp.VO"
#include "c:xsharpincludedbcmd.xh"
#include "c:xsharpincludeset.xh"

USING STATIC xSharp.Core.functions
USING STATIC xSharp.RT.functions
USING STATIC xSharp.VO.functions


// ------------------------

SET EXCLUSIVE OFF

LOCAL cDBF AS STRING

cDBF := "D:testxsharp.dbf"

// USE "D:testxsharp.dbf" NEW VIA "DBFCDX" ALIAS  "XSHARP1"

dbUseArea ( .T. , "DBFCDX" , cDBF , "XSHARP1" ) 

dbusearea ( .T. , "DBFCDX" , cDBF , "XSHARP2" )

GO BOTTOM

SKIP -4


? "list content of Field no. 1"
? "---------------------------"
?

do while ! eof()

	? Fieldget ( 1 ) 
		
	SKIP 1 // dbskip (1)

enddo 


SELECT 1
? Alias()  

SELECT 2
? Alias()  


CLOSE DATABASES  // DBCloseAll()

SELECT a
? Alias() 

SELECT b
? Alias()


?
?

// Console.WriteLine ("press any key" ) 
// Console.Read() 

robert wrote:You'll be able to contribute in a few weeks. After finishing the current build I will add function prototypes for all the functions from the list to the source and I will also create a xml file for the documentation of these functions.
I'll write a small tool to extract the documentation from the VFPX help project (will give them credits of course) so we can fill the help fairly quickly.
After that you can start filling in functions, either by copying the implementation from the toolkit or by writing it yourself.

Please give me a few weeks (let's say Jan 1st) to set this up.

And they use their own classes and tables to live without the DBC features. But without DBC you don’t have long field names and some other features..
BR Rainer

robert wrote: - The keyfiles are in the right location if you compile with VS. Chris is the only one in our team that works with XIDE. You should ask him what to change to get the XIDE code to run. I can imagine that the Runtime.xiproj file needs to be updated, since I have added some new files since it was last updated in October 2019.

robert wrote: - When you install X# then we install the runtime files in the GAC. When testing you have to make sure that you are testing with the updated runtime and not with the files from the GAC. That's why there is an option to NOT install the runtime in the GAC in the installer.

robert wrote: What we really like:
- Strongly type the return values of all functions (when multiple return types, type as USUAL)
- Strongly type the parameters when all parameters are mandatory
- For optional parameters add checks and throw an exception for incorrect parameters. You can also call runtime functions such as EnforceNumeric() and EnforceString(). Or you check with IsString(), IsNumeric() etc.
- Make sure you test "edge" cases in the implementation, such as empty strings, negative numbers etc.
- Use as much "standard .Net" code as possible. For example for the Just..() functions I have used the normal methods in the System.IO.Path class to retrieve extensions and filenames. I did not write a "parser" for this. I have also not hard coded the directory separator in "AddBs" (even though the name implies a backslash) because on non windows platforms this might be a forward slash instead of a backslash.