Did you know that array[index] and index[array] do the same thing in C?

int a[] = {1,2,3,4,5};
a[3] == 3[a];

Exactly, find a new or weird idea that sucks you right in.

poorly

I'm at the point where it's readable, but incredibly poorly written. I've still got an algorithm I translated from Python to C about a year ago, saved just for giggles. It's a direct translation that mallocs new objects where Python created new ones, and leaks so much memory it's barely usable.

ST B 121

ST C 101

PR B

PR C

fucking vmposters, get off my board

It's worth noting that div() is from a time when compilers weren't smart enough to merge a mod and a div into a divmod.

It would also be a good intermediate step to try and learn more about python's assembly, but there aren't many resources for doing that online. Assembly is good because it teaches you what's going on inside your computer, so it would be a good intermediate step to learn what happens to run python code.

What he means is that the code is written the way you'd write it in C. In Python the preferred method would probably be more functional.

If we're going that route, isn't C just viewed as Assembly?

In Haskell:

nonRepeat s = head $ filter (\c -> 1 == length (filter (==c) s )) s

The game is both incredibly good and incredibly hard.

While this is really awesome, I don't think it's going to be replacing actual programmers anytime soon.

Shoot, you're right, edited.

C master race.

The type system is not as rigid as C/C++

IDK about C++, but C's type system is pretty darn relaxed. You can easily convert a floating point number to a pointer, then use that as an index into the array 5.

double x = somenumber;
printf("%u",5[*(signed*)&x]);

Except that this is actually mocking him.

Holy shit it works!

Bitbucket seems to be pretty ok.

Another fun one:

for(byte i = 0; i < 256; i++)

This kind of utter bullshit makes me mad in a very specific way. A programming language should just be a programming language. No politics, just a specification and maybe a compiler/interpreter, etc. If a community dedicated to a language wants to have it's own stupid microagression rules, I would disagree, but fine, whatever, it's just a website. But you can't just go making that part of the language itself. I almost feel like this would be breaking the sanctity of the language. In the end, all a language is is a collection of rules for a computer to follow to get meaning out of some text/flowchart/whatever. Computers can't understand politics, so keep that garbage away!

</rant> </anger>

Just to clarify for OP, I think &gt should render as '>'. (a bug in Voat?)

Yeah, C's great because you have to have some ideo of what's underneath all the abstractions, so you have a better idea of what's going on when you use something like C++.

I remember once mentioning I had used 'hacky' code to my mother once, and dispite my efforts to explain the term to her (and getting two new computers since then) she still blames any issues I have on it.

Just off the top of my head, it sounds to me like this may reduce to the Travelling Salesman Problem, making this a very difficult problem to solve for large data sets, like you wanted. If you're OK with getting a non-optimal answer, some kind of heuristic.

Not quite what you want, but hackertyper.net is relevant.

Exactly. These rules are for space, most programming doesn't need them.

I always just assumed it was just Jeff Atwood typing real fast.

I'm partial to C myself. I'm the kind of lunatic who needs to be able to 'see' the Assembly from inside the programming language, so I tend to find things like C++ too opaque.

I love making softwares!

import this

main() {
        puts("C++ scum");
}