Viewing profile — PySlice

Yes, bounds checking are unnecessary, you don't need those _s() functions - NSA director

However it's going to take some time to learn all the gotchas in string functions... Failing to zero-terminate strings (strncpy), potential buffer overflows (many), global internal…

I think your comment is spot-on. A good Perl programmer can do wonders, but if you add just one average programmer to the team (without a very extensive training), he can write stu…

Yeah, it's so annoying. Everytime I go to the moon I remember how I hate that uneven gravity!

+1 just because of "I would personally prefer to tinker with a Brainfuck implementation than spend any amount of time in any bar"

I guess they just ran out of names, after deprecating java.util.Date (remember that there's also java.sql.Date).

Never using a space before the paren is more consistent. I don't know why people put a space there...

Same here...

I don't see how that invalidates my explanation In F# I would certainly call it "callTwice" too: let callTwice aFunction y = aFunction (aFunction y)

So enlighten me.

If programmers of functional languages were better at naming things, it would be easy. Let's rename g to callTwice and h to aFunction : function callTwice(aFunction) { return funct…

Well, I guess this is going to be a fairly down-to-earth language.

What one can learn from Perl: When programming in a language you hate, don't take naming arguments for granted. It could be worse: you could be programming in Perl, where all argum…

I don't think that is a misconception. Perl is the language with the highest occurrence of "subtle" and "ambiguous" in its documentation and tutorials that I have ever seen. Humans…

> bring a knife to a gun fight > If the goal of the competition is to slice apples What?

Perl eats C++'s "most vexing parse" for breakfast.

The standard music notation and the criticism this new notation receives here look to me as if we were stuck for centuries with only one programming language, C++, and nobody could…

After your excelent suggestions for names (makeMapper and makeGetter, they make everything easier, thank you), I'll try answering this, with a F#-like syntax using redundant parent…

Your example is great, but it would be even more convincing if it used list comprehension syntax such as totals = [order.total for order in orders] (like some other poster in this …

Can I upvote you twice? More than once I have found about a new technique in language A and thought: "Wow, this is clever". Then sometime later I learnt language B where that techn…

I went in the other direction and it was enlightening too. I learned how useful hash tables can be, and that a word count algorithm need not be a complicated assignment full of seg…

That logic is just a starting point (just to avoid the "I don't need it, why can't you be just like me?"), not the whole thing. Then you have to take into account a few other crite…

Which is better?

I remember some years ago when I was glad Java 5 had got some really practical new features. I didn't program in Java back then, but I wanted the language to evolve (maybe I was go…

> Thus, getters and setters should not be encouraged. Damn, so why are they encouraged in Java? 11 out of 10 frameworks insist that you write getters/setters so properties can be a…