Difference between seekg() and seekp()

What is the difference between seekg() and seekp(), and tellg() and tellp(), as they always appear to be returning the same values ?

The 'g' version move the get pointer, the 'p' versions move the put pointer... If memory serves, a particular implementation may use a single pointer for both. However if you are about to perform input you should definitely use seekg(), and seekp() in the other case.

seekg moves the file input pointer(position of reading frm file) while seekp moves file output pointer( position f writing to file).

Another question from juice answerable simply by reading the documentation.

istream::seekg - C++ Reference
ostream::seekp - C++ Reference

Originally Posted by rags_to_riches

Another question from juice answerable simply by reading the documentation.

No one really understood the question, or maybe I was unable to express myself, but I let it go, assuming(from what I observe from a couple of programs) that seekg and seekp can be used interchangeably.

And f** you, by the way.

And had you read the documentation you would have seen that seekg and seekp can not be used interchangeably....

Originally Posted by juice

No one really understood the question, or maybe I was unable to express myself, but I let it go, assuming(from what I observe from a couple of programs) that seekg and seekp can be used interchangeably.

And you did not understand that observing the side effects of something opaque is not the best way to understand it, the documentation is.

Seriously, what makes you think that they can be used interchangeably ?

Originally Posted by manasij7479

Seriously, what makes you think that they can be used interchangeably ?

This is what makes me think so...

Code:

#include"stdafx.h"
#include<iostream>
#include<fstream>

struct record
	{
		char  code[6];
		char name[20];
		int i;
	}r;

int main()
{
	std::fstream file("Temp.dat",std::ios::trunc|std::ios::in|std::ios::out|std::ios::binary);
	if(!file)
	{
		std::cout<<"unable to open file";
		exit(0);
	}

	std::cout<<"enter character code, name and an int\n";

	std::cin.getline(r.code,6);
	std::cin.getline(r.name,20);
	std::cin>>r.i;
        file.write((char *)&r,sizeof(r));

	std::cout<<"\n\n"<<file.tellg()<<'\n'<<file.tellp();
	
	file.seekg(3);
	std::cout<<"\n\n"<<file.tellg()<<'\n'<<file.tellp();

	file.seekp(5);
	std::cout<<"\n\n"<<file.tellg()<<'\n'<<file.tellp();

}

you really think I would like to post a question and wait for someone to answer when I could simply get an answer from some documentation?

Just because seekg and seekp may operate on the same pointer (the get and put pointer) they are not guaranteed to do so, which you would have realized had you read the two links posted to you....

Originally Posted by juice

This is what makes me think so...

By that same logic, writing outside of the bounds of an array must be okay because this works (for me):

Code:

#include <stdio.h>
int main(void) {
    int a[10];
    a[12] = 1;
    printf("%d\n", a[12]);
    return 0;
}

Ah, the familar sequence of steps of someone who does not really want to learn...

Asks Question instead of looking it up.
Be given correct answer anyway.
Ignores answer and decides their own wrong answer is correct.