Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Visual FoxPro - Transition to VB.NET or C#?
Message
 
To
06/09/2002 14:04:42
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Miscellaneous
Thread ID:
00695052
Message ID:
00699146
Views:
24
Actually, I did forget while typing that message - but it doesn't affect my response. <g>

Let me explain in some more detail. There are two types of functions here - intrinsics and externals. CInt and CStr are intrinsics - so they cannot be called by C# or any other language. Other functions like UCase are external, and can be called by other languages. To make things a little more confusing, some of our intrinsics, in some cases, may call helper functions that are in the microsoft.visualbasic namespace - and C# developers could find them and call them - though I don't think they are documented (though intellisense should still work).

I get the feeling that I just made things clear as mud. <g>

yag

>Alan,
>
>>The thing is, I was looking over this thread and noticed that YAG had pointed out that C# had access to the Framework for things like the Convert class while VB had conversion routines built in that might actually be faster. For instance, Convert.ToInt32(LongVar) vs CInt(LongVar).
>
>Maybe YAG forgot? :-)
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform