Overflowing a Long

An amazingly resilient meme, that one.

Since the product used to blunt the poison's taste in Jonestown was really Flav-or-ade.

 

Public fpi as Oxymoron


Yep, sure enough!

 

In VB-land, anything's possible . I suppose I ought to have said
"floating point variables", but I assume you know what I meant =P.

 

Maybe Karl belongs to a different group that uses Kool-Aid...?


Rob

 

Hard to keep a Good Meme down! ;-)

 

I think one of the things that *most* confuses those new to VB is that the
definition of "Integer" is extremely precise. So much so, in fact, it hasn't
changed in over 30 years. So much so, it was invariate across 8-, 16-, and 32-bit
processors. In fact, it was this very confusion that led to the ultimate death of
VB, as we all knew and loved it. The newcomers couldn't be bothered to RTFM.

MSBASIC, 1976-2001, RIP.

 

¤ > ¤ Oh, wow, there's a compiler option to supress overflow checking?
¤ > ¤ Great, I'll give that a try and see if it works--if it does, I take
¤ > ¤ back the nasty things I said about VB . They really should implement
¤ > ¤ a bit-shift operator, though, and preferably one that can handle more
¤ > ¤ than a Long! Thanks for your help.
¤ >
¤ > Actually it was implemented in Visual Basic.NET 2003.
¤
¤ Which has *nothing* to do with the subject at hand, of course!

Then why did you bring it up?

"Totally agree. Isn't gonna happen, though. It's a dead language; which isn't
altogether a Bad Thing."


Paul
~~~~
Microsoft MVP (Visual Basic)

 

¤
¤ > Actually it was implemented in Visual Basic.NET 2003.
¤
¤ What a strange statement! Are you on something?
¤

Why did you find it strange? Care to explain?


Paul
~~~~
Microsoft MVP (Visual Basic)

 

¤ > Actually it was implemented in Visual Basic.NET 2003.

If I had to guess, I would say because this newsgroup is devoted to problems
people have with VB6 (and earlier). What other languages do (be they VB.NET,
C++, Fortran or whatever) doesn't go very far in answering questions posed
here by people using the programming language for which this newsgroup
caters to.

Rick

 

¤ > ¤ > Actually it was implemented in Visual Basic.NET 2003.
¤ > ¤
¤ > ¤ What a strange statement! Are you on something?
¤ > ¤
¤ >
¤ > Why did you find it strange? Care to explain?
¤
¤ If I had to guess, I would say because this newsgroup is devoted to problems
¤ people have with VB6 (and earlier). What other languages do (be they VB.NET,
¤ C++, Fortran or whatever) doesn't go very far in answering questions posed
¤ here by people using the programming language for which this newsgroup
¤ caters to.

My post was in response to the statement about adding the feature to the language and correcting one
which claimed it would never happen.

It isn't up to me to decide whether the option is a viable alternative. I'm simply providing the
information for those who would choose to decide for themselves, and not having it forced upon them
by those who would never consider it.


Paul
~~~~
Microsoft MVP (Visual Basic)

 

Non sequitur.

 

It didn't happen. The language died. You're hallucinating. QED.

 

¤ > Well, I definitely don't need a shift operator that desperately .
¤
¤ Heh, so you've met our resident evangelist! Repeat after me:
¤
¤ "Bite me, Paul!"
¤
¤

Hey, someone's gotta save the folks from the resident anti-Microsoft boogeymen. ;-)


Paul
~~~~
Microsoft MVP (Visual Basic)

 

But the feature you were taking about, as I recall, was a Shift or perhaps a
Rotate instruction. Such a feature has *not* been added to Visual Basic, at
least not to the *real* Visual Basic. Dotnet is effectively a completely
different language. It is *not* an update to VB6. You must be "on something"
if you think that it is. Micro$haft can of course call it anything they
like, just as you can spend all year if you wish, or even longer, calling a
spade a fork. But calling a spade a fork will not actually turn it into a
fork, no matter how many times you say it!

Mike