C# IntelliSense is suck!

  • Thread starter Thread starter Dave
  • Start date Start date
This is the insidiousness of VB. It promotes "loose" thinking, which leads
to "top posting" and not recognizing simple logic such as the fact that no
statement can ever be more than 100% accurate.

Regards,
Dan
 
Hi Brutus,
I forgot the referenceNo I told you that I did expirimences and that the Visual Basic functions
are faster that the system.net members.
I gave you that test program.
:-))
Cor
 
* "Fergus Cooney said:
VB.NET is a friendly Labrador which wags its tail and knocks things over.
It's just a bit boisterous and clumsy at times. Always seems to take up more
space than you'd expect. It does the most horrendous farts.

C# is a Police-trained German Shepherd. Sharp is a good word for it. Its
moves are clean and efficient. Cuddly it ain't - though it's quite beautiful.
You wouldn't have it for the children to play with - not because it's
dangerous (too well trained for that) but it just wouldn't be as much fun as a
Labrador.
Click to expand...

ROFLM*O
 
* "Fergus Cooney said:
Part of this is the fact that a 100 line block of VB can be done in 20
lines of C# - so you can <see it all>. C# and elegance can be as one with each
other. I'd rarely say that with VB.
Click to expand...

Are you sure?!
 
* "Cor said:
No I told you that I did expirimences and that the Visual Basic functions
are faster that the system.net members.
Click to expand...

I know that (your test program), but I thought you wanted to turn to C# *shock*.
 
Hi Brutus,
No I told you that I did expirimences and that the Visual Basic functions
are faster that the system.net members.
I gave you that test program.
Cor
Click to expand...

What functions are faster? Almost all of the VB.NET functions delegate
to actuall .NET functions anyway...
 
Hi Tom,
When I read this, I think I have to go start using C#
Do you know if I can use the microsoft basic functions in it, because my
experimences showed me that they are such a lot faster?.
Cor
Click to expand...

I don't see how they can be faster, since most of them are just wrappers
around the .NET framework classes... But, yes - if you like you can use
them. Just reference Microsoft.VisualBasic.dll, make your appropriate
using statements, and off you go.
 
Hi Fergus,
I love the {}, the way a variable and an object is declared, the unifomity
of the program control,
do you real think I did not do some expirimences with it; I can do the most
strange things with JavaScript.

I find the word "then" absolute unneccesary in Visual Basic (that is a word
that I always forget to write).

But I realy hate the == and the case sensitive (probably because that
strange document object model, that has the uppercases on the most strange
places).

You must understand that, it has a lot of plusses for me, one of the things
to that C is for what is the code, almost natural language independent. But
because of the framework it is not and has therefore almost no benefits
about that above Visual Basic.

But I love it, if a it is posible to make a program that don't need comment
blocks.

And I think that is better to do with Visual Basic than C#

Therefore I don't understand those people who ask for comments blocks in
Visual Basic,

(You understand than too why I don't like the regular expression).

Cor
 
Tom,

I use the system.members, I don't like it that the index of the functions
start at 1.

But I was always arguing with Herfried about them, and thought why not it is
a benefit of a natural language when you can use more words to express
yourself.

Last week there was an arguing in this newsgroup with Jay B. and some others
about the regular expressions, the functions and the system members.

Jay B, said it was too discussed in the C# group but nobody did make a
testprogram, so I did.

With a String the Visual.Basic function Find was twice as fast as the
system.member indexof exactly on the same way used.
The regulair expression was 15 times slower than the indexof.
Only with a character, (that is not in the functions), the indexof was
faster.

I was perplex.

Cor
 
Hi Dan,

ROFL.

Although in Tom's defense I have to say that there's Spock logic (range 0%
to 100%) and there's McCoy logic. The latter can have 'percentages' far in
excess of 100 - calculated, as it is, with emotionally fuzzy logic.

Regards,
Fergus
 
Hi Tom,

That's what I thought.

But this character counting loop
Do
iResult = InStr(iStart, strInput, strDelimiter)
If iResult = 0 Then Exit Do
iCount += 1
iStart = iResult + 1
Loop
is actually faster than
Do
iResult = strInput.IndexOf (sDelimiter, iStart)
If iResult < 0 Then Exit Do
iCount += 1
iStart = iResult + 1
Loop
(though not when IndexOf uses a Char)

Regards,
Fergus
 
Hi Herfried,

Sure, I'm sure.

Take:
Public Property Foo As String
Get
Return m_Foo
End Get
Set
m_Foo = Value
End Set
End Property
vs
public string Foo { get { return m_Foo; } set { m_Foo = value; }}
for instance.

That's perhaps an extreme example (8 to 1), but C# has lots of space
savers.

Regards,
Fergus
 
Hi Tom,

That's what I thought.

But this character counting loop
Do
iResult = InStr(iStart, strInput, strDelimiter)
If iResult = 0 Then Exit Do
iCount += 1
iStart = iResult + 1
Loop
is actually faster than
Do
iResult = strInput.IndexOf (sDelimiter, iStart)
If iResult < 0 Then Exit Do
iCount += 1
iStart = iResult + 1
Loop
(though not when IndexOf uses a Char)

Regards,
Fergus
Click to expand...

Interesting... Did anyone look at the IL to see what was going on? Just
curious.
 
* "Fergus Cooney said:
Sure, I'm sure.

Take:
Public Property Foo As String
Get
Return m_Foo
End Get
Set
m_Foo = Value
End Set
End Property
vs
public string Foo { get { return m_Foo; } set { m_Foo = value; }}
for instance.

That's perhaps an extreme example (8 to 1), but C# has lots of space
savers.
Click to expand...

ACK. IMO the C# version is "unreadable".
 
FWIW, i would tend to agree. They are getting compiled into the same IL anyhow, so id rather have
code that makes sense just by looking at it.
 
Hi Tom,

I haven't done so and no one else mentioned it. If you find yourself
delving, it would be interesting to know, but STD_OUTPUT_HANDLE might keep you
too busy! ;-)

Regards,
Fergus
 
Hi Herfried,

|| IMO the C# version is "unreadable".

That's useful to know - ponder and recall that feeling, then multiply it.
Many one-language-only speakers feel <that>, and more, when they see a page of
German or French, or English, or Russian, Greek, Sanscrit, Korean,
Babylonian....

Regards,
Fergus
 
Hi Herfried, Rick,

Europeans once discovered a tribe of natives who had lived their entire
lives in the jungle. A few of these natives once had occasion to travel with
the Europeans and eventually came to areas of plains where herds of grazing
animals lived. They could be seen for miles around. The natives couldn't
believe how some of these creatures were so big and yet others (of the same
type) were so tiny. They simply couldn't understand how the images were small
because of perspective. They had never perceived anything like it in the
jungle where the longest as-far-as-the-eye-can-see distance is measured in
mere metres.

So it is with C# and VB.

======================================
The standard formatting of braces in C# is
string foo()
{
Code at this level.
}

I <hate> it - for my eyes are used to
string foo()
{
Code at this level.
}

The former makes me feel very uncomfortable because my eyes can't parse it
as readily as the style I've been using for all these years.

Regards,
Fergus
 
* "Fergus Cooney said:
That's useful to know - ponder and recall that feeling, then multiply it.
Many one-language-only speakers feel <that>, and more, when they see a page of
German or French, or English, or Russian, Greek, Sanscrit, Korean,
Babylonian....
Click to expand...

It's not unreadable because I don't "speak" C#, but my eyes need much
more time to understand the code.
 
Back
Top