AutoHotkey Community

I meant, buggy codes are posted in other languages. The 99 bottles of beer challenge provides several examples. If you find my functions acceptable, post it, with a url to here.

This is added to k to get the next trial divisor, not divisible by 2, 3 or 5, as the comment next to function header tells. It is very easy to verify. Start with e.g. k = 7. The SubStr expression tells that the next divisor is 4 larger, k = 11. For k = 11 the SubStr expression tells the next divisor is 2 larger, 13, and so on. We get into a cycle of length 8, so we don’t need entries for never encountered k (mod 30) values, indicated by “-“ in the haystack.

Count how many of n random throws in a square falls into an inscribed circle. It yields an estimate of pi.

Am going through the posting so far to cleanup syntax-wise (indentation and casing). It looks like the syntax-coloring for AutoHotkey stopped working.

Ok, one request: if you post something to the Rosetta Code site, please use proper indentation and casing.



And please use an indentation of 2 spaces per "tab"

TY

Thanks for cleaning up the casing and indentation.

Please add autohotkey as a language on your user page, see first post for instructions.

We could write a little robot to fix the casing and indentation...
I will try to get the highlighting back online, once i update the lexer a little.

Hi,

I created an ambiguous function that matches RosettaCode's AMB challenge. But I don't know how to add it to the page. :-/

http://www.autohotkey.com/forum/viewtopic.php?p=275987#275987

_________________
Scripts - License

Well, it may not equal the examples of most other languages (they are usually lowercase), but it does confirm with the documentation casing. The fact that AutoHotkey is case-insensitive and generally very "forgiving" could be explained on the language page.

I suggest lowercase for variables and proper mixed case for keywords. I also suggest using descriptive variable names, even if the tendency is to create short code, I think the site is a proper outlet to clarify what is going on in the code, not necessarily provide the fastest and most condensed code. One could add variations if applicable, sure, but per default please some consistency.

To make the syntax-coloring stand out more, it helps to avoid using variable names that are also AutoHotkey keywords.

Just my 2 €cts

How about a "disclaimer" like this one? http://www.rosettacode.org/wiki/FizzBuzz#AutoHotkey

hmm, yeah i think that would be good for most ahk scripts posted on RosettaCode. But I lowercased mine anyway. xD

_________________
Scripts - License

Mode of a list of numbers is the number, which occurs the most frequently in the list. This function sorts and scans the list once to find the Mode. The delimiter can be given in the second parameter, default to space.
Another approach was to convert the numbers to variable names (e.g. by appending “v” and replacing “.” with “_”), and count in these variables the number of time the corresponding value occurs. We’d have difficulties with equal numbers written differently, like 10, 10.0, 1.0e1, therefore the list has to be first scanned and the numbers converted to uniform notation, e.g. with “SetFormat FastFloat, 0.16e” and adding 0 to each, making the function slow and complicated.

@infogulch: I added your code.

thanks, n-l-i-d


Edit: what about the Tasks Not Implemented in AutoHotkey ?

_________________
Scripts - License

Can someone post my functions, too?

I added all of Laszlo's functions, apart from the MontePi, couldn't find that one...

Heh, we're gonna need a full-time Rosetta Code updater just to add stuff posted here.
I looked at editing them, but couldn't figure out how to do it.

Here's another one: Forward Difference


I tried to format it nice, but it can be reformatted.

Edit: oh, and what about Laszlo's MD5?

_________________
Scripts - License