10/10, does what is says.
Simple yet effective. Good job Rolo.
@Ghost-Writer
1) while (%x < 15) { } <- You need to set off the while loop. At its current state, it will never work, as %x does not yet exist. He also started it at 2 for a reason, as white text won't show up, and black text is normal. Also, yours will never reach 15, as it is < when it should be <= in this case.
2) var %x $iif(%x,$calc(%x + 1),1) <- $iif is pointless. It will always do $calc(%x + 1) since %x will always exist in the loop. How about just inc %x?
3) echo -a $+($chr(3),%x,$1-) <- This will only flood the user who uses it, not the channel or query.
@Jethro_
Nice usage of regex, although it kills readability.
@Ghost-writer
A hash table would be pointless. You'd have to make the table, then load the file, add/delete nicks and such and then save. It'd require more time to process the hash table code than the code as it is. Besides, live hash tables cannot be viewed easily without saving to a file. Although, using addresses would be a tad better.
@Master-Of-Death
Looks like you need to read up on aliases before you attempt this on your own.
@D34th
I'll rate it when I get the time, but nice usage of a dialog, as those are always a pain to do layouts by hand. I say 8/10.
Remove all 3 constants, as they're not needed in this short of code. A numeric value that is hard-coded isn't going to change. Now if you just used a double NAME, then it might change. So for the Temperature function:
void Temperatures(double fahrenheit) {
double celsius, kelvin;
celsius = fahrenheit * 1.8 + 32.0;
kelvin = celsius + 273.15;
printf("Fahrenheit: %.2lf\n", fahrenheit);
printf("Celsius: %.2lf\n", celsius);
printf("Kelvin: %.2lf\n", kelvin);
}
@Jethro_
You went off rambling about nothing. If his code is fine, don't go off on something else that is 100% irrelevant. I don't care if the information is correct or not, it's of no use to the author who never requested that you go into "A History of mIRC".
@Master-Of-Death
Go kiss ass elsewhere. And you really should read below.
Read the code, if it has issues, then comment. Don't add stuff that a) makes the code worse or b) has nothing to do with the author's original intent. If you really wish to assist users, you'd make an attempt to understand what they are trying to code, and then you comment with relevant information.
@gooshie
You give perfect example of a useful comment, thanks for not failing
Dude, just read the damn code. Where does he imply that $rnick(chan,#) is its usage here?
alias rnick { return $nick(#,$r(1,$nick(#,0))) }
Read the code. And you're not benefitting anyone by not reading what is going on in the code. Don't blindly go and call someone out if you haven't even looked at it.