Re: isElement - determining if an object is an element
- From: "Aaron Gray" <ang.usenet@xxxxxxxxx>
- Date: Thu, 31 Jul 2008 17:15:52 +0100
"Henry" <rcornford@xxxxxxxxxxxxxx> wrote in message
news:bb9f4738-eba2-4760-9ef8-db0da0b38598@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jul 31, 4:19 pm, kangax wrote:
<snip>
... . It appears, though, that the need
for "isElement" exists.
How does that appear? It appears that there is a desire and that the
desire is being serviced but nothing has yet suggested a need.
You have to double or tripple up on constructors to do the same trick. Its
neater with one constructor and using what in static class languages is
called overoading.
Aaron
.
- Follow-Ups:
- References:
- isElement - determining if an object is an element
- From: Aaron Gray
- Re: isElement - determining if an object is an element
- From: Henry
- Re: isElement - determining if an object is an element
- From: Aaron Gray
- Re: isElement - determining if an object is an element
- From: Aaron Gray
- Re: isElement - determining if an object is an element
- From: kangax
- Re: isElement - determining if an object is an element
- From: RobG
- Re: isElement - determining if an object is an element
- From: kangax
- Re: isElement - determining if an object is an element
- From: Henry
- isElement - determining if an object is an element
- Prev by Date: Re: isElement - determining if an object is an element
- Next by Date: Re: isElement - determining if an object is an element
- Previous by thread: Re: isElement - determining if an object is an element
- Next by thread: Re: isElement - determining if an object is an element
- Index(es):
Relevant Pages
|