« first day (7 days earlier)      last day (4836 days later) » 

2:50 AM
I have two answers on my question, "Obfuscated Hello World", that are the same length and will most likely not be beat by any other language.
Are there any guidelines in place for an issue like this?
 
3:27 AM
Ummm....
Lemme check. :-)
Are you talking about my answer and gnibbler's?
@Bass5098 Usually, if there is a clear winner, I accept it. In the case of a tie, usually I go by the "fastest gun in the west" rule.
Certainly, that is how Anarchy Golf does it: shortest pre-mortem solution, tie broken by favouring the earlier-submitted entry.
 
3:56 AM
/me is trying to get motivated to answer more golfing questions.
 
Which problem are you going for?
 
I'm thinking of either the globbing one, or maybe bogosort. :-P
Wow, @gnibbler's rep, like, skyrocketed. O_o
I should write a GolfScript interpreter. I've been meaning to for ages.
I originally got halfway through writing one in Java, but then I decided that Java sucks too much. :-P
I'll probably write a C++ version, and maybe a Scheme version too.
'Cuz, like, someone on this site has to carry the torch for Scheme, right? ;-)
 
4:18 AM
lol, so much love for golfscript?
 
Yes.
Some of us were talking about writing GolfScript entries for Google Code Jam.
See, the biggest problem with GolfScript is that, using the reference Ruby interpreter, it's too slow.
So, I have half a mind to write an interpreter that, well, runs faster.
It's too bad that GolfScript is not easy to compile to object code without doing a lot of flow analysis.
 
That would actually be awesome
 
I agree. :-)
 
set up a public repo and I'm sure you'll get more than one contributor from here
 
I bet. :-)
 
4:23 AM
You take part in code jam every year?
 
@Juan I have since 2006.
That was the final year on the TopCoder platform (which I dislike). 2008 heralded the GAE-based platform, which I like much better.
 
How far do you get? I never get past the 2 round
 
Good news for all of you!
0
Q: UserScript to fix the code-size argument once-and-for-all!

George EdisonCurrent version: The current version of the script is 0.15. I was inspired by this Meta post to write a UserScript that would automatically tally up the size of code blocks and display the count underneath. The advantage provided by the script is that it brings uniformity in regards to line-...

I have been hard at work on a small UserScript to help keep track of code size.
It will also display the length of the shortest piece of code on the page near the top too.
Feedback is appreciated.
 
Great! Much apreciated, I'm gonna give it a try now
 
4:42 AM
@Juan Neither do I.
@Juan go-hero.net/jam/10/name/cky for stats. :-)
@GeorgeEdison How does it choose if there are multiple shortest entries?
@GeorgeEdison Also, how do you make it filter out HQ9+ and other nonsense entries?
 
@Chris: Well, as for multiple shortest entries, it doesn't really matter since it only displays the length of the shortest entry.
Also, for HQ9+, I haven't decided how to deal with those yet.
 
@GeorgeEdison Ah, that makes sense.
 
This script is still in its infancy.
 
@GeorgeEdison *nods*
 
Any ideas are welcome.
By the way, did it install and run okay?
 
4:48 AM
@GeorgeEdison I don't have Greasemonkey installed yet. I'll get around to it, but right now I'm coding a GolfScript interpreter in either C++ or Scheme. :-P
 
@Chris: You should write the interpreter in GolfScript.
 
@GeorgeEdison That's too easy: ~
 
@GeorgeEdison Yeah, that question sounds hardcore. :-P
 
5:06 AM
@Juan: Did it work?
 
5:35 AM
@GeorgeEdison like a charm
 
 
14 hours later…
7:42 PM
Anyone here that knows golfscript? I'm having a really weird issue
 
 
3 hours later…
10:56 PM
@Juan, care to elaborate?
 
11:19 PM
@gnibbler I'm getting different results in the perl interpreter and the ruby one. The code's at codegolf.stackexchange.com/questions/501/…
I used the perl interpreter to debug the script (It tells you what it's doing step by step), the tried on the ruby version once I was confident it worked.
The interpreter begged to differ.
 
11:44 PM
I didn't even know about the perl interperter :) I'll take a look for you
 
It's great for debugging, you can get a step by step explanation of the execution
Anyway, thanks for checking. I can't imagine that going through that mess of a code can be easy!
 
@Juan, I just posted another gs answer. After I write up the analysis I'll look at yours
 
@gnibbler much appreciated
 

« first day (7 days earlier)      last day (4836 days later) »