[VFP] VFP dialect macro compiler issues

[cpyrgas]

Following macro compiler expressions throw a macrocompiler error in VFP dialect only, with either /fox3+ or /fox3-

// Both with fox3+ and fox3-
//#pragma options("fox3", enable)

BEGIN NAMESPACE TestNS

CLASS TestFox
	STATIC EXPORT StaticExport AS INT
	STATIC PROPERTY StaticProperty AS INT AUTO
END CLASS

END NAMESPACE

FUNCTION Start() AS VOID
? &("System.Int32.MaxValue")
? &("TestNS.TestFox.StaticExport")
? &("TestNS.TestFox.StaticProperty")

/*
XSharp.MacroCompiler.CompilationError
Macrocompiler (1,59): error XM0222: 'TestNS.TestFox' is not a valid expression term
*/

[RobertvanderHulst]

I will roll back my changes (the MPrepare) and fix this in the macro compiler itself.

One question:
Given the expression Foo.Bar, when does the macro compiler check if Foo is a cursor?

• During the compilation where the code is converted to IL
• When evaluating the code where the IL is executed

In the last case, it is probably the easiest if I generate 2 sets of code in the macro compiler and store them both in one object. Then at runtime we can check to see if there is a cursor with that name.
However, how would I do this for Foo.Bar + Foo2.Bar2. There are 4 possible combinations here...

[cpyrgas]

Robert, can't the macrocompiler work in exactly the same way as the regular compiler? Let everything in this case be resolved at runtime, when /fox3 is enabled?

Btw, after seeing a lot of VFP code, I don't think we can ever get away from /fox3. The only possible reason for not using it in the VFP dialect would be if someone wants to write new code with in the VFP dialect in a modern way, but then why would they use the VFP dialect...

[RobertvanderHulst]

Chris,
Yes, the macro compiler can do that too. It's just that I need to figure out how Nikos has implemented this and insert the right logic.

[cpyrgas]

Maybe Nikos can step in? @nvkokkalis ?

[nvkokkalis]

Yeah I'll check it today!