Path: csiph.com!feeder.erje.net!1.eu.feeder.erje.net!weretis.net!feeder4.news.weretis.net!news.szaf.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Wolfgang Riedmann" Newsgroups: comp.lang.clipper.visual-objects Subject: Re: Very interesting : XSharp development roadmap for 2018 Date: Fri, 11 May 2018 20:32:25 +0200 Lines: 87 Message-ID: References: <1f81b4a4-fdb0-48cd-a1cb-6b0b729bf621@googlegroups.com> X-Trace: individual.net h8Viy9B6zNont/Z5A2fUNw9+z4brDwEFEPEbveUR47Nwcp1/o= Cancel-Lock: sha1:/cKakfX3d7Y1gkAkyascJN0sXt0= User-Agent: XanaNews/1.18.1.6 Xref: csiph.com comp.lang.clipper.visual-objects:11609 Hi Dick, I can give you a feature that alone outweighs all others (from a accounting software developers standpoint): the decimal datatype. Then I see collections, interfaces, generics and typed init methods as advantage, and the one line syntax for properties are a real time saver. And the come all the source code samples, the 3rd party libraries and a lot more. Wolfgang D.J.W. van Kooten wrote: > Replying on message of Fri, 11 May 2018 16:05:49 +0300 from Chris > Pyrgas: > > > Hello Chris, > > I'll give you the same reply as I gave Wolfgang: you are 100% right.Or > 95% maybe, from my point of view, as I don't some of the advantages > you describe as an advantage. Or less than 95% () depending on how > badly one misses some VO features. > > I must add that I consider a lot of language elements not present in > VO hardly as something I find really more useful than the VO > alternative while a couple of 'missing' features from VO weigh much > heavier for me. That's why I -still- prefer the 'outdated' VO above > the 'modern' but more time consuming .Net languages. However, I do > realize 100% that there will be a tipping point, where replacing X# > with VO is better. That point will differ from application to > application I think. > > > Let's go through some examples, most the ones you mentioned. > > FOREACH. It is more logical to use like e.g. going through all files > of a directory. VO's FOR..NEXT requires just 1 line more code and IMO > is then easier to follow as in the debugger you have a number of files > in a variable. Enumarators is about the same, but I admit it is a more > efficient than using arrays as you would in VO. Or something like a > LIST is definitely better as in an array you don't see what it > contains. > > Int64 is certainly true. Fabrice great Fabtools include a Fabzip but > due to VO's limitations it stops when files are >2 Gb. I currently zip > by calling my Vulcan/C# DLL and if that's all in one program it would > be better of course. Strong typing: not needing to declare the > variables is certainly much better. > > Scoped locals (I had to look up what you meant with it) are useful > indeed, so far I only used them in C#. Generics I always find hard to > understand when I see code using it, I don't see any advantage in > namespaces (classes are already bad enough - I would love to only use > program wide functions ;). > > > I don't see what array initializers add to VO's defining of arrays. > Same for attributes: I wasn't familiair with these either and to me it > looks the same as adding a comment in code. And commenting in and out > works way better in VO anyway.... > > Interfaces: I know of 1 specific situation where it made sense: where > I had a Vulcan Pc/server based client talk to a C# based server on a > website. Without the interface DLL generated for both it wouldn't > work. For all other instances it's is just more code than necessary. > > Stepping back in debugging is, if I understand correctly, something of > VS 2017, which I don't use as long as I still have Vulcan program. But > that should change for me soon. Of course the average VO users will > need the 'Ctrl X' style inspection option much more badly than any of > the other VS debug options. Good to know this option is close! > > Finally I would be interested in how to use a project in Xide and VS > at the same time. Can you say something more about that? E.g. I do > have a few VS X# WPF projects, if I would want to work on the code > (except WPF editor based work) how do I setup that in Xide? > > Dick --