it sets endwait to be the current clock() value (presumably a timestamp) + a time to wait. It then goes into an empty loop until the clock() value becomes equal to endwait, at which point it exits...

Not all professionals refuse to use goto, or else the Linux kernel stopped being updated some while back. Goto sometimes is very useful; just because it's hard to use properly doesn't mean it should...

They'll probably tell you to never use goto as well, but that doesn't mean you should just listen to them. Find out why, and then do what is best; and yes, the popular opinion can be wrong...

I'd guess that it's due to how floating point values are stored imprecisely in memory, causing the weird results to come up on rare occasions.

I'd say to just keep writing code for now, when you get to the 4-year school they'll have plenty of resources. You might consider reading a couple books on algorithms or software development, and...

Yes, the use of & is optional in this case. Similarly, when calling the function *foo() and foo() will also be the same.

I don't see the word screen anywhere in his post...

Please don't use bold text when you post. It's meant to give emphasis to parts of a post, not the entire body; using it too much is poor netiquette. Also, please use and tags when posting code...

Different solution using stringstreams:

#include <sstream>
#include <string>
#include <iomanip>
using namespace std;
string foo(string city, string state)
{
stringstream ss;
string str;

If you're copying something, you need to allocate memory and then copy the appropriate values in. When dealing with strings, however, there's several library functions that'll help you along the...

Is it getting the day counts right though? Maybe if you just rearrange the values for the days it'll straighten out...

Nope, you've got the loop. Remember, j is going from 1 to the current month. So if you pass j, it'll look up the days in the 1st, 2nd, 3rd, ... nth month. :icon_wink:

I actually didn't test the leap year code. What's happening is you're adding the last year before it's over, skewing the result by that number of days. Ditto with the month. If you change the <=...

You add an extra year to the result, plus the number of days in the selected month. January 1800 comes out as 396, or 365+31.

That's about what WaltP suggested :icon_wink:

It depends on the function you're calling. It could be defined as void foo(T* someArray, int arraySize, int otherValue) or as void foo(T* someArray, int otherValue, int arraySize). The second one...

Your code really needs to be indented for readability purposes.

Anyways, global identifiers are typically considered bad style. They still work, but if you can come up with a solution without...

If you're using C++, you should probably be using the std::string type rather than C-style strings (char*).

And your line strlen(getWord) = numLetters; is backwards. Try flipping it around. ;)

How are you currently sorting them?

vijayan's solution should be correct. There's a few things different between his and yours, though, which are important. First, his parameter takes a const object. This allows you to have a const...

Just looking at the code for display, I'm surprised it doesn't crash.
void doubly::display()
{
node *temp;
temp=head;

while(temp!=NULL)
{
cout<<temp->data<<"\t";
...

You seem to be leaving out braces on your if statements. It was really easy to find with the code auto-indented. Here's a code excerpt:
switch (pkgType)
{
case 'A':
if...

Ok, a list of things.

First, as Lazaro pointed out, main should be type int, not void. A return 0; is then implied, but most people add it for clarity's sake.

Second, on a matter of style:...

Lazaro, please do everyone else a favor and don't quote hugely long threads for a one line reply. Or, if you're quoting to that your reply has context, please trim the quoted part as much as...

when [ left] got parsed out ;)

You're getting close, but you're still missing some things. For instance, if left > size, you don't return anything, which should be a compiler error. You did try to compile the code first, right? ...

Try running through your code on paper, as though you were the computer. You'll see that you're not using the left variable for anything, except the +1 before recursing. And you'll recurse...

Ancient Dragon's example will work for the first elemend of the 2D vector, and you'll probably have to nest it to go through all the rows of the 2D vector.

The easiest way would probably be to take the input as a string and compare each character to '1' and '0'. This will also help you tell if the user entered something like "101234" or "16oz."

1) Where is _strdate() defined? I'm not finding it...
2) Why are you using <iostream> and <stdio.h> (which should be <cstdio>)?

The #include "myheader.h" will essentially paste the contents of myheader.h into the top of whatever file it is #included into. So it'll be comiled just fine. In order to get the .cpp file...

When you run a program, the program starts with the main() function by definition. You need a main() somewhere in your project, and whatever file contains main() should be the one you compile to...

1) Post some code. Unfortunately, crystal balls are a bit out of the budget, so we can't see what's wrong.

2) A 9-year old book is... well, almost antiquated. Consider getting a new one, since...

This is because it reads the number, then the loop condition fails so it doesn't save the number. I'll let you figure out a way to fix that ;)

I made a few changes to the code, mostly small ones, but here's what I've got atm:
#include <fstream>
#include <iostream>
using namespace std;

const int MAXLEN = 10;
int buffer[MAXLEN];
int...

I'd first off recommend using return types instead of pointers. Handling pointers like that (imho) just makes the code messier than it needs to be. You could do it with references instead of...

The easiest way would be to put a big loop around the main part. You could have your menu contain an extra option to quit, and just keep doing calculations until they enter that option.

I don't see the reason for the 3rd loop for(int k = 0; k < 14; k += 2)
cout << endl;
You'll be outputting 7 newlines between rows of stars... is that what you meant to do?