How to use flags in my own UDFs?

[SlowCoder74]

I like the way flags are utilized in AutoIT functions, e.g. stringstripWS("text",flag).  I'm guessing there's a bitwise check on the supplied flag value.

Is there a good example of how to utilize that in my own UDFs?

[guinness]

BitAND is the clue.

[Melba23]

SlowCoder74,

Look at my ChooseFileFolder UDF - the _CFF_Check_Display function does that sort of thing using BitAnd.

M23

[SlowCoder74]

Exactly what I was looking for.  Thanks!

[SlowCoder74]

Though there are tricks, classic ASP doesn't internally allow optional arguments.  Flags have been a great way to maintain compatibility with my ASP projects while adding functionality to the subs/functions themselves.

In ASP and VBScript I've used "flags" in a different way, by setting up a string argument with possible values like "[Opt1][Opt2][Opt3]", where each of the "[Optx]" parts was a "flag".  In one way, it makes it fairly easy to add functionality to the subs/functions, and also makes the arguments easily readable.  The downside of using these types of flags, is that if you are supplying a large number of options/flags, the call to the procedure can be long enough to cause readability problems, especially if you are nesting multiple procedures.

e.g. x=ShowNameParts("[Last][First][Middle]")

With the numeric flags, readability of the actual options is decreased, but readability of the line is better.

e.g. x=ShowNameParts(7)