[tex]

sorry to do this, i just realized i had left part of a project out i have due tomorrow, and this thing is giving me fits. compiler error message doesnt help either. whats wrong with it? palindrome is a class, works fine for everything else. << is overloaded, works fine if i use a constant vs an interator. size_type throws an error too. all the variables and stuff are defined right, its something with i and the vector::iterator shindig in the use of at(i). thanks

               for (vector<palindrome>::iterator i = pVector.begin(); i < pVector.end(); i++) {
                        cout << pVector.at(i);
                }

[thadood]

Using a class?

Write a function within it to display the information rather than trying to cout it every time.

Example:

               for (vector<palindrome>::iterator i = pVector.begin(); i < pVector.end(); i++) { 
                        pVector.print(i); 
                }

[MSP]

I know jack shit about programming. In 7th grade I took a programming class at a local college and made a command decision - I'm not well suited to sitting and pounding out code all day. Hence I do hardware, networking, and project management.

[hans5849]

^We Ryans stick together.

[tex]

Originally Posted by thadood

Using a class?

Write a function within it to display the information rather than trying to cout it every time.

Example:

               for (vector<palindrome>::iterator i = pVector.begin(); i < pVector.end(); i++) { 
                        pVector.print(i); 
                }

yeah, i know how to do that, its my backup plan right now. im supposed to overload << tho. and theres a lot of other stuff i need at() for...

and i would imagine using << would be more proper than .print()

[thadood]

OOH, I get what you're doing now.

You can probably find how to do it using some code I wrote a while back: http://thadood.ath.cx/9.cpp
Let me know if it helps.

[tex]

lol thats not the problem. << IS overloaded properly. I can call it on specific elements and it works fine. the problem is with the iterators. if i replace .at(i) with .at(x) with x being any integer, it works fine. im screwing up with the iterator somehow...