WaltP

4th option: Make a zeroed array of 5,00,000 integers. For every integer read, use it as an index into the array and increment that entry. When done, the value that's 1 was read once. But **shanki himanshu**'s solution seems to be the most efficient. It's a really slick solution.

Read it.

>First, is there any way that I can do this more efficiently, ... First thing is compile the program and fix the errors. There's generally no reason to enhance a program that won't compile in the first place or runs improperly. > ...and second, what is the easiest way to …

You should avoid `goto` completely. After 30 years in C, I've never needed one. Restructure your program to use one of the 3 loop structures. As for *why* it executes twice, when you type your answer, how many keys do you actually press? What do you think is now happening? …

Does it work? If so, probably. Test it with a lot more data. If not, no. Please don't use `getch()` at the end of programs. It's non-standard and when you get to a *real* compiler, you'll have problems. What to replace it with? Well, what does `getch()` do? What standard …

Not bad... Here are some possible things you could consider for improvements: ------------------ Because *coinval* is a `#define` it should be in all caps. And while you're at it, define the heavy and light values too: #define COINVAL 2 #define COINHEAVY 3 #define COINLIGHT 1 Also, make the values for …

Of course. Parse the string into it's components (a 17 and a 30). Fill a time *structure* (defined in `time.h`) with the appropriate values. Call the appropriate time function in to convert the structure into **time_t**.

[QUOTE=sgw;544665]Thanks for the link. I just read your post there. So it looks like unless you use cin.ignore(), you would always need to type cin.get() twice. There's no cleaner way...[/QUOTE] Yes, there are cleaner ways. First is to not use [ICODE]cin[/ICODE]. Read a full line into a [I]char*[/I] or a …

I don't like the explanation you've received for "undefined behavior". What this means is the C Standard has not defined the operation, and what it is supposed to do. Therefore, any given compiler can do what they want. For[INLINECODE]fflush(stdin)[/INLINECODE], the compiler designers can write the compiler to: 1) do nothing …

And why is the kettle calling the pot black?

[QUOTE=Ancient Dragon;1098772]and the fastest modem available was 300 baud.[/QUOTE] or the teletype hardwired to the computer that takes up an entire room runs at a blazing 110 baud! [QUOTE=almostbob;1099892]I still have 3 paper tapes ascii art (if you squint a bit) ladies scantily attired just need somebody with an ibm …

Also, if you don't understand `stringstream` there are two avenues: 1) Don't use `stringstream` 2) Learn how `stringstream` works by writing a bunch of test programs that will teach you various aspects of it. Also your formatting needs a lot of work. You code is almot impossible to read and …

**[boilerplate_help_info]** Posting requests for help must be well thought out if you want help quickly and correctly. Your post did not meet the criteria for quality help. You may get some posts, but are they going to be useful? Check your post with these checkpoints - what is it *you* …

None that I know of, since C is not controlled by a single company like Java.

**[boilerplate_help_info]** Posting requests for help must be well thought out if you want help quickly and correctly. Your post did not meet the criteria for quality help. You may get some posts, but are they going to be useful? Check your post with these checkpoints - what is it *you* …

Ok, done. Now what?

> I havent tested the above code? Why not? How do you know what needs to change if you haven't bothered to try it? > Any correction? Too much to go into. Based on what you've posted you need to go way back to the basics. Like 1) the infamous …

> Another approach is to use the strtod(const char* nptr, char** endptr) function. > > You could use boost::lexical_cast to try and convert the string to a number I'm curious how these two approches actually *test* for valid values. Won't they both simply convert whatever it can to binary and …

> I am able to successfuully build my DOS aps under this compiler on WinXp, I wouldn't try to run it though. Why not? I've successfully built and run Turbo 1.0 graphics code in WinXP.

> Calling main() from within main() would be an example of recursion, and not looping. > ------ > its not loop. Its just "calling the main function" we don't consider it a loop. Actually, it's called a *recursive loop*, so yes, recursion **is** a loop. > A loop is a …

I like option 1. I don't need to automatically see comments, but when I want to see them it would be nice to have "show comments" only when there are comments.

And why is the related article imbedded in the first post? That just seems wrong since it wasn't posted by the OP. At least put it *after* the post.

Copy the text boxes into an array. Sort. Write the array back into the Text boxes.

And yet another "*not totally working*" post, as if we're supposed to know what that means. When asking for help, give us information. Don't make us guess what "*not working*" means.

Google can

> I would like to ask only a good algorithm for this problem. Then explain what you don't understand and **IN DETAIL** explain what you need the program to do.

How 'bout `Employee::Calculate(parameters)` ????

Why would you want the data explosed to the outside? Use a *get* method to expose the location. If you want to see the value of location 0,0, return the location with `val = level1.getMapLoc(0,0);`

> I'm not sure what the situation is in India where the original poster is from... But you can bet the boxes are programmed using Turbo C....

> total=total+(pow(n,i)\fact(i)); Take a *closer* look at this equation. Specifically the math symbols.

**Consistent** formatting is the key. [See this](http://www.gidnetwork.com/b-38.html) and refine your indentation. I believe this will fix your problem when you indent properly.

I would recommend you stay away from all practices/function/headers that are compiler/OS dependent. Unlearn `conio.h` since only 1% of the compilers ever made have it defined. And of those compilers, each `conio.h` is different.

#Run program and see

Then don't use it. Write your own version and you'll know how it works.

>Does anyone know what I am doing wrong? Mainly, if it's supposed to be a string, where's the space for the \0 that terminates a string?

Why 0-5, 6-9, 12-13? Why not 0-3, 4-8, 9-13? Or 0-1, 2-3, 4-5, 6-8, 9-13? > My attempt is here, but there is a problem with this: So what's the problem with *this*?

Unfortunately, we can't see your screen to see what the errors and warnings are.

> Also use a vector as **the array isn't contingously aligned**. It isn't? Please explain... And why do you guys always suggest vectors when they are obviously beyond the scope of their knowledge? What do you think would happen when they turn in their homework with vectors which hasn't been …

> what will print Nothing. There are no output statements. Assuming that's not the correct answer, sit down with pen and paper and figure it out. Write down the variables and their contents Write down the pointers and where they point Now follow the code statement by statement

plz try to understand please read deceptikons msg he tells you correct stuff and dont cry be a big boy and stop begging you sound like a whiney 3-year-old and you must be 13 years old to post here

Can't tell from what you posted whether **BufferData** points to a valid buffer or random memory. That's could be why you get different values.

Can you be less vague? Not one win condition works? Some work but not others? All but one works? And where should we start looking? This is like looking for a needle (vague idea what we're looking for) in a haystack (371 uncommented lines of code)

> **My boss** has seen this & **has disabled** the dowloading of videos from my computer. Doesn't that sentence tell you anything?

> For those interested here it is. Now how do you delete posts? If the post was deleted, why would we be interested? ;o)

Yes, it's precision, and double is simply more accurate. That does not equate to bigger. For example: `double` may be 56.42735816, float may be 56.42736 -- `float` is bigger.

Posting Questions Lesson number 1: "[I]This is wrong[/I]" doesn't cut it. [I]What[/I] is wrong? Always provide details. Only you know what happened, so you need to tell us a) what happened b) what should have happened. Remember, we cannot see your screen. You need to post all information that is …

Depends on how **blocks** is ultimately defined. Depends on what **length(blocks)** returns. Depends on what **size(blocks)** returns. Depends on what **sum(size(blocks))** returns. There are a lot of possibilities on each of the above. Unless there's a *Matlab* user that can answer these questions, we'd be just guessing.

Most likely mis-matched braces. If you would [indent in a consisent manner ](http://www.gidnetwork.com/b-38.html), that type of error would never show up.

Then, as **deceptikon** says, it's not supported by that compiler. Write your own.

*[pedantic]* Since the hottest recorded temperature is a mere 3.6 billion degrees, why would you care if the program worked for 10 Quattuordecillion? *[/pedantic]* Actually, the problem is the limits of binary math. 45 digits is too many for computers handle. The only way to cleanly deal with numeric abnormalities …