WorldDMT is right. That saves the work of setting all the vars unnecessarily. When it comes to scripting, always think hard and find an efficient, shorter way to make your script work faster and use less resources if feasible.
Firstmate, if my post appears to be ignorant or disparaging (at least to you), I apologize. But my main aim is to tell people to like regex. For your info, I'm still learning about regex, and I know I won't be good at mastering it. Learning is a long, winding road that it's never enough. Again, I'm not trying to get people withdrawn from using other methods, identifiers, or commands made available to simulate regex. They're also good for scripting purposes but will come in a limitation as Hawkee suggested, hence not universal.
Aucun50 Wrote:
To the best of my recollection there was a guy who was fascinated by the tremendous amount of if statements himself...
| Quote: |
| Little thing called elseif and else might want to try them. |
I concur with Hawkee wholeheartedly. Regex is universal in just about every programming language known to date. By using tokens (other than the ones made solely for certain programming languages) that will only work for MSL and nothing else.
Aucun50, you don't like using regex is because you don't want or bother to understand how it works. Once you get some understanding of it, you'll find yourself fancying it more than you think.
Aucun50, you don't like using regex is because you don't want or bother to understand how it works. Once you get some understanding of it, you'll find yourself fancying it more than you think.
Ok SnoooP, I've updated the script to make sure it's a two-letter word ending in the vhost to match for the country codes, along with two addition of part and quit event. Let me know if there's any shortcoming that you find.
Ford, that is a good idea, but the problem is, if I have the output emitted via raw 323, the channel info will go to the bottom and the mode definitions go on top, which will become the opposite of what the original output is supposed to be.
Ever since I've learned about regex, I've come to a conclusion that it is not a best tool for a bad work kicker. Let's you have lots of bad words to add. Your regex string will get very, very long over time. (unless, of course, you use the line break identifier) but that will still look very untidy and you can get your remote file increased in size. The best method I have found is using hash tables with
to look for matches.
However, you can still use regex to match bad words stored in a text file. Something like this:
| Quote: |
| if ($hfind(badword,$1-,w,1)) { |
However, you can still use regex to match bad words stored in a text file. Something like this:
| Code: |
| if ($regex($1-,/(?:^| )(\Q $+ $replacecs($read(swear.txt,n,1),\E,\E\\E\Q,$chr(32),\E|\Q) $+ \E)(?= |$)/iS)) { |
You mean to have an asterisk symbol added? If so, I have added it so it simulates the default output.
Plus I don't see how raw 322 will check the "whole list" when it only returns the channel info you've specified.
napa182, give me your best suggestion so I can learn from it. I'm sure there is a way to keep the list window closed upon the trigger of this script.
