 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"nemesis" <nam### [at] gmail com> wrote in message
news:4bd85eb7$1@news.povray.org...
> Invisible escreveu:
>> OK, so I decided to try to use X to actually do something *useful*.
>>
>> Big mistake.
>
> there, made a template for your posts.
>
> --
> a game sig: http://tinyurl.com/d3rxz9
LOL!
Cheers Dre
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 4/28/2010 6:49 AM, Invisible wrote:
> Invisible wrote:
>
>> set trans = CreateObject("NameTranslate")
>> trans.Init 3, ""
>> trans.Set 3, "domain\user"
>> set name = trans.Get(1)
>> WScript.Echo name
>>
>> Only trouble is... it doesn't work.
>
> Oh my god.
>
> Apparently you have to delete the word "set" on line 4. And then it
> works perfectly. WTF?
>
As a rule, the word "set" is almost **never** used in VB, at all. I
think there may be some obscure cases where you may use it, but, in
general, its little more than a hold over from ages past, when it was
mandatory. It hasn't been in most BASICs for... at least DOS1.0, maybe?
--
void main () {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> yeah, nothing like good ol' RTFM instead of trial and error...
>
> To be fair, this is old tech, so MS doesn't exactly make it easy to find
> the documentation when you could be upgrading to VBNET.AWSOME.
I thought the expected upgrade from VBS/JavaScript was to powershell?
http://en.wikipedia.org/wiki/Windows_PowerShell
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> OK, so I decided to try to use X to actually do something *useful*.
>>
>> Big mistake.
>
> there, made a template for your posts.
You forgot the "obviously this is impossible" part :-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 29.04.2010 05:34, schrieb Patrick Elliott:
> As a rule, the word "set" is almost **never** used in VB, at all. I
> think there may be some obscure cases where you may use it, but, in
> general, its little more than a hold over from ages past, when it was
> mandatory. It hasn't been in most BASICs for... at least DOS1.0, maybe?
That would be true for "let".
As for "set", it has been mandatory at least in every version of VBA
that I ever touched. Not sure about full-fledged VB though.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
And lo On Wed, 28 Apr 2010 15:49:14 +0200, Invisible <voi### [at] devnull> did
spake thusly:
> Invisible wrote:
>
>> set trans = CreateObject("NameTranslate")
>> trans.Init 3, ""
>> trans.Set 3, "domain\user"
>> set name = trans.Get(1)
>> WScript.Echo name
>> Only trouble is... it doesn't work.
>
> Oh my god.
>
> Apparently you have to delete the word "set" on line 4. And then it
> works perfectly. WTF?
and don't forget good practice in trans = nothing when you've finished
with it ;-)
--
Phil Cook
--
I once tried to be apathetic, but I just couldn't be bothered
http://flipc.blogspot.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Patrick Elliott <sel### [at] npgcablecom> wrote:
> As a rule, the word "set" is almost **never** used in VB, at all. I
> think there may be some obscure cases where you may use it, but, in
> general, its little more than a hold over from ages past, when it was
> mandatory. It hasn't been in most BASICs for... at least DOS1.0, maybe?
The rule actually is if you do object assignment you use set if not then you
don't.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott wrote:
>>> yeah, nothing like good ol' RTFM instead of trial and error...
>>
>> To be fair, this is old tech, so MS doesn't exactly make it easy to
>> find the documentation when you could be upgrading to VBNET.AWSOME.
>
> I thought the expected upgrade from VBS/JavaScript was to powershell?
> http://en.wikipedia.org/wiki/Windows_PowerShell
Depends if you want it in a shell or not. VBS runs in web servers too.
--
Darren New, San Diego CA, USA (PST)
Linux: Now bringing the quality and usability of
open source desktop apps to your personal electronics.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott escreveu:
>>> OK, so I decided to try to use X to actually do something *useful*.
>>>
>>> Big mistake.
>>
>> there, made a template for your posts.
>
> You forgot the "obviously this is impossible" part :-)
Yeah, but I guess it's implied in "Big Mistake", plus it sounds better
as a comic punchline. :)
--
a game sig: http://tinyurl.com/d3rxz9
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 4/29/2010 1:05 AM, clipka wrote:
> Am 29.04.2010 05:34, schrieb Patrick Elliott:
>
>> As a rule, the word "set" is almost **never** used in VB, at all. I
>> think there may be some obscure cases where you may use it, but, in
>> general, its little more than a hold over from ages past, when it was
>> mandatory. It hasn't been in most BASICs for... at least DOS1.0, maybe?
>
> That would be true for "let".
>
> As for "set", it has been mandatory at least in every version of VBA
> that I ever touched. Not sure about full-fledged VB though.
Yeah, was thinking of "let".
--
void main () {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
