Page 2 of 3
Error XS7038
Posted: Thu Mar 21, 2019 6:50 am
by Juraj
Hi all
I thank Chris for the great help. Bugs in the code were due to my inattention. This will probably not damage the drive because it was the same error in multiple files. [ (string) cNaz> 0, instead of cNaz: Length> 0 ] . I think it's good if the compiler is getting more stringent, but it would be a good idea to include such errors in the log to make them easier to fix.
After correcting this typo, the compilation took place without a mistake once again thanking Chris for quick help. It's great to have such support from XSharp-team.
Juraj
Error XS7038
Posted: Thu Mar 21, 2019 7:15 am
by lumberjack
Hi Juraj,
As you mention, great support via the forums and the DevTeam.
A suggestion, to everybody actually.
The DevTeam are quite busy enhancing X#, support, bug fixes. It consumes a lot of that time. It implies "marketing" is a bit neglected. I posted a message yesterday on c.l.c.vo just to remind anybody that is not aware of X# and the success story to try it out. My gut feel was correct, there are still VO developers who apparently don't know or follow X#... Dick also jumped in sharing his success story. Thanks Dick! We need to make people aware of X#. I for example monitor the VFP forums and if somebody ask about VFP alternatives, I respond, there already a couple of VFP guys here that I recognize the User ID from VFP forums. They still quiet, luckily there are some like Matt, he started making noise in the forums. He did a WinForm using EF for data exchange. He announce, I know a little bit of c# and VFP, within a day or two I was able to.... Small things, it can make such a difference in awareness of X#.
So why don't we as a community share these success stories on c.l.c.vo, somebody might just have an issue and remember, oh there was this forum c.l.c... and post his issue. Hmmm, interesting, what is this X# posting in here...
A community working together to share the X# experience riding the .NET wave.
Just my thoughts,
Error XS7038
Posted: Thu Mar 21, 2019 3:40 pm
by Chris
Thanks for the good words Juraj! Yes, of course this is a small compiler bug, it should had found the typo in the code and display a proper error message, this will be done soon I am sure.
Johan, thanks for your initiative(s), just remember that up till now X# wasn't really ready for mass marketing. You can already do new pure .Net apps just fine with it, but for apps to be ported from VO, we were depending on the vulcan runtime, which is not even officially available anymore right now. But all this is about to change very soon, the X# rutnime is now very close to being production ready, which will open a lot of new possibilities. It will be an exciting year.
Error XS7038
Posted: Thu Mar 21, 2019 4:08 pm
by lumberjack
Hi Chris,
Chris wrote:Johan, thanks for your initiative(s), just remember that up till now X# wasn't really ready for mass marketing. You can already do new pure .Net apps just fine with it, but for apps to be ported from VO, we were depending on the vulcan runtime, which is not even officially available anymore right now. But all this is about to change very soon, the X# runtime is now very close to being production ready, which will open a lot of new possibilities. It will be an exciting year.
You welcome!
Well why you think I started now with my initiative... We almost 100% mature.
And the beauty is X# already support:
Code: Select all
ADD OBJECT o AS Button WITH 10, 10, 50, 100
ADD OBJECT o AS Button ;
WITH Top=10, Left = 10, Height = 50, Width = 100, ;
Name = "ButtonOk", Caption = "Ok", EVENT Click = OnButtonClick
TEXT TO cStr AS ;
SELECT * ;
FROM tbl ;
WHERE x < 10
ENDTEXT
if you understand what I mean...
Error XS7038
Posted: Thu Mar 21, 2019 7:29 pm
by wriedmann
Hi Johan,
please don't forget: most VO and most VFP programmers need DBFCDX support.
IMHO it may be better to wait with massive marketing actions to have it working and stable. Otherwise there is a risk that people will look at X#, see the RDD is missing and discard it too fast.
Wolfgang
Error XS7038
Posted: Thu Mar 21, 2019 8:55 pm
by FFF
+1.
Hopefully we will see CDX after Austin
Error XS7038
Posted: Thu Mar 21, 2019 9:29 pm
by lumberjack
Hi Wolfgang,
Yes I realise that, however what do you define as "most". From my understanding "most" already working in RDBMS via the ODBC drivers etc. Which don't need DBFCDX anymore.
Johan
Error XS7038
Posted: Fri Mar 22, 2019 4:56 am
by wriedmann
Hi Karl,
Hopefully we will see CDX after Austin
yes, I hope that really. Robert wrote some time ago that DBFCDX is priority #1.
Wolfgang
Error XS7038
Posted: Fri Mar 22, 2019 8:11 am
by FFF
Johan,
we don't know. But if the whole exercise in "transplanting" Vo to modern times shall work, you can't ignore a major part. My suspicion is, that there are quite some folks out there who don't want or can't invest a lot of time swapping GUIs and Databackends. To "jump" there has to be a lot of benefit...
Anyway, i think completion is not far away, let us see it, use it, make dev fix some buglets
- and then propose to the rest of the world...
Error XS7038
Posted: Fri Mar 22, 2019 12:10 pm
by robert
Wolfgang,
That is still true.
Robert