Methods vs functions

[Stefan]

Could someone please explain if there is a difference between when one
should use the word method or function. Do they have the same meaning?

[Tom Spink]

I generally use the term method, because thats how the framework refers to
them. The term method has no distinction between a Sub and a Function, and
can therefore mean a Sub or a Function. If you want to be explicit, then use
the terms 'Sub' or 'Function'. Also, in C-based languages, and indeed some
other languages, there are no subs or functions, and to create a 'sub' you
simply set the return type as void:

C++:

void MySub( )
{
return;
}

VB.NET:

Public Sub MySub()
Return
End Sub

C++:
int MyFunc( )
{
return 5;
}

VB.NET:

Public Function MyFunc() As Integer
Return 5
End Function

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit
"Stefan" <st******@student.uu.se> wrote in message
news:u2**************@TK2MSFTNGP11.phx.gbl...

Could someone please explain if there is a difference between when one
should use the word method or function. Do they have the same meaning?

[Jay B. Harlow [MVP - Outlook]]

Stefan,
Like Tom I use method for either Sub or Function.

I will also use method to mean Property procedures as well.

The way I view it is: Sub, Function & Property are types of methods. So I
use method when I want to be generic, I use Function when I need to be
specific.

Hope this helps
Jay

"Stefan" <st******@student.uu.se> wrote in message
news:u2**************@TK2MSFTNGP11.phx.gbl...

Could someone please explain if there is a difference between when one
should use the word method or function. Do they have the same meaning?

[Herfried K. Wagner [MVP]]

Hello,

"Jay B. Harlow [MVP - Outlook]" <Ja********@email.msn.com> schrieb:

Like Tom I use method for either Sub or Function.
That's how I use the term "method" too.
I will also use method to mean Property procedures as well.
I won't.
The way I view it is: Sub, Function & Property are types of methods. So I
use method when I want to be generic, I use Function when I need to be
specific.

I use the terms a bit different (according to
http://msdn.microsoft.com/library/en...gobjects.asp):

"methods" are actions, an object can perform.
"properties" are attributes.

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Tom Spink]

Also, when compiled, IL creates two methods for the property, the get_...
and the set_... (unless its readonly or writeonly)

Just like operator overloading, IL creates overloaded versions op_...
methods to specify the different overloaded versions of the operators, which
technically means you can implement operator overloading in VB.NET, but
cannot *use* it in operator form.

Public Function op_Equality(ByVal o As Object, ByVal p As Object) As Boolean
Return o.ToString = p.ToString
End Function

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit
"Jay B. Harlow [MVP - Outlook]" <Ja********@email.msn.com> wrote in message
news:uo**************@TK2MSFTNGP12.phx.gbl...

Herfried,
Although I agree with you 100%.

You did notice I was specific to say Property _Procedures_ (by Procedure I
mean the Get & Set assessors) and not just Property. As the Get & Set
assessors have statement blocks aka action.

http://msdn.microsoft.com/library/de...us/vbls7/html/
vblrfVBSpec7_6.asp
The problem is Properties are in that grey area where they're both.
Depending on what aspect of a property you are referring to.

The property itself is an attribute, while the get & set assessors are
'actions', which can be Overridden.

For example, You can apply the ConditionalAttribute to any method. This
includes the Get or Set assessor of a Property.

Property Name() As String
<Conditional("DEBUG")> _
Get
return m_name
End Get
<Conditional("DEBUG")> _
Set(ByVal value As String
m_name = value
End Set
End Property

Of course the above Get will not have the desired effect as its returning a value, and needs to be called in all cases...

Which is where generically I will include Property Assessors as methods. At the same time generically I include Properties as attributes.

Hope this helps
Jay

"Herfried K. Wagner [MVP]" <hi*******@m.activevb.de> wrote in message
news:uG*************@TK2MSFTNGP11.phx.gbl...

Hello,

"Jay B. Harlow [MVP - Outlook]" <Ja********@email.msn.com> schrieb:

Like Tom I use method for either Sub or Function.
That's how I use the term "method" too.

I will also use method to mean Property procedures as well.

I won't.

The way I view it is: Sub, Function & Property are types of methods.

So I use method when I want to be generic, I use Function when I need to be
specific.

I use the terms a bit different (according to

http://msdn.microsoft.com/library/en...tandingobjects
..asp):

"methods" are actions, an object can perform.
"properties" are attributes.

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Cor]

Hi,
I think this can be an endless discussion but important is in my opinion
again what language are you using (speaking).
My child name is Kok and from my sister Con.
My mother is not speaking any language.
You should have seen the faces from the french people when my mother was
calling us on the camping where we where when I was young.

I think that when I am thinking in VB I use the word function when I am
talking about functions like Mid, Len and even String.
I then am talking about methods when I use things like String.substring.

Cor

[Herfried K. Wagner [MVP]]

Hi Jay,

"Jay B. Harlow [MVP - Outlook]" <Ja********@email.msn.com> schrieb:

Although I agree with you 100%.

You did notice I was specific to say Property _Procedures_
(by Procedure I mean the Get & Set assessors) and not just
Property. As the Get & Set assessors have statement blocks aka action.

http://msdn.microsoft.com/library/de...fVBSpec7_6.asp
The problem is Properties are in that grey area where they're both.
Depending on what aspect of a property you are referring to.

The property itself is an attribute, while the get & set assessors are
'actions', which can be Overridden.

For example, You can apply the ConditionalAttribute to any method. This
includes the Get or Set assessor of a Property.

Property Name() As String
<Conditional("DEBUG")> _
Get
return m_name
End Get
<Conditional("DEBUG")> _
Set(ByVal value As String
m_name = value
End Set
End Property

Of course the above Get will not have the desired effect as its returning a value, and needs to be called in all cases...

Which is where generically I will include Property Assessors as methods. At the same time generically I include Properties as attributes.

Notice that I am not a native English speaker, maybe I am misinterpreting
the meaning of method, procedure, and attribute. Why not use the terms like
that:

method: Sub, Function (if they are members of a class)
procedure: Sub, Function, Property (Get, Set)
attribute: Property

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Tom Spink]

The term attribute does tend to confuse, as that's what the < and > are
called:

<StructLayout(Foo)> Public Structure Bar
Public Baz As Moo
End Structure

The <StructLayout(Foo)> is an attribute, that's what microsoft calls it.

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit

"Maybe it's a game called 'Punish the User'"
"Herfried K. Wagner [MVP]" <hi*******@m.activevb.de> wrote in message
news:OI**************@TK2MSFTNGP12.phx.gbl...

Hi Jay,

"Jay B. Harlow [MVP - Outlook]" <Ja********@email.msn.com> schrieb:

Although I agree with you 100%.

You did notice I was specific to say Property _Procedures_
(by Procedure I mean the Get & Set assessors) and not just
Property. As the Get & Set assessors have statement blocks aka action.

http://msdn.microsoft.com/library/de...us/vbls7/html/
vblrfVBSpec7_6.asp

The problem is Properties are in that grey area where they're both.
Depending on what aspect of a property you are referring to.

The property itself is an attribute, while the get & set assessors are
'actions', which can be Overridden.

For example, You can apply the ConditionalAttribute to any method. This
includes the Get or Set assessor of a Property.

Property Name() As String
<Conditional("DEBUG")> _
Get
return m_name
End Get
<Conditional("DEBUG")> _
Set(ByVal value As String
m_name = value
End Set
End Property

Of course the above Get will not have the desired effect as its

returning a

value, and needs to be called in all cases...

Which is where generically I will include Property Assessors as methods. At

the same time generically I include Properties as attributes.

Notice that I am not a native English speaker, maybe I am misinterpreting
the meaning of method, procedure, and attribute. Why not use the terms

like that:

method: Sub, Function (if they are members of a class)
procedure: Sub, Function, Property (Get, Set)
attribute: Property

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Herfried K. Wagner [MVP]]

Hello,

"Tom Spink" <th**********@ntlworld.com> schrieb:

The term attribute does tend to confuse, as that's what the < and > are
called:

<StructLayout(Foo)> Public Structure Bar
Public Baz As Moo
End Structure

The <StructLayout(Foo)> is an attribute, that's what microsoft calls it.

ACK. The term attribute is overloaded, it applies to both, attributes, and
properties.

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Cor]

Tom,
Maybe Enlish it is not our native language but I think you misread
something.
Its funny :)) I had to smile.
Cor

[Cor]

Herfried,
To that Tom has to give the answer.
Strong one
:-)
Cor

[Jay B. Harlow [MVP - Outlook]]

Herfried,

Notice that I am not a native English speaker, maybe I am misinterpreting
the meaning of method, procedure, and attribute. Why not use the terms like that:

method: Sub, Function (if they are members of a class) When are they not a member of a class? Module & Interface perhaps? I
consider them methods in any Type (Class, Module, Interface, other).
procedure: Sub, Function, Property (Get, Set)
attribute: Property
For me method & procedure are synonymous (have the same or very nearly the
same meaning). Overall I consider procedure a type of method.

For me: Procedure is a carry over from RPG, COBOL, VB1 - VB6 days, while
Method is a carry over from C/C++/Java OOP days.

Because I favor OOP over VB6, I will tend to use method over procedure. When
I use procedure it will generally be in a VB6 context.

As you said Methods are actions, Property Get is an action & Property Set is
an action.

I consider both properties & fields to be attributes (lower case a). While
an Attribute (upper case A) adds meta data to any member or type.

Hope this helps
Jay

"Herfried K. Wagner [MVP]" <hi*******@m.activevb.de> wrote in message
news:OI**************@TK2MSFTNGP12.phx.gbl... Hi Jay,

"Jay B. Harlow [MVP - Outlook]" <Ja********@email.msn.com> schrieb:

Although I agree with you 100%.

You did notice I was specific to say Property _Procedures_
(by Procedure I mean the Get & Set assessors) and not just
Property. As the Get & Set assessors have statement blocks aka action.

http://msdn.microsoft.com/library/de...fVBSpec7_6.asp

The problem is Properties are in that grey area where they're both.
Depending on what aspect of a property you are referring to.

The property itself is an attribute, while the get & set assessors are
'actions', which can be Overridden.

For example, You can apply the ConditionalAttribute to any method. This
includes the Get or Set assessor of a Property.

Property Name() As String
<Conditional("DEBUG")> _
Get
return m_name
End Get
<Conditional("DEBUG")> _
Set(ByVal value As String
m_name = value
End Set
End Property

Of course the above Get will not have the desired effect as its

returning a

value, and needs to be called in all cases...

Which is where generically I will include Property Assessors as methods. At

the same time generically I include Properties as attributes.

Notice that I am not a native English speaker, maybe I am misinterpreting
the meaning of method, procedure, and attribute. Why not use the terms

like that:

method: Sub, Function (if they are members of a class)
procedure: Sub, Function, Property (Get, Set)
attribute: Property

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Tom Spink]

My response was a joke, e.g. we cannot yet perform operator overloading, so
why should we be able to overload attributes, even though it makes no
sense.... <g>

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit

"Maybe it's a game called 'Punish the User'"
"Herfried K. Wagner [MVP]" <hi*******@m.activevb.de> wrote in message
news:u1**************@TK2MSFTNGP10.phx.gbl...

Hello,

"Tom Spink" <th**********@ntlworld.com> schrieb:

I don't think VB allows attribute overloading ;-) SCNR

VB .NET cannot do it -- but we are able to overload the term "attribute"

;-)))

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Herfried K. Wagner [MVP]]

Hello Jay,

"Jay B. Harlow [MVP - Outlook]" <Ja********@email.msn.com> schrieb:

method: Sub, Function (if they are members of a class) When are they not a member of a class? Module & Interface perhaps? I
consider them methods in any Type (Class, Module, Interface, other).

Ooops. I forgot to mention interface, ...

procedure: Sub, Function, Property (Get, Set)
attribute: Property

For me method & procedure are synonymous (have the same or very nearly the
same meaning). Overall I consider procedure a type of method.

For me, methods are a subset of procedures. Some programming languages
don't allow defining classes etc., they allow procedures only. IMO these
procedures are not _methods_, because there are no objects (they do not
model an action an _object_ can perform).
For me: Procedure is a carry over from RPG, COBOL, VB1 -
VB6 days, while Method is a carry over from C/C++/Java OOP
days.
ACK.
Because I favor OOP over VB6, I will tend to use method over
procedure. When I use procedure it will generally be in a
VB6 context.
;-)
As you said Methods are actions, Property Get is an action &
Property Set is an action.
The implementation may perform an action, but it's not considered to be an
action. A property is used to model an attribute (no, not an attribute like
'ComVisible') of an object. If "an action" is performed in the property
procedure, I would write an explicit Get... or Set... method to make it
clearer, that I don't try to model an attribute. Notice that this is my
personal opinion.
I consider both properties & fields to be attributes (lower case a).
ACK.
While an Attribute (upper case A) adds meta data to any member
or type.

ACK.

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Herfried K. Wagner [MVP]]

Hello,

"Tom Spink" <th**********@ntlworld.com> schrieb:

My response was a joke, e.g. we cannot yet perform operator overloading, so why should we be able to overload attributes, even though it makes no
sense.... <g>

I am not sure if you understood me...

;-)

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Tom Spink]

LOL sorry. Let's just EOT it :-)

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit

"Maybe it's a game called 'Punish the User'"
"Herfried K. Wagner [MVP]" <hi*******@m.activevb.de> wrote in message
news:Oo*************@tk2msftngp13.phx.gbl...

Hello,

"Tom Spink" <th**********@ntlworld.com> schrieb:

My response was a joke, e.g. we cannot yet perform operator overloading,

so

why should we be able to overload attributes, even though it makes no
sense.... <g>

I am not sure if you understood me...

;-)

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Fergus Cooney]

Hi Jay,

You can obtain information about the members of a class using
System.Reflection [as you know :-)].

The help topic for MemberInfo says:
The MemberInfo class is the abstract base class of the classes used to
obtain information for all members of a class (constructors, events, fields,
<methods>, and <properties>).

Reflection includes both functions and subs under the tem methods. It
makes a distinction between methods and properties.

As I see it, a property (in its simplest form) is just a different
accessor for a field. I don't see fields as methods, and therefore don't see
properties as methods.

There are those who consider that writing a property that "takes action"
is bad design as they would define "action" as a side-effect - something not
desired in a property. It depends, of course, on how you define "action." :-)

Both "procedure" and "method" used to mean a routine that didn't return a
value, ie a Sub, but that distinction has been trampled on, RIP.

Just some thoughts.

Regards,
Fergus

[Fergus Cooney]

Hi Cor,

|| You should have seen the faces from the french people
|| when my mother was calling us on the camping

LOL

|| My mother is not speaking any language

!!

Regards,
Fergus

[Herfried K. Wagner [MVP]]

Hello,

"Cor" <no*@non.com> schrieb:

I think this can be an endless discussion but important is in
my opinion again what language are you using (speaking).
My child name is Kok and from my sister Con.
Cor is pronounced as Kok?
My mother is not speaking any language.
?!?
You should have seen the faces from the french people when
my mother was calling us on the camping where we where
when I was young.
How can your mother call you without speaking any language?
I think that when I am thinking in VB I use the word function
when I am talking about functions like Mid, Len and even String.
I then am talking about methods when I use things like
String.substring.

That's how I use them too. Substring is an action, a string can perform.
Mid, Len etc. are members of a class, but I treat them as functions because
they are not actions an object can perform.

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Herfried K. Wagner [MVP]]

Hello,

"Fergus Cooney" <fi******@tesco.net> schrieb:

As I see it, a property (in its simplest form) is just a different
accessor for a field. I don't see fields as methods, and therefore don't see properties as methods.
100% ACK. Both are used to model "attributes" of an object.
There are those who consider that writing a property that
"takes action" is bad design as they would define "action"
as a side-effect - something not desired in a property.
It depends, of course, on how you define "action." :-)
100% ACK.
Both "procedure" and "method" used to mean a routine that didn't return a
value, ie a Sub, but that distinction has been trampled on, RIP.

;-)

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Cor]

My mother, One, Dutch.

[Cor]

Fergus,
Nothing wrong with it, but native English speaking people often thinks that
the meaning of an English word makes things clear.
I heard that English is a poor language for describing things like my own
native language Dutch.
Why don't you try it to describe it once in a rich language. Lets say
Chinese.
And before you ask it. No I don't know anything about that language.

Cor

[Cor]

You two are so clever late in the evening, when Dutch people say "She
doesn't speak languages they mean she speaks only Dutch"

[Cor]

Fergus
It was just for fun, but let me say it in other words, there are a lot of
descriptions (not yours) but like the last 2 days when someone did write
"overide", who had the right to decide of the meaning of that word? When
they give another meaning for that word in China so what?
You can say in this program language the meaning of x=...................,
but that is all in my opinion.
Cor

[Jay B. Harlow [MVP - Outlook]]

Fergus,
I'm not going to get into a public debate of something that is largely
academic.

Hope this helps
Jay

"Fergus Cooney" <fi******@tesco.net> wrote in message
news:uG**************@TK2MSFTNGP10.phx.gbl...

Hi Jay,

You can obtain information about the members of a class using
System.Reflection [as you know :-)].

The help topic for MemberInfo says:
The MemberInfo class is the abstract base class of the classes used to obtain information for all members of a class (constructors, events, fields, <methods>, and <properties>).

Reflection includes both functions and subs under the tem methods. It
makes a distinction between methods and properties.

As I see it, a property (in its simplest form) is just a different
accessor for a field. I don't see fields as methods, and therefore don't see properties as methods.

There are those who consider that writing a property that "takes action" is bad design as they would define "action" as a side-effect - something not desired in a property. It depends, of course, on how you define "action." :-)
Both "procedure" and "method" used to mean a routine that didn't return a value, ie a Sub, but that distinction has been trampled on, RIP.

Just some thoughts.

Regards,
Fergus

[Jay B. Harlow [MVP - Outlook]]

Herfried,
I'm not going to get into a public debate of something that is largely
academic.

Hope this helps
Jay

"Herfried K. Wagner [MVP]" <hi*******@m.activevb.de> wrote in message
news:%2***************@tk2msftngp13.phx.gbl...

Hello Jay,

"Jay B. Harlow [MVP - Outlook]" <Ja********@email.msn.com> schrieb:

method: Sub, Function (if they are members of a class) When are they not a member of a class? Module & Interface perhaps? I
consider them methods in any Type (Class, Module, Interface, other).

Ooops. I forgot to mention interface, ...

procedure: Sub, Function, Property (Get, Set)
attribute: Property

For me method & procedure are synonymous (have the same or very nearly the same meaning). Overall I consider procedure a type of method.

For me, methods are a subset of procedures. Some programming languages
don't allow defining classes etc., they allow procedures only. IMO these
procedures are not _methods_, because there are no objects (they do not
model an action an _object_ can perform).

For me: Procedure is a carry over from RPG, COBOL, VB1 -
VB6 days, while Method is a carry over from C/C++/Java OOP
days.

ACK.

Because I favor OOP over VB6, I will tend to use method over
procedure. When I use procedure it will generally be in a
VB6 context.

;-)

As you said Methods are actions, Property Get is an action &
Property Set is an action.

The implementation may perform an action, but it's not considered to be an
action. A property is used to model an attribute (no, not an attribute

like 'ComVisible') of an object. If "an action" is performed in the property
procedure, I would write an explicit Get... or Set... method to make it
clearer, that I don't try to model an attribute. Notice that this is my
personal opinion.

I consider both properties & fields to be attributes (lower case a).

ACK.

While an Attribute (upper case A) adds meta data to any member
or type.

ACK.

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Fergus Cooney]

Hi Cor,

I understand. You mean she doesn't speak any <additional> languages. Which
is what I would hopefully have realised if my brain wasn't so tired after
clubbing all last night :-)

Regards,
Fergus

[Tom Spink]

Should have enabled Option Strict.

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit

"Maybe it's a game called 'Punish the User'"
"Fergus Cooney" <fi******@tesco.net> wrote in message
news:#z**************@tk2msftngp13.phx.gbl...

Hi Cor,

I understand. You mean she doesn't speak any <additional> languages. Which is what I would hopefully have realised if my brain wasn't so tired after
clubbing all last night :-)

Regards,
Fergus

[Herfried K. Wagner [MVP]]

Hello,

"Cor" <no*@non.com> schrieb:

It was just for fun, but let me say it in other words, there are a lot of
descriptions (not yours) but like the last 2 days when someone did write
"overide", who had the right to decide of the meaning of that word?
When they give another meaning for that word in China so what?
You can say in this program language the meaning of x=...................,
but that is all in my opinion.

That's a problem indeed. There are lots of programmers who are not native
English speakers. These programmers have problems understanding the
keywords, ...

http://brucem.mystarband.net/vbnet.htm

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Herfried K. Wagner [MVP]]

Hello,

"Tom Spink" <th**********@ntlworld.com> schrieb:

properties as methods.
100% ACK. Both are used to model "attributes" of an object.

Indeed I must agree. Unless you are talking about the Get and Set parts of
the property.

I use the terms "method", "property", "event", "attribute" more abstract,
language-, and implementation-independent.
Using a tool like ILDASM or .NET Reflector to disassembly or
decompile an Assembly clearly shows that there are two methods
created, a get_### and set_### (unless of course the property is read-
only or write-only).
ACK.
I'd class the property as an attribute, like you say Herfried, but the code within the Get and Set blocks as the method part of a property.
ACK.

as a side-effect - something not desired in a property.
It depends, of course, on how you define "action." :-)

100% ACK.

Totally Agree. Properties shouldn't be used to perform time-consuming
tasks, such as this:

Public ReadOnly Property AskUser() As DialogResult
Get
Return MsgBox("Foo", "Bar")
End Get
End Property

That is BAD.

The sample above is really good. AskUser is an _action_, it should not be
implemented as a property (attribute).
What *I* think is acceptable is something like checking for the
presence of your window handle:

Public Property SubTitle() As String
Get
Return m_Title
End Get
Set (Value As String)
m_Title = Value
If Me.IsHandleCreated Then RepaintMe()
End Set
End Property

ACK. I would accept this as a property too:

\\\
Public ReadOnly Property InstalledFonts() As FontFamily()
Get

' Enumerate fonts and return an array of FontFamily objects.
End Get
End Property
///

Sure, the code performs an action, but this action is transparent to the
user of the class. When implementing something like your 'AskUser' property
as a property, the action is not transparent to the user any more.

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Herfried K. Wagner [MVP]]

Hello,

"Jay B. Harlow [MVP - Outlook]" <Ja********@email.msn.com> schrieb:

I'm not going to get into a public debate of something that is largely
academic.

OK.

;-)

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Herfried K. Wagner [MVP]]

Hello,

"Cor" <no*@non.com> schrieb:

You two are so clever late in the evening, when Dutch people
say "She doesn't speak languages they mean she speaks only
Dutch"

That's how I understood it.

;-)

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Fergus Cooney]

Hi Cor,

|| Why don't you try it to describe it once
|| in a rich language. Lets say Chinese.

LOL

|| I heard that English is a poor language for
|| describing things like my own native language Dutch.

Here, we have two phrases for language that can't be understood. "It's all
Greek, to me", and "He's talking double Dutch" :-) I've looked on the net for
the origin of the phrase but can't find it. It's from the 1870's.

As for native Dutch, I'm pretty sure that it is able to express plenty of
things for which English is inadequate (and likewise for Greek).

Regards
Fergus

[Fergus Cooney]

Hi Tom,

|| What *I* think is acceptable is something like
|| checking for the presence of your window handle:

Indeed, an Enabled/Checked/whatever Property that <didn't> update the GUI
would be pretty useless!

Regards,
Fergus

[Fergus Cooney]

Hi Jay,

|| I'm not going to get into a public debate
|| of something that is largely academic.

A lot of academics would love the chance. :-)

Regards,
Fergus

[Fergus Cooney]

Hi Cor,

|| ... Lets say Chinese. And before you ask it. -
|| No I don't know anything about that language.

There is a strong debate about which language will become the World
Tongue. Many think that it will be (Americanised) English. Certainly in our
current period this looks the most likely.

However, there are an awful lot* of Chinese in the world. And it is a
country that has yet to exert its potential influence in the World arena.
There are plenty of people who think that major shifts are ahead and that
Chinese may well become the dominant language.

One thing's for sure - it's not going to be Cockney, Gaelic or Dutch!!

Forget English, Cor, it's time to start learning Chinese!! ;-)

Regards,
Fergus

* No, this doesn't mean that the Chinese are an "awful lot"!! Lol. That would
be "<is> an awful lot".

[Fergus Cooney]

Hi Cor,

I'm taking it all as fun, I hope you see my responses the same way. :-)

Regards,
Fergus

[Cor]

Hi Fergus,

There is a strong debate about which language will become the World
Tongue. Many think that it will be (Americanised) English. Certainly in our current period this looks the most likely.
Only a minority of the people on the world speaks English as native
language.
I gues when I count maybe maximum 400.000 that is nothing.
And when you think about that the US is the second largest spanish speaking
country in the world mayby even less.
However, there are an awful lot* of Chinese in the world. And it is a
country that has yet to exert its potential influence in the World arena.
There are plenty of people who think that major shifts are ahead and that
Chinese may well become the dominant language.

One thing's for sure - it's not going to be Cockney, Gaelic or Dutch!!
Once it was, but that is 300-200 years ago. Those languages where as
powerfull as now (Americanised) English
And therefore maybe there are so many sentences like "double dutch"," going
dutch" in the English language.

3 Years ago I did eat in a Chinese restaurant in Soho, I was thinking I was
in China, very nice.

Did you know that the main Polish swear words are "Cholera" and "Hollander"
:-)
The Netherlands did not alway be that polite nation like now.

Regards,
Cor

[Fergus Cooney]

Hi Herfried,

It was an interesting article. Amongst other conclusions - no doubt the
guy will bounce back and produce Hardcore VB.NET when he's found enough holes
in the Framework.

Shame about the background - it sure did my eyes in!

Regards,
Fergus

[Fergus Cooney]

Hi Cor,

:-))

Fergus

[Herfried K. Wagner [MVP]]

Hello,

"Fergus Cooney" <fi******@tesco.net> schrieb:

It was an interesting article. Amongst other conclusions - no
doubt the guy will bounce back and produce Hardcore
VB.NET when he's found enough holes in the Framework.

I posted the link because I remembered the author talks about programming in
Latin.

;-)))

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Herfried K. Wagner [MVP]]

Hello,

"Cor" <no*@non.com> schrieb:

Ist Heaven

???

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet

[Herfried K. Wagner [MVP]]

Hello,

"Fergus Cooney" <fi******@tesco.net> schrieb:

|| What *I* think is acceptable is something like
|| checking for the presence of your window handle:

Indeed, an Enabled/Checked/whatever Property that <didn't>
update the GUI would be pretty useless!

These properties change visual attributes of the object.

Regards,
Herfried K. Wagner
--
MVP · VB Classic, VB .NET
http://www.mvps.org/dotnet