Sorry if some of this might look a bit disjointed, with our SA electricity crisis I don't want to spend time explaining too much here, but want to focus on producing code. I can at anytime be notified the energy demand in SA surpasses supply capability, and depending the deficit end up with upto 3 x 2.5hr power shutdown blocks in a day. Luckily so far, Stage 1, SA is ok, use sparingly, we monitor but can announce Stage 2 - 5 implemented with immediate effect. It is a bit of a nightmare, but we managing...Karl-Heinz wrote: on GitHub i´ve found the UDC file dbcmd.xh . Wouldn´t it make sense to add it to the XSharp setup and install it in the include dir ?
https://github.com/X-Sharp/XSharpPublic ... n/dbcmd.xh
We have a bit of spaghetti communication going on here. Matt and I are already busy with something. I have shared the Clipper *.ch files with him, hence we are both aware of the #command feature. It is just a bit early to share all the information with Matt yet, there are a couple of background processes we need to first sort out, before I will get him into "pre-proccessor programming". I have already started a separate VFP.xh for commands not covered yet. E.g. Scan / EndScan, ADD OBJECT, TEXT/ENDTEXT etc. Some of these are still very crude e.g. TEXT/ENDTEXT only understand Single Line text, but I can look at the /ppo output and see what needs to be done to make X# understand. These I will discuss with the DevTeam, how it will be understood by X# and then I write an interim wrapper "HelperUtility" in producing the desired X# syntax before saving it in the X# "Transported" target. We busy demystifying the VFP repo. First phase was Matt producing a TXT version of the VFP repo in a Vertical structure with Markers that is then used by our X# "VfpTransporter" to convert to a "X# style" repo. This is probably 80+% completed. We modifying the output slightly maybe to make the Transporter understand it easier, very similar to how XIDE store Projects/Applications/Application/References/PRG/PRGSource/......./Single line of #X statement. The single line is then evaluated and checked if it matches the X# syntax, if yes then just "dump" it in the output, otherwise convert, or mark it in a comment block e.g. "/* $$TransportISSUE$$ <vfp text */". These we need to investigate and make a decision what needs to be done. So a "Marker" could be something like "$$DecideCompareAssign$$", do we have enough info to determine VFP"x = z" means iif(Any of {IF,CASE,WHILE,UNTIL[,<rest,...>]} is contained in VFP"<line>", XS"x = z", XS"x := z"). We just need to get this logic sorted out, then we will make an announcement if the DevTeam feels it is acceptable. We might then share this in a GitHub repo to get VFP and X# community members involved in assistance. The aim, assist the DevTeam not to worry about nitty gritty stuff that we as community can sort out, focus on compiler enhancements etc. We the community, a joint venture between VFP and X#(Old Clipper/VO/Vulcan head) users will take care of those. Probably a first in the XBase world, XBase forks working together with a common goal, bring two worlds into the X# world.
Again, hats off to the DevTeam, they have provided us a platform "X# is XBase.NET".
Do you X#?
