@IsmaelMiguel timsort beats it for patterns but is not as good for shuffled input. On average, pdqsort indeed seems to be the best truly general purpose one.
@Mast Too chatty it is. I don't see offensiveness. I've had a comment somewhat like that before. I laughed my a$$ off and edited the code to match the comment. easy +10
UPDATE table1 as outr SET country_fid =
(SELECT contact.country_fid FROM table1 as person
JOIN table2 as contact ON person.table2_fid = contact.pid
WHERE person.pid = outr.pid)
WHERE country_fid IS NULL;
I've been working on a VBA macro that parses HTML into a an Excel sheet. The code is functional, but extremely slow (it takes roughly 20 seconds to fill 270 lines from columns B to M). Due to the code being functional, I suspect it would be best submitted to Code Review.
But. The code I have is ...
@Vogel612 I have an array with data like this: {"id":"3750-011","location_name":"Alcafaz - AGADÃO","postal_designation":"AGADÃO","district_name":"Aveiro","county_name":"Águeda"}
I need to write data into 2 or 3 tables
And each don't have a well-defined structure yet
I have to write the name of the city on one table, with a language identifier
Then I have to write the "id" into another table
And then I have to insert more data into another table with the translations and a bunch of stuff
All those depend on the primary key of the city created
@nhgrif I know you pingged Mat, but I think you can't. You will need to have a compiler capable of compiling to windows. As far as I know, compilers compile to the operating system they are in.
But what's the big deal about writing a Windows app in Objective-C if you have to be on a Windows machine to do it?
There are ZERO developers who write Objective-C who sit around and see "Gee, Objective-C is great! If only I could use this on a Windows machine to write Windows app."
No.
People write Objective-C because before Swift, that was the best way to write native OS X and iOS apps.
If I still need Windows to at least give a really cursory alpha test to a Windows application, then nothing great has been accomplish by creating Objective-C.NET
Nothing that Microsoft couldn't have done 30 years ago when Objective-C was a new language.
They've waited till after Swift as all the people who know Objective-C are converting over to Swift.
I'm working on a pretty big Objective-C iOS application for a client. Microsoft is also paying for us to build a Windows/Windows Phone application for the client.
And when I say paying for... I don't mean they're paying for us to convert the Objective-C project.
> You think all the iOS developers will now buy a PC to port their apps to the windows world? NOT And buy a windows license? NOT If you want to attract people from the iOS/Apple world, think about OS X Dev tools.
Pretty much that.
This is great news for an extraordinarily small segment of the developer world.
1. Very small companies that couldn't support a full Windows team but want to put out a Windows port of their Objective-C iOS app. 2. Successful indie devs that want to increase their profits by what they see as a zero-cost way to release to Windows.
This may also be relevant to this conversation:
Symbolic: iOS unit sales are now matching Windows PCs. http://t.co/4qsNg3ntYW
I am implementing a Stack using an array. I have written the below code and it works fine
#include<stdio.h>
#include<stdlib.h>
int isFull(int top, const int unsigned size)
{
if(top==size-1)
return 1;
else
return 0;
}
int isEmpty(int top)
{
...
I VTC'd, based on: "Does the method to implement a Stack as given in the above link is more efficient than my code and What is the better way to implement Stack my method or the one given on that website ?"
That screams for an explanation (understanding) of their code.
Inspired by this question: Custom Close Reason Post-Mortem.
Can we alter
Questions must involve real code that you own or maintain. Questions seeking an explanation of someone else's code are off-topic. Pseudocode, hypothetical code, or stub code should be replaced by a concrete example.
T...
"Questions must involve real code that you own or maintain. Pseudocode, hypothetical code, or stub code should be replaced by a concrete example. Questions seeking an explanation of someone else's code are also off-topic." That question asks, "Does the method to implement a Stack as given in the above link is more efficient than my code and What is the better way to implement Stack my method or the one given on that website ?"
I had to write a generic wrapper that enables me to pass variable number of arguments for execution of some methods and repeat it up to a few times when it fails because of network connection problems.
What I came up is this class and a helper method. Well I can't say it's perfect - it is suffi...
Unless we are only qualifying the last sentence of that close reason if the question only involves code that the author owns, than that close reason is completely valid here.
@JeroenVannevel For the sake of this question, the answers are evidence that it's a really bad question. The asker doesn't want a review. And the answers he's getting aren't reviews.
@EBrown You're in disagreement with the community at large. Not just me.
In fact, myself (and other long standing community members) once thought like you did about this close reason, but there are things you need to understand.
You can VTC or not (for whatever reason you like), I'm using mine. And I'm not going to sit here and waste time I can be doing something else for voting to close the question for the fact that, as far as the text stands, it is off-topic by at least one sentence in that VTC. If that sentence in that VTC is not intended to apply literally, then it should be reworded to be more explicit.
So it's important that you catch up with the rest the community up to date
At the end of the day, the point is to not confuse the person whose question got closed
And the experience we've had with that close reason is that when people get their question closed with it, they come back and say "But that's not hypothetical code, and I did write it myself!"
I'm not saying that it's an invalid idea, but that posting that specific example with a comparison of "my code" (from the author's perspective) and "someone else's code" would still warrant a VTC, for the reason I did.
Just stop, for a second. Act like I've been a major part of the meta and this community for almost 2 years, and you're relatively new. Give me that credit, and let me explain this to you
These close reasons are supposed to be pretty specific and used for one specific common problem (per close reason). We're limited to three. But they're not supposed to be a catch-all for as many reasons as we can fit in the character limit. If a close reason appears to apply to multiple problems, then there is a problem with the wording. The close reason we're talking about is for when the asker has posted code that is hypothetical code, pseudo code, stub code, or code for which he is...
...not the owner or maintainer. And that is it. The extra sentences (talking about explaining) are there to help clarify why it's a problem and provide extra links to the meta discussions about that specific problem.
The code in the question isn't hypothetical code, isn't pseudo code, isn't stub code, and to the best of our knowledge, the asker is the owner/maintainer of it. Thereby, this close reason does not apply.
And if it were closed for this reason and the asker asked on the meta why it was closed, our only explanation would be that the wrong close reason was used, and then we'd explain the actual problem with the question.
Then perhaps there should be a couple qualifiers linking the two ideas together. Because as I see it, one reason can (and should) apply to several problems. This is obviously an edge case, because there is equal justification each way.
Instead of doing that and waiting for it to get to the meta, you should use a custom close reason so the user more quickly gets a clearer explanation of their problem.
I have multiple times in the past asked that we should have a custom close reason purely for people seeking an explanation of code.
We only have 3 close reasons though. And the three we're using happen more frequently than people outright asking for explanations (and none of the others apply)
If we got a 4th close reason, asking for explanation might be that 4th reason
Note: For chat-like discussions of this subject, let's use this Discuss Close Reasons chat room
Code Review currently has three standard off-topic reasons:
Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. A...
I'm not saying a custom reason would not be more appropriate/more qualified, what I am saying, is that my using of that VTC is not "wrong." It may not be the "most qualified", but the VTC can still be interpreted (pretty plainly/easily) to apply to this question.
The code in the question isn't hypothetical code, isn't pseudo code, isn't stub code, and to the best of our knowledge, the asker is the owner/maintainer of it. Thereby, this close reason does not apply.
There may be code in the question that is not the askers, but for a full understanding of the question, one must also read and understand the linked-code, which is not the askers.
Even if it were his own code he wanted comparison with, I leave my close vote exactly as is because that is the overriding problem: he doesn't want a review
Going through a book, I encountered the following assignment:
Write an application that asks for the user’s first, middle, and last names and
replies with the user’s initials.
Are there any flaws you notice immediately? Is there any way this code can be improved? I'm not really interested...
I think that a comparative review should be 2 questions, and then the user can take the answers from both and do the comparing on their own. then they can decide what is going to work best for their situation.
@EBrown You should always start with the biggest problem a question has. And this is especially true for questions that already have answers. When we start with smaller problems, the asker tends to have trouble seeing the forest through the trees.
@nhgrif If that's the case, then the close dialogue should specify that. I pick the first reason I find that is well-satisfied by the question. If there is not one, I add a custom reason.
I think that a comparative review should be 2 questions, and then the user can take the answers from both and do the comparing on their own. then they can decide what is going to work best for their situation.
This came from chat.
There is a lot of discussion in Chat about comparative-revie...
I also posted an answer. I don't post on meta very often, I do try to keep track of stuff on meta though, hopefully @Jamal will edit my Q&A a little bit and make it pretty
I think that a comparative review should be 2 questions, and then the user can take the answers from both and do the comparing on their own. then they can decide what is going to work best for their situation.
This came from chat.
There is a lot of discussion in Chat about comparative-revie...
@jacwah @IsmaelMiguel Not only that, but you must have an interpreter that works on every environment you plan to run on. I.e., if there is no interpreter for Windows, then you're SoL.
@IsmaelMiguel In my experience it's usually spoken as the abbreviation, as it's a commonly accepted acronym in English. ("Man, my car is S-O-L after that accident Wednesday.")
If "better solutions" demoralize you, don't ever go to Boost's website. Anyway. I notice that you tagged this c++11, which sets you well ahead of most beginners already. If you want some competent advice on a working piece of your code, you can post a question on Code Review. StackOverflow here is for code that doesn't work, so people can help you spot the problem. Beware to make it a good question though, have a look around to know what to do and not to do. Welcome to the Stack ! — Quentin23 secs ago
I am implementing a Stack using an array. I have written the below code and it works fine
#include<stdio.h>
#include<stdlib.h>
int isFull(int top, const int unsigned size)
{
if(top==size-1)
return 1;
else
return 0;
}
int isEmpty(int top)
{
...
Inspired by this question: Custom Close Reason Post-Mortem.
Can we alter
Questions must involve real code that you own or maintain. Questions seeking an explanation of someone else's code are off-topic. Pseudocode, hypothetical code, or stub code should be replaced by a concrete example.
T...
I had to write a generic wrapper that enables me to pass variable number of arguments for execution of some methods and repeat it up to a few times when it fails because of network connection problems.
What I came up is this class and a helper method. Well I can't say it's perfect - it is suffi...
Note: For chat-like discussions of this subject, let's use this Discuss Close Reasons chat room
Code Review currently has three standard off-topic reasons:
Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. A...
if (word1Length !== word2Length) { return false; }
for (var i = 0; i < word1Length; i++) {
}
Affordable Dental Implants in Parramatta
Going through a book, I encountered the following assignment:
Write an application that asks for the user’s first, middle, and last names and
replies with the user’s initials.
Are there any flaws you notice immediately? Is there any way this code can be improved? I'm not really interested...
I think that a comparative review should be 2 questions, and then the user can take the answers from both and do the comparing on their own. then they can decide what is going to work best for their situation.
This came from chat.
There is a lot of discussion in Chat about comparative-revie...
