Re: The Demise of C#
- From: "David Davidson" <daviddavidson3@xxxxxxxxxxxxxxxx>
- Date: Fri, 26 Aug 2005 14:21:02 -0700
What about VarPtr, VarPtrArray, StrPtr, and ObjPtr? Won't they still work in
VB.Net?
- Dave
"Kevin Spencer" wrote:
> The AddressOf operator is not for creating pointers. It is for creating
> procedure delegates. You can't use pointers in .Net without unsafe code.
> VB.Net does not allow unsafe code.
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> ..Net Developer
> What You Seek Is What You Get.
>
> "David Davidson" <daviddavidson3@xxxxxxxxxxxxxxxx> wrote in message
> news:53E1470A-9787-4E0A-BF3B-FD59E0F814C9@xxxxxxxxxxxxxxxx
> > You can use unmanaged code and pointers in VB.NET. I've used the
> > dllImport
> > attribute to make calls to functions in DLLs like User32 and the like, and
> > there's the AddressOf operator for creating pointers to functions and
> > such...
> > I think there is something C# can do that VB.NET can't, but I can't
> > remember
> > what it is. I do know that C# doesn't have ParamArrays while VB.NET does,
> > but that's just indicitive of the main reason to choose one .NET language
> > over the other: personal preference.
> >
> > - Dave
> >
> > "Kevin Spencer" wrote:
> >
> >> > There is nothing that you can do in C# that you cannot do in VB.NET.
> >>
> >> I'm afraid that's simply untrue. You can't use unmanaged code in VB,
> >> pointers, and several other less important items. Yes, it may be a rare
> >> occasion that you need to, but believe it or not, I've worked on several
> >> projects over the past year which process very large (200 - 500 MB)
> >> images,
> >> and there's no substitute for pointers in a situation like that. In fact,
> >> even with the use of pointers, I have one app that takes several hours to
> >> process a single image.
> >>
> >> --
> >> HTH,
> >>
> >> Kevin Spencer
> >> Microsoft MVP
> >> ..Net Developer
> >> Neither a follower nor a lender be.
> >>
> >> "Peter Rilling" <peter@xxxxxxxxxxxxxxxxxx> wrote in message
> >> news:O6eVNATGFHA.3728@xxxxxxxxxxxxxxxxxxxxxxx
> >> > Okay, I write this message with the full knowledge that I am going to
> >> > piss
> >> > a
> >> > large number of people off. So I fully expect some flaming to happen.
> >> >
> >> > As languages evolve, there becomes less and less that differentiates
> >> > them.
> >> > There is nothing that you can do in C# that you cannot do in VB.NET.
> >> >
> >> > I came from a VB development background and moved to C# about five
> >> > years
> >> > ago. I do not necessarily think that companies look for C# people
> >> > because
> >> > of the tie-in with C++, but rather that C# develops have more of an OOP
> >> > sense about them. C++ and C# are object oriented languages and
> >> > therefore
> >> > those people tend to think in object design. VB used to be thought of
> >> > a
> >> > toy
> >> > and only used for RAD development. There was little emphasis placed on
> >> > proper coding styles. It was more of a "let's get it done" mentality
> >> > rather
> >> > then "let's design something for expandability and maintainability".
> >> > Keep
> >> > in mind that until VB.NET was released, the concept of classes was
> >> > shoddy
> >> > at
> >> > best and certainly did not have inheritance or polymorphism, which
> >> > means
> >> > that VB was NEVER an object oriented languages.
> >> >
> >> > Remember that when the GUI first came out it was also thought of as a
> >> > toy.
> >> > Why would real computer uses use a graphical interface, was the mantra
> >> > of
> >> > my
> >> > command-line gurus.
> >> >
> >> > "Kevin Spencer" <kevin@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> > news:#XnYteSGFHA.2876@xxxxxxxxxxxxxxxxxxxxxxx
> >> >> About 2 years ago, and as recently as perhaps 1 year ago, I can recall
> >> >> seeing many posts about what language to use with ASP.Net. The
> >> >> consensus
> >> > was
> >> >> that employers paid more for C# programmers, and it seems that C#
> >> >> became
> >> > the
> >> >> darling of the ASP.Net crowd.
> >> >>
> >> >> In the meantime, I have observed an interesting phenomenon.
> >> >> Originally,
> >> >> employers hired programmers who used C# because it was based on C, and
> >> >> the
> >> >> prevailing opinion was (and may still be) that C# developers were
> >> >> better
> >> >> because they must have known and/or practiced C or C++ at some time,
> >> >> which
> >> >> would make them better programmers overall. C and C++ are hard-core
> >> >> programming languages compared to VB.
> >> >>
> >> >> However, now that nearly everyone has jumped on the C# bandwagon, it
> >> >> seems
> >> >> to me that the distinction between the languages has nearly
> >> >> disappeared,
> >> > at
> >> >> least in terms of evaluating programmers for hire. There seem to be
> >> >> almost
> >> >> as many clueless C# developers out there as VB.Net developers. Many C#
> >> >> developers today are basically VB.Net developers using a different
> >> >> syntax.
> >> > I
> >> >> wonder if the employers have become aware of this trend?
> >> >>
> >> >> --
> >> >>
> >> >> Kevin Spencer
> >> >> Microsoft MVP
> >> >> .Net Developer
> >> >> Neither a follower nor a lender be.
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >>
>
>
>
.
- Follow-Ups:
- Re: The Demise of C#
- From: Kevin Spencer
- Re: The Demise of C#
- From: Kevin Spencer
- Re: The Demise of C#
- Prev by Date: Re: Cannot use "fill" with Datareader
- Next by Date: Re: datagrid in a div for scrolling question
- Previous by thread: Database Statistics... Best way to maintain stats???
- Next by thread: Re: The Demise of C#
- Index(es):
Relevant Pages
|
