vbNullString

[Robin]

Can't let LGM give all the Knowledge ><

vbNullString > ""

[Rian]

How much faster is vbNullString? Is there any way to test it?

[Robin]

><

Well, there was no way I was going to read everything you copied and pasted from another site.

I think you should have just posted a link to the site you got it from -_-;;

[Spodi]

I wouldn't really worry too much about these kinds of optimizations unless you are very, very desperate for speed (or the routine is being used a few hundred times per second). When saying "" < vbNullString, we're basically saying 0.001ms < 0.0008ms. Point being, slightly slower then fast is still fast. :wink:

[Robin]

I wouldn't really worry too much about these kinds of optimizations unless you are very, very desperate for speed (or the routine is being used a few hundred times per second). When saying "" < vbNullString, we're basically saying 0.001ms < 0.0008ms. Point being, slightly slower then fast is still fast. :wink:

I am not saying you should just go through your source and replace all '""' with vbNullString (but you can in the right circumstances), but that you should get into the habit of writing it instead of "".

Good habits are very valuable in programming

[Spodi]

Good habits are very valuable in programming

Very true.

[Liz]

You could just hit replace all, if you wanted to, but like Spodi says, it really doesn't make all that much of a difference.

[Robin]

You could just hit replace all, if you wanted to, but like Spodi says, it really doesn't make all that much of a difference.

Some instances of '""' are needed.

[William]

You could just hit replace all, if you wanted to, but like Spodi says, it really doesn't make all that much of a difference.

Some instances of '""' are needed.

Actually no. It's only used for the Quote = """" And I dont even think that constant is used.

[Misunderstood]

You could just hit replace all, if you wanted to, but like Spodi says, it really doesn't make all that much of a difference.

Some instances of '""' are needed.

Actually no. It's only used for the Quote = """" And I dont even think that constant is used.

Actually no. I believe some instances of "" are needed, I don't remember which ones, but there was a discussion about this earlier where this came up.

[William]

Oh yeah, guess it can be bad to use vbNullString when you save data with PutVar. Not sure thought, for example:

Call PutVar(FileName, "NPC" & NpcNum, "Name", vbNullString)

Still it should work.. so I dont know.

[Robin]

Well, I never changed it on Vanilla Mirage, but on my source I remember having several instances of '""' which needed to be kept.

Otherwise the thing just didn't work >

[William]

I think i changed all in my source, and that seems to work just fine

[Misunderstood]

vbNullString is just that, a null string, "" is an empty string, fairly different...
vbNullString doesn't really take any more space, "" does.