VOPS
in [Visual Objects]
|
From: Gary Stark on 20 Nov 2005 02:00 Jamal, A point of order if I may ... :) Jamal wrote: > You should really stop this constant barrage of non-sense, because it really > DOES hurt your credibility after all of your contributions to this NG. > It probably would, were he to have any. I'm not too sure that this is the case these days. :) -- g. Gary Stark gstark(a)RedbacksWeb.com http://www.RedbacksWeb.com
From: Geoff Schaller on 20 Nov 2005 02:08 Gary, > I'm paying roughly half that price for a system of that sort of > specification, and I'm only getting a 200 or 250GB drive into the bargain! Well bully for you <g>. But if you can a box with those specs for $450 Oz with an MS OS then that is a good price. But you are only amplifying my comments to Johel that I don't see how Brazillians can be getting such a better deal for hardware nor how hardware costs and software costs can be really such an issue any more anyway. Any business capable of paying rent, hiring staff and setting themselves up with basic office equipment simply isn't going to be burdened by the price of Windows XP or MS Office. Geoff
From: Ginny Caughey on 20 Nov 2005 07:05 Hi Geoff, I > don't believe there will be the scenario where we will just 'convert' our > 300,000 line VO apps and class libraries to anything. So if there is any > conversion effort involved, it will be as easy to convert to C# as it > would Vulcan. Of course you're entitled to your beliefs, but the fact is that Vulcan converts VO code to .NET today. It isn't complete yet, but it is nearly complete. (For you to hold the beliefs that you do, I have to wonder if you even tried Vulcan while you were part of VOPS.) Once you have MSIL, you can convert that to C# (or VB or Delphi) in 5 minutes if you want to. (Of course you may believe differently. <g>) If you prefer rewriting your VO apps in C#, don't let me stop you - hey I like C# too. And if your class libraries and apps really need a redesign anyway because you aren't happy with them, then of course you'd want to rewrite. But why are you waiting until next year to do so? Ginny
From: jmespinosabaviera on 20 Nov 2005 15:48 >Once you have MSIL, you can >convert that to C# (or VB or Delphi) in 5 minutes if you want to. (Of course >you may believe differently. <g>) What is MSIL ? Do you mean I can convert automatically from VO to Vulcan and then automatically from Vulcan to Visual Basic ? Please give me information about this.
From: BillyBob on 20 Nov 2005 16:17
MSIL stands for Microsoft Intermediate Language. All .Net languages compile to this intermediate language. The .Net runtime JIT takes care of compiling this Intermediate Language further so that it can be executed as native code. What Ginny is saying, is that you could theoretically compile Vulcan to IL and than reverse engineer it back to C#. This would in effect allow you to convert all your code to C#. It doesn't sound like the long term viability of Vulcan .Net is upper most in Ginny's mind. I think Brian needs to kick her out of VOPS. <g> <jmespinosabaviera(a)yahoo.com> wrote in message news:1132519735.658278.191620(a)f14g2000cwb.googlegroups.com... > >Once you have MSIL, you can >>convert that to C# (or VB or Delphi) in 5 minutes if you want to. (Of >>course >>you may believe differently. <g>) > > What is MSIL ? Do you mean I can convert automatically from VO to > Vulcan and then automatically from Vulcan to Visual Basic ? Please give > me information about this. > |