AutoHotkey Community

Ta!

I feel Scripts & Functions suits this topic..

I was set against that idea a few weeks ago when tinku99 asked me......but in light of Laszlo's recent activity there is an awful lot of working code here. It would seem my argument no longer holds water. SKAN, if you believe it belongs in S&F, I don't object.

I think this thread should remain here since, as you noted, its purpose is not directly related to that forum. I think it would be better to create a separate thread in S&F which hosts the finished RosettaCode functions.

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

I oppose redundant posting of code, especially within the forums. From my correspondence with tinku99...The same scripts should definitely not be posted here in General Chat and also in S&F.

I do believe the Rosetta codes need to be promoted as much as possible, but not by duplicating every script. Several people have done an amazing job with this project; and it was a brilliant idea by tinku99 to begin with.

I have thought for some time that something should be done with Jon's "Catalogue of Scripts" sticky topic in the S&F forum. Since Jon moved his catalogue to the wiki years ago, the only purpose of that thread is to redirect people to the wiki. I propose to do the same with that sticky topic as Titan did with the AutoHotkey.net sticky: cut it down to one post to inform users of the many working code examples on the Wiki and on Rosetta code. It should serve as an advertisement so to speak.

While I agree that redundancy is typically bad form, this thread has already constructed itself in a manner that is not conducive to the spirit of threads you would typically find in S&F so simply moving the thread would equally be bad form, IMO (danged if we do, danged if we don't).

Here's my thought along the lines of your idea: Make a sticky note in S&F that redirects to our section of the Rosetta Code Wiki and the original thread, like this:



That way the sticky can present the information with a more reader-friendly logic that the thread itself simply doesn't have while leaving the thread in its original forum and avoiding code rendundancy.

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

I could not login for past few hours owing to some phpBB Critical Error and so I was unable to respond.. IMHO, the gems from Laszlo always belong to Scripts and Functions. Since sinkfaze feels otherwise, I will remember to bump and move this topic to Scripts and Functions when it fades out to the second page.

@sinkfaze
I agree with everything in your latest post. That's what I propose to do.


While I certainly agree with this statement, as sinkfaze alluded: this thread is a mess, and contains as much material that doesn't belong in S&F as useful code.

Also, even if this thread is moved to S&F, unless it is made sticky (which I strongly oppose: five stickies in one forum is more than enough) this thread won't stay visible there either. I believe that combining an explanation of Rosetta code with Jon's first post in the Catalogue thread is the most consistent and productive option. The revised thread could then be titled something like, "AutoHotkey Wiki + RosettaCode Challenges."

That was not the point. People tend to NOT CLICK General Chat topic in Forum search results. As for me, I always confine my search to "Scripts & Functions" and/or "Ask for Help"



Anyways! I have no problem with that..

Shell sort of comma separated lists:

Awesome, I've done it.

You could split this topic by individually selecting all of the useful code posts and moving them to a new Scripts & Functions thread, leaving the discussion posts behind.

FIFO's, or stacks can be implemented via global arrays. Their names are passed to the stack handling functions, so many stacks can be used at any time:

The function for the Knuth shuffle creates the array internally from a list, and returns the shuffled list, for easy display:

A short recursive (slow) function for the Longest Common Subsequence task (based on the Python code):
The following function uses dynamic programming, and it is much faster. It is based on the Java program posted to rosettacode:

We can find all Non Continuous Subsequences by selecting those 01 sequences, which do not consist of only one block of 1’s. It is very easy with regular expressions. At the end we have to translate 1’s to the sequence entries corresponding to their position: