logomancer | (no subject)

VT email got ransacked by the virus. It's been down for most of the week. I've just started to get non-virus emails again. Still not able to send anything till the queue clears. Stupid virus.
As the deadline for my first CS project draws near, I've hit a snag. The constructor I've made for the class won't compile -- some sort of pointer conversion error in the assignment operator for my linked list template. I had no clue why. Neither did Capra. Nor did the TAs. Can I panic now?
Had first chem lab yesterday. TA spoke a bit more English than the one I had last year, though his accent still makes him nigh-incomprehensible. Our first assignment: In addition to the prelab questions, copy all of the safety rules by hand and hand them in next week. Oy. On top of that, the one person I knew who thought she was in that lab section turned out to be in a different one, so now I'm back to begging perfect strangers to be their lab partners. *sigh*
Edit: That sysadmin job was already taken by the time I called. Apparently, the hiring person forgot to take his name off the database. Grr.

On that note, I head to DiffEq.

The constructor I've made for the class won't compile -- some sort of pointer conversion error in the assignment operator for my linked list template.

If you post the constructor & assignment operator code and compiler message I can try and make useful observations. Do you have a valid copy constructor? Sometimes that can cause similar errors.

Well, to be anal, sharing code for a project that's being graded would be an Honor Code violation...

But, let's have fun brainstorming what could cause this error! :-D

If it's not compiling due to a conversion error, I think it might be something like:

int x;
int *y;

And somewhere in the assignment operator, he missed a & or *, and he's doing y = x, instead of y = &x. Throwing a pointer into something declared as a non-pointer, without casting.

If it were that simple, it'd give him a line number. Since he mentioned that it's a template, I'm betting that it won't build because he's changed the header file somehow (which changes the size of the class) but not the implementation (and maybe his makefile is written such that changing only the header doesn't require a rebuild).

Well, to be anal, sharing code for a project that's being graded would be an Honor Code violation...

[sarcasm]
D'oh, I forgot that in school they prepare you for the "real world" in which no one shares information, offers help or publishes solutions so the wheel does not need to be reinvented. My bad. :P
[/sarcasm]

The difference between completely copying someone else's project vs. asking for help on an already written project that has a weird bug the teacher couldn't even figure out is a simple distinction for me but apparently not for Tech. That always angered me about the way they did things. I can honestly say that it has taught me to be more of a lone programmer than a team programmer.

We really need to push W3C to standardize a sarcasm tag... :-)

And you're right about the lone-programming thing. A couple of my ECE classes, fortunately, were team programming projects.

I haven't read the Honor Code, but my teachers always said it was okay to have someone else look at your code and tell you to look really close at line x or something - provided if it's another student they're not in the class or theirs is already done or something.

You know, the TA wil eventually stop asking you guys to turn in handwritten assignments once he realizes how bad his class's handwriting is....you can help this by making yours as incomprehensible as possible...

Actually, it was "copy the safety rules by hand" which is an important distinction. By copying them by hand, the hope is that you will at least have to READ THEM in order to copy them. It is a very subtle technique, I know, but still... :P

(no subject)

no subject

Re:

Re:

Re:

Re:

Re:

no subject

Re: