Are posts scanned for language? Just wondering because MSDN's was broken or so they say.
What happens if you type in f-word e.g.?
Printable View
Are posts scanned for language? Just wondering because MSDN's was broken or so they say.
What happens if you type in f-word e.g.?
You shouldn't type ****.
In addition to what Marty said, you'll also likely get a warning from a moderator saying that profanity is a violation of the acceptable usage policy of this site. ;)
Brad!
Are you talking about code? Because you sometimes post code that has been filtered because variable names contain inappropriateness.
Code:Const BA****INERY = 1;
If words are getting partially filtered, then send Joe or me an email with the word and what is getting filtered. We can adjust the filters to only do full words versus partial where it makes sense.
Brad!
This one gets hit by the profanity filter. This is also used as a UDT in a browser for folder routine in VB6. It comes out as ****EMID
Since we are talking about a User Defined Type, then that is easy to change with no functionality loss by simply removing the T, which is what I do when I post it. But I thought I'd point that out.
The VB UDT is:Code:'with the T removed
Private Type SHIEMID
cb As Long
abID As Byte
End Type
Private Type ITEMIDLIST
mkid As SHIEMID
End Type
I think the MSDN guys should take possible word filters into account when naming their types.
This one has caught me out before and I have said to someone "you can't put asterisks in variable names." 9 times out of 10 it is me who looks stupid and not the poster. :D
:lol: This brings back memories. I remember the first time I posted code that used those two UDTs and, of course, the asterisks appeared and for the life of me, and the longest time, I couldn't figure out why. :sick:Quote:
Originally Posted by visualAd
SH_ITEMID would be a sensible alternative.
SHITEMID --> works for me. :)
Slight change made to system. We'll leave the change unless we see issues down the road.
Brad!