From: Henning on

"Scott M." <s-mar(a)nospam.nospam> skrev i meddelandet
> "Henning" <computer_hero(a)> wrote in message
> news:ebDfnYhRKHA.1236(a)TK2MSFTNGP05.phx.gbl...
>> And as usual, the OP has already posted in the dotnet group!
>> And then the issue of Call in dotnet takes place in the wrong group, as
>> usual!
>> /Henning
> Since you seem to be very "used" to this kind of thing, one would expect
> you'd have gotten over it by now instead of letting it keep you up at
> night.
> If you haven't read the entire thread, you should because it has spawned
> an explanation of the proper use of the Call keyword in relation to a VB 6
> application, which certainly belongs in the VB 6 newsgroup, no?
> -Scott
*It* is not what is keeping me up ;)
What VB6 application??
As have been said, Call might as well be dotnet, and a lot of other
languages, or?
And the OP *is* as seen, in the dotnet group, using dotnet. Good guess


From: Karl E. Peterson on
Scott M. wrote:
> "Karl E. Peterson" <karl(a)> wrote ...
>>> You disagree that "Call" originated with classic VB?
>> Ever hear of Fortran? ASM?
> Sure I have, but since those languages are not VB, they are not related to
> my response. No one is asking about the use of Call in those languages.
> I'm talking about when Call originated in the VB language.

Well forgive me for taking you to mean what you said, in that case. Call certainly
did *not* originate with ClassicVB. But if upon correction and reflection you want
to qualify your initial WILD ASSertion, so be it.

VB is a dialect of MS BASIC, and Call goes back further than VB in that language
family. It's entirely debatable whether VFred falls into the same family, so don't
bother pointing out the confusingly similar names as any sort of rationale for that
meaningless restriction.
..NET: It's About Trust!

From: Tom Shelton on
On 2009-10-06, Scott M. <s-mar(a)nospam.nospam> wrote:
> "Karl E. Peterson" <karl(a)> wrote in message
> news:%23L5t0ksRKHA.1792(a)TK2MSFTNGP04.phx.gbl...
>> Scott M. wrote:
>>> "Call" is a keyword that originated with classic VB.
>> Bull. How old are you, anyway?
> You disagree that "Call" originated with classic VB?

It didn't. It originated before VB.

Tom Shelton
From: Tom Shelton on
On 2009-10-06, Scott M. <s-mar(a)nospam.nospam> wrote:
> "Tom Shelton" <tom_shelton(a)> wrote in message
> news:%23HOPJlgRKHA.1796(a)TK2MSFTNGP02.phx.gbl...
>> On 2009-10-05, Scott M. <s-mar(a)nospam.nospam> wrote:
>>> It's supported for legacy reasons, but not needed at all. It's not
>>> included
>>> in any code snippets or required as it is in VB 6. In short, there is no
>>> reason to ever use or need it in .NET.
>> Where was it rquired in VB6?
>> Besides, required or not is beside the point. It's there, it can be
>> used - so
>> you can't judge it to be vb6 code simple because it uses the the call
>> keyword.
>> --
>> Tom Shelton
> I disagree. I think that in "reality" you can very easily make a very
> accurate educated guess that this code is VB 6 code.

Are you kidding? Seriously, Scott - many VB.CLASSIC developers (including
myself) used to be in the habbit of using call on almost all calls that didn't
assign a value - simply because the VB.CLASSIC way of handeling parens was so
confusing :) Do you think they are just going to give up that habbit
overnight? I know lots of my early VB.NET code has lots of Call statements in
it :)

Tom Shelton
From: Eduardo on
Bob Butler escribi�:

> Where it gets confusing for people new to VB is when CALL is omitted:
> DoThing (lngValue)

You can do that only if the function has just one parameter, but if it
has more than one, you need whether to use Call or to remove the

That's in fact the difference with .Nxt, you can use parenthesis even
with more parameters without the need of the word Call (I researched a bit).

PS: And about the other discussion about when the word Call appeared in
BASIC, at least it was in the TI99/4A (year 1983). A TI99's program
using Call is posted here:

The TI99:
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Prev: crack for VSFlex8 in VB6.0
Next: Component Handles