Cint or Integer.Parse?

[Brian Henry]

Which one is better to use? CInt(string) or Integer.Parse(s tring)? thanks!

[Herfried K. Wagner [MVP]]

* "Brian Henry" <br**********@n ewsgroups.nospa m> scripsit:

any reason specific reason why you suggest i should use CInt instead of the
framework versions? I'm trying to maintain as much compatability in tearms
of code with C# incase they ever want this code directly coverted over to
it..

Readability. Code is more compact, there is no useless stuff like
'Parse'. It's like using '+' instead of 'op_Addition'. If we start
using the greatest common subset of language features in our code,
language interoperabilit y and more than one .NET programming language
are useless.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Jay B. Harlow [MVP - Outlook]]

Brian,
Because CInt may actually be faster then Integer.Parse or Convert.ToInt.

http://www.panopticoncentral.net/arc...5/31/1100.aspx

http://www.panopticoncentral.net/arc...6/07/1200.aspx
Using Integer.Parse, "cause its more C#" may actually be developing bad
habits. In that you will use Integer.Parse or Convert.ToInt "cause its more
..NET", where as if this was C# code I am sure you would have no problems
using an (int) cast. Guess what CInt is both an (int) cast & a
Convert.ToInt! VB.NET picks the correct on based on usage. Somehow that
makes it more preferred in my book, rather then less preferred... More RAD
somehow...

I'm trying to maintain as much compatibility in terms
of code with C# incase they ever want this code directly converted over to
it.. I would worry about conversion when the conversion actually happened,
allowing me to write "correct" VB.NET code, by "correct" I mean use the
correct feature for the correct problem. If you want to use VB.NET to write
C# code, I would strongly recommend you use C# to write C# code!

As a friend of mine says: avoiding CInt in VB.NET is like buying a new car
and avoiding using the power windows.

Just a thought
Jay
"Brian Henry" <br**********@n ewsgroups.nospa m> wrote in message
news:OC******** ******@TK2MSFTN GP09.phx.gbl... any reason specific reason why you suggest i should use CInt instead of the framework versions? I'm trying to maintain as much compatability in tearms
of code with C# incase they ever want this code directly coverted over to
it..
"Herfried K. Wagner [MVP]" <hi************ ***@gmx.at> wrote in message
news:eX******** ******@TK2MSFTN GP11.phx.gbl...

* "Brian Henry" <br**********@n ewsgroups.nospa m> scripsit:

been trying to knock out all the old vb stuff out of my head so sounds
like
the parse one is good to go with :)

'CInt' is not "old vb". It's current VB syntax that /should/ be used
/instead/ of the framework functions whenever possible. That's why we
have these commands.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Marc]

"Brian Henry" <br**********@n ewsgroups.nospa m> wrote in message
news:ua******** ******@TK2MSFTN GP12.phx.gbl...

Which one is better to use? CInt(string) or Integer.Parse(s tring)? thanks!

Another thing to consider is that CInt will convert the string
"1,000", whereas Integer.Parse will not; you'll get an exception.

Marc.

[Marc]

Sorry. Ignore my previous message.
You can use something like Integer.Parse(" 1,234",
Globalization.N umberStyles.Any ) to convert that string.

"Marc" <no****@nospam. com> wrote in message
news:u6******** ******@TK2MSFTN GP10.phx.gbl...

"Brian Henry" <br**********@n ewsgroups.nospa m> wrote in message
news:ua******** ******@TK2MSFTN GP12.phx.gbl...

Which one is better to use? CInt(string) or Integer.Parse(s tring)?

thanks!

Another thing to consider is that CInt will convert the string
"1,000", whereas Integer.Parse will not; you'll get an exception.

Marc.

[Herfried K. Wagner [MVP]]

* Marc <no****@nospam. com> scripsit:

Which one is better to use? CInt(string) or Integer.Parse(s tring)?

thanks!

Another thing to consider is that CInt will convert the string
"1,000", whereas Integer.Parse will not; you'll get an exception.

That depends on your system's number style settings...

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[The Grim Reaper]

Yes, you're quite right. I must have been more tired than I thought at 1am
this morning!!
I was thinking of the Asc() function - sorry.
_______________ _______________ _____
The Grim Reaper

"Herfried K. Wagner [MVP]" <hi************ ***@gmx.at> wrote in message
news:O8******** ******@TK2MSFTN GP09.phx.gbl...

* "The Grim Reaper" <gr*********@bt openworld.com> scripsit:

I agree that Integer.Parse is the wrong thing to use - but CType(xx,
Integer) is functionally identical to CInt - and if you happen to not have Microsoft.Visua lBasic referenced... it's fine :D

Both, 'CInt' and 'CType' are VB /keywords/ that should work without
referencing this library.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>