When I downsized last year I got rid of a load of books (offered here) -
this included full sets for V.O. and Clipper - including a special
edition Technical Reference which had all the 'C' source code for
Clipper functions ( Clipper used a macro* pre-processor that converted
'Commands' into functions - *you could write your own commands).
I also remember seeing comments on the Harbour/xHarbour site asking
contributors not to just submit these C functions without
checking/re-writing them.
Add to that the source code for the VFP extensions for C# /VB .NET and I
can see where these guys are coming from, and maybe where they're going <g>
...
-----Original Message-----
From: ProFox [mailto:[email protected]] On Behalf Of Alan Bourke
Sent: 07 February 2017 10:22
To: [email protected]
Subject: X#
Don't remember seeing this mentioned here before but it looks interesting.
https://www.xsharp.info/forum
You may have heard of Vulcan.NET which is an xBase language in more of the
Clipper vein and which supports Visual Objects projects.
Anyway the consensus among developers is that Vulcan.NET is dying or dead, and
so some of the developers have struck out on their own to implement an
open-source .NET implementation of xBase.
"In April 2015 a group of concerned customers and some members of the GrafX development team
have talked about starting a new open source project to give the xBase language for .NET a new
future. This initiative is called XSharp. This was partially inspired by the fact that Microsoft
has published the source code to its C# and Visual Basic compilers under an open source license
(.NET Compiler Platform "Roslyn"[1]). The plan is to create a new development language
(compiler, runtime libraties, IDE, tools) where the compiler is partially based on the Roslyn
source code."
While it will initially support Vulcan\Clipper\VO type syntax (which is in the
VFP ballpark but not identical) they also intend to support VFP syntax next. I
would imagine it would be core VFP syntax, dropping all the legacy stuff like @
.. SAY and defunct SYS() functions and so forth.
I *think* they intend to support DBF files natively.
Anyway, worth keeping an eye on at least.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
...
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
