Is it a Windows handle, the one in windows.h? It's not an initializer, it's what int and char are: a type.
If it's a window handle, it's basically as specific as a pointer. A pointer used by windows to keep track of resources, varying from windows (window handles) to files (file handles).
I know that's the problem, and MSVC++ is sometimes quite archaic when it comes to "C code". You can try and use the vector class? MSVC++ apparently can't create 2D "standard" arrays dynamically.
... size_t is a standard type (~100% of the time it's an unsigned int)... that's weird. Could you copy and paste what your compiler is saying please? :)
Erm. I guess it can be compile in MSVC++. You can try to install MSVC++ Express and grab the platform SDK. Google is your friend. Can anybody else compile this code?
class Client
{
public:
string name;
Menu order;
int table_number;
string type;
double bill;
Client(void)
{
name="";
table_number=0;
type="";
bill=0.0;
}
};
This code lacks the virtual addClient table wants to use. Another note: is a table a client? If not, you shouldn't have inheritance, but perhaps composition.
I meant something like that. That's the "input" loop. Now, as you can see, this one is for subjects, but you should also create one for students for their variables. Same goes for output. If you don't know how, first write the code for reading in 1 student, then simply loop that. ;)
That sucks. But still, just loop the student array then, one time for input, one time for output. So no more extra variables representing members in class Student! ;)
You could create a function that accepts a reference to a student and outputs it's data?
void output_student(Student &stud){
//put the output code here
}
//....
int main(){
//loop each of your students here, one loop for reading in the data, the other one for outputting the data
}
Good luck with the assignment, don't forget about the STL! (It has a queue, of course you can't use that, but it has plenty of other useful containers and algorithms).
If you're standing in queue line at the grocery shop, does the LINE look like a tree, with intersections and such, or more like an array of (possibly annoyed) customers?
Wait, doesn't the fstream constructor *always* create something? Check if file.good() is true.
If the constructor is not successful in opening the file, the object is still created although no file is associated to the stream buffer and the stream's failbit is set (which can be checked with inherited member fail).
Oh and, don't open it twice. In the constructor OR with fstream.open(), not both.
One time (at band camp, xD) I was trying to open a file from an app I wrote in Code::Blocks on windows. So I put that file in project/bin/debug/, but code::blocks launched it in project/, so it couldn't find the file.
I've just created a single multithreaded program and it was (a dreaded task and) crashing constantly! So I ended up creating mutexes for every "group" of shared variables.
"Set pass/fail" I guess? Maybe the int is the subject indicator? Ugh, the variable names are horribly chosen. Just use that int as subject index and the char as.. P or F or something? Or grades? I dunno.
main() is just reading it, so no protection is necessary in this case.
That's wrong, almost 100% sure, couldn't make sure with google, but it's just 2 threads trying to access the same memory: doesn't matter if they read or write, both will lead to errors.
Agreed on not using Sleep(). It's a useless function: wait for events to happen, don't guess how long such and such is going to take, and put that time in Sleep().
Haha, no, that function of course needs to know what subject to set. Change it a bit, add a comment for your prof? The other functions do have such a parameter, so maybe he forgot?
A small addition: Sometimes set functions do return something, and most of the time that's whether they succeeded or not.
Anyway, seeing the format, it's like this:
<name>, list(<subject>, <number>, <character>)
Make a function that separates those variables, so you can output them individually. If you can do that, then you can set them individually with those set functions handed to you.
while(!inFile.eof())
{
// use getline to read entire line
getline(inFile, s);
cout << s << endl;
}
That's wrong code. eof gets set when it has read eof, so and in that case getline() won't do a thing, so you'll output the last output twice (possibly).
Correct code:
while(getline(inFile, s) // use getline to read entire line
{
cout << s << endl;
}
From there, again, use the set functions. You do know what your set functions do right? :D Some of the classes functions are empty though, either get rid of them or make them useful.
while(firstTry == true)
{
{
cout << "It Is Your First Try, We Will Create My Array First:\n";
updateArr(arr, size);
}
return firstTry = false; //Don't return here, hehe.
}
Should be something along the lines of..
if(firstTry == true)
{
cout << "It Is Your First Try, We Will Create My Array First:\n";
updateArr(arr, size);
firstTry = false;
}
Here's are tiny server/client applications. I don't guarrantee they work or are the holy grail of winsock programming, but if they still work then they are good references. ;-)
basicServer.c
/*BasicServer.c*/
#include <stdio.h>
#include <winsock.h>
#include <string.h>
#define BUFFERSIZE 511
int main(int argc, char **argv){
if (argc < 3){
printf("Usage: %s <message to send to client> <ip to listen to>\n", argv[0]);
return -1;
}
SOCKET sock, accepsock = SOCKET_ERROR;
WSADATA wsaData;
WORD wsaVersion = MAKEWORD(2,2);
int sizeOf, wsaerr;
struct sockaddr_in sockinfo, clientinfo;
sockinfo.sin_family = …
Nah I just meant to say that if you're sure that you'll only use it on your system, why not use those compiler specific functions? I think it's overkill to make basically everything you create cross platform, but if you're coding for your job then you should I guess... I'm a hobby coder. :)
Don't AVOID compiler specific functions, but be sure to find a cross-compiler way to do it as well, as in: find it, use it a couple of time, memorize it.
However, I think it's a definite plus if you also know compiler specific tweaks.
Not in any imaginable way if you ask me. Like I said, a pointer to an array of pointers (an array of "arrays") resembles a 2D array. Unless you want that, there's no use for a double pointer.
You can always create the double pointer at any time by &students, so if the need would arise it has a simple solution.
It is only a pointer, don't worry. It's a pointer that points to pointers.
The struct declaration indeed only reserves one pointer, not an array or anything.
However, I guess you want to have *students in your struct. An "array" of students, right? That makes a bit more sense than what you have now (which resembles a 2D array of students).
