129 karma · joined October 15, 2012
This is output from the WORDS program http://archives.nd.edu/whitaker/words.htm
=> quod: Pronoun
who; that; which, what; of which kind/degree;
person/thing/time/point that;
who/whatever, everyone who, all that, anything that;
any; anyone/anything, any such; unspecified some; (after si/sin/sive/ne);
who?, which?, what?; what kind of?;
lesser: Adverb
with respect to which;
lesser: Conjugation
because, as far as, insofar as; [quod si => but if];
--
"[The greatest seducers in history] aggressively escalated physically with every woman they were flirting with. They began touching them immediately, kept great body language and eye contact... Even when a girl rejects your advances, she KNOWS that you desire her. That's hot. It arouses her physically and psychologically."
"Decide that you're going to sit in a position where you can rub her leg and back. Physically pick her up and sit her on your lap. Don't ask for permission. Be dominant. Force her to rebuff your advances."
"Pull out your cock and put her hand on it. Remember, she is letting you do this because you have established yourself as a LEADER. Don't ask for permission, GRAB HER HAND, and put it right on your dick."
--
This is not okay. This is sexual assault trumped up as "Dating Advice".
Thankfully there is a report button: http://www.kickstarter.com/projects/tofutofu/above-the-game-...
Also shameless Shmoo group plug: http://tinfoilhat.shmoo.com/
Generally speaking mods close questions for quality reasons or because they don't fit the format of the site. The F.A.Q. is fairly explicit about what SO is for and while I can only speak for my self, I do my best to adhere to those rules when closing questions.
As for locking questions, that is a bit more subjective but in most cases they are locked because they are well known and they have been solved. Being that there is no need for additional answers they are closed such that you don't have the spam issue of "Thanks" posts.
I doubt that there is a systemic pattern of censorship and rather what you see is the normal operations of a very large and famous Q.A. site with a very specific purpose.
I find in programming, like in many creative disciplines, there isn't a singular Aha! moment but rather a series of them. One must continuously learn and work. The process is generally prodigious amount of toil and frustration for brilliant moments of elation and clarity.
The ability to do large projects comes from doing large projects. You can read all you want about project management and software design but until you are in the thick of it, none of that matters.
I became a much more liberated and free programmer when I accepted that all of my code is crap. In point of fact, most code is crap and in light of that I strive not to write good code but to write better code than I did yesterday.
In short, forget about worrying. If you want an idea of organization then read through the source of a large project. Better yet, start one. Think through the issues that arise as you try to manage a large project. You will fail, this is okay, good even. Learn through failure and don't invest your self in your code. You are not your code. Be proud of your success and toil but don't worry what others think. We were all bad programmers once and most of us still are.
Note: This is based on my personal taste and experience. I am a professional in the IT industry with over ten years programming experience. Not a huge amount I guess, but definitely not that shabby. Currently I am not a professional programmer per-say, but it makes up a large amount of my daily work.
http://freeloaderproductions.com/theyre-made-out-of-meat-/-d...
Lack of experience isn't going to kill this project, lack of a spec will. Learning to program is like any other skill, put the time and effort into it and you can learn, but if you have no idea what you are trying to do you'll get no where.
They aren't supposed to know what Lorem Ipsum means. Further, it doesn't actually mean much of anything. It's nonsensical in the best of places and flat out wrong in the worst.
alias get="sudo apt-get install"
> get program1 program2
Their papers are non-existent, their sources jokes and the whole thing is based in religion. You need evidence for your claims, especially when they fly in the face of all of modern cosmology.
The C spec doesn't handle this case. The only correct answer is undefined.
Firstly, from Wikipedia
A sequence point defines any point in a computer program's execution at which it is guaranteed that all side effects of previous evaluations will have been performed, and no side effects from subsequent evaluations have yet been performed.
-----
Secondly from Annex C of the C99 Standard: Sequence Points
1. The following are sequence points described in 5.1.2.4
- The call to a function, after the arguments have been evaluated (6.5.2.2).
- The end of the first operand of the following operators: logical AND && (6.5.13); logical OR || (6.5.14); conditional ? (6.5.17).
- The end of a full declarator: declarators (6.7.5);
- The end of a full expression: an initializer (6.7.8); the expression in an expression statement (6.8.3); the controlling expression for a while or do statement (6.8.5); each of the expressions fro a for statement (6.8.5.3); the expression in a return statement (6.8.6.4).
- Immediately before a library function returns (7.1.4).
- After the actions associated with each formatted input/output function conversion specified (7.19.6, 7.24.2).
- Immediately before and immediately after each call to a comparison function and also between any call to a comparison function and any movement of the object passed as arguments to the call (7.20.5).
-----
Now onto this statement
i = ++i + ++i;
lacking in sequence points between the double assignments is undefined and has been undefined for the life of the language. It is as undefined as all of it's ugly brethren and should be left to die.
Why does this question keep popping up?