Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[3man75]

Thanks for your help. But I remember doing something similar that caused the loop to go bad when I tried to use x(woudn't identify or needed a pointer), how would I fix that?

Right now it seems like when I pass an array it either works or dosen't want to work (an thinking like that is never good in the tech. world). Also I know it's not 'junk' but it's what we called it in class when our programs accessed memory/files we didn't need.

[Reelya]

Thanks for your help. But I remember doing something similar that caused the loop to go bad when I tried to use x(woudn't identify or needed a pointer), how would I fix that?

Right now it seems like when I pass an array it either works or dosen't want to work (an thinking like that is never good in the tech. world). Also I know it's not 'junk' but it's what we called it in class when our programs accessed memory/files we didn't need.

Try adding more print statements to check the values of variables during the run. e.g. each loop print x and book[ x ] with this:

cout << " x = " << x << endl;
cout << "book[" << x << "] = " << book[ x ] << endl;

You should do this often if you're having problems with basic stuff. You should be adding print statements all over the place to check values before thinking of getting help. All professional programmers use print statements to see what variables are doing. Everyone does, because it's so effective at alerting you to errors.

Make sure that variables have the values that you expect. You can also add a print statement to detect errors which should not occur, e.g. each time you access an array you can check the value that's being used as the index:

if(x < 0 || x >= size)
{
    cout << "I dun passed the wrong value" << endl;
}

for example, a 10-element array goes from 0 to 9, so it would be an error to pass it an x value of <= -1 or >= 10.

[Skyrunner]

Heck, you could even argue that debuggers are simply infinitely more detailed and easy-to-use print statements...

[Orange Wizard]

Heck, you could even argue that debuggers are simply infinitely more detailed and easy-to-use print statements...

raise IdiotProgrammerError

...

[spoiler]This will be hidden if BBCode is enabled[/spoiler]

Code: [Select]

[spoiler]yeah but you could just put it in a [code] block which is easier[/spoiler]


[TheBiggerFish]

I think I borked Java.

I can't compile anything, Netbeans freezes up, and I can't even LAUNCH Eclipse for some probably-different reason.

Helllp meee.

[i2amroy]

I think I borked Java.

I can't compile anything, Netbeans freezes up, and I can't even LAUNCH Eclipse for some probably-different reason.

Helllp meee.

More info is needed. Are you getting any errors with netbeans? How about when you try to launch eclipse, what error are you getting there? Have you tried repointing netbeans/etc at your Java JDK? Have you checked to see if you can update to a later version of anything? Did you do anything specific before it froze? Have you tried restarting the computer? Are you running any other programs at the time that you were trying to open stuff?

[TheBiggerFish]

It was Malwarebytes Anti-Exploit for some reason.

I still don't know WHAT'S with Eclipse but I don't really care all that much.

[Cryxis, Prince of Doom]

Guess who gets to learn Robotc for their engineering class.

.....

It's me

[TheBiggerFish]

Huh.
Good luck, there.

You'll need it.

[Cryxis, Prince of Doom]

Thank you
I'll probably come here if I get confused

[Mephisto]

In what's possibly a futile choice of actions, I'm currently smashing F# and WPF together and hoping something good gets produced. Both are things I'd like to know more about, both personally and as far as the local job market is concerned.

[jaked122]

Ehh, I remember robotC, did it at a summer camp a few years back.


Don't remember any of it now, but it wasn't all that different from normal C. Just a little bit more restrictive.


Also coroutines. Those existed in it. They were alright.

[BlindKitty]

Try adding more print statements to check the values of variables during the run. e.g. each loop print x and book[ x ] with this: --snip--

You can also try using a language that actually gives you decent error messages and/or decent debugger with Watch option (which just keeps showing you the value of a variable without printing it all the time). (That is, of course, unless you need C/C++ for some other reason).

[Skyrunner]

Try adding more print statements to check the values of variables during the run. e.g. each loop print x and book[ x ] with this: --snip--

You can also try using a language that actually gives you decent error messages and/or decent debugger with Watch option (which just keeps showing you the value of a variable without printing it all the time). (That is, of course, unless you need C/C++ for some other reason).

C++ also happens to have the best debugger ever, aka Visual Studio!

[itisnotlogical]

I downloaded Visual Studio a few days ago. It's definitely better than Code::Blocks or Geany, and it's the only IDE I've seen with a GUI programming system that does not make me want to commit seppuku.

Well, I guess NetBeans had something similar, but my problems with NetBeans stem from Java and Swing. Particularly the "look and feel", which has no purpose except to make your programs eye-gougingly ugly unless you set it to use the system default look-and-feel.