|
|
Save it in other place and then move the "closed" file there   
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
All well and good, until you want to load one of those files! 
|
|
|
|
|
Here is another page with more then 20 Sample code links that do not work:
Shell SDK Samples (Windows)
-> you have to click (for example):Automatic Jump List Sample -> Downloading the Sample
-> You'll either end up with page not found or just the SDK Link
I don't think its funny and certainly not helpful
|
|
|
|
|
David O'Neil wrote: and find a function with 11 indentation levels!
One more reason to change to .Net. Where do these many circles of hell levels of indentation come from?
The lack of a proper exception implementation in old-style C/C++.
Just look:
HResult hr;
hr = ;
if (SUCCEEDED(hr))
{
hr = ;
And in case of error, ... it does nothing. Just the user wonders why it does not work, the service hotline people will be delighted by not having any indication of why things do not work.
C# would prefer to throw an exception in case of failure, and no need to handle each place of potential failure separately. Of course, catching the exception and - more importantly - handling it usefully, are still things the developer has to take care of (but it's rather easy).
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
|
|
|
|
|
something = Anotherthing - ((condition == 0) ? (assignment_here = object->method()) : someothervalue);
So we have: an arithmetic expression of which one operand is actually the result of the ternary operator, which in turn assigns a value to another unrelated variable and calls a function... but only if the condition of the ternary operator is true.
This thing is pure evil and is sapping away at my sanityk lanòsak òjslshf pAHRW R'LYEH.
GCS d-- s-/++ a- C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
It needs some shift lefts and shift rights thrown in for good measure. It's not obscure enough.
This space for rent
|
|
|
|
|
I would only make a couple of changes
something = Anotherthing - (condition ? someothervalue : (assignment_here = object->method()));
I never liked
condition == 0 I like
!condition much better.
|
|
|
|
|
Currently I am so fortunate that my programming is in a language where (numeric != bool) 
In my last plain C project, I happened to set up a "#define ever ;;" so that I could write "for (ever) {..." to make an infinite loop, which is not uncommon in embedded code. (In the CHILL language, made for programming phone switches, "DO FOR EVER ..." is defined in the basic language.) One of the other team members reacted quite fiercly to this, searching through the entire code base for "for (ever)", adding a nasty commit message about "someone" who were trying to make funny jokes in the code, and he changed it to the proper "while (1)". The header project files did define "true" and "false" constants, but he woudn't accept even "while (true)": There is one proper way to make an infinte loop in C, and that is "while (1)".
I was seriously considering to change it to "while (2)", with a commit message that 2 makes it twice as clear that the loop should run for (ever), but I decided not to. My relationship to that guy was bad enough without further provocations.
So, provided "condition" is a bool variable, or an numeric variable that stores nothing but the value of bool expressions, I certainly agree that "!condition" is the proper way. But if "condition" is a numeric value treated as such (e.g. a counter from n down to 0), treating it as a bool for flow control is bad. Then "condition == 0" is far better.
Same with pointers. I detest "if (!nextpointer) { /*leave loop*/" - that should be "if (nextpointer == null)" (or "nil" or "empty" or whatever your favorite language calls is).
Which makes me think of that really nice construction I have encountered in a single language: "FOR currentpointer IN listhead:nextpointer DO..." - "nexpointer" being the name of a pointer member in the class "listhead" (and "currentpointer") points to.
|
|
|
|
|
I only use a ternary operator when it is very clear what is going on. This exceeds my limits on clarity with the assignment in there.
|
|
|
|
|
Anotherthing is inconsistently cased, pure evil indeed!
|
|
|
|
|
That is indeed the real crime here.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
So....
We should both be very grateful that you don't do peer review for me. I would have tucked in an anonymous function just to piss you off.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
den2k88 wrote: but only if the condition of the ternary operator is true.
There's certain elegance to that which I can't help but admire.
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
At least it's all on one line.
|
|
|
|
|
There's a lack of prefix and postfix operators, don't you see that? The code should be corrected to:
something = Anotherthing - ((++condition == 0) ? (assignment_here = object->method()) : --someothervalue);
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
|
|
|
|
|
There are in other bits of code. This is as of now the single line of code with the most horrors I ever seen.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
|
Well, object->method() could be a recursive call so it's not that bad.
|
|
|
|
|
Kodi is a home theater video/music player. It's available for Windows, Mac, and Linux. It uses a sqllite database to store video file info. I was cruising their wiki, and at the top of the wiki is this statement:
Warning: The databases are critical components of Kodi. We strongly urge that you do not interfere with
them, unless you have knowledge and experience with database designs.
Imediately following this statement are the schemas for the various tables, which includes the following column names:
c00
c01
c02
...
c23
Maybe they should heed their own warning.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Well duh! c for 'collumn'. What else you gonna name them? 
|
|
|
|
|
All rows start with an "r"?
I.e. Hungurian notation as suggested by Simonyi done right according to Joel Spolsky?
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
|
|
|
|
|
So the intersection of a row and a column in a table that uses this naming convention is an "rc", or 'arse"?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
David O'Neil wrote: collumn
Collumn! Collumn! The Master knowsss where the preciousss design is.
GCS d-- s-/++ a- C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Software Zen: delete this;
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
