Computer Programming - Seneca Polytechnic College•3y ago

where is the difference between these two file modes ?

where is the difference between

and

w+

w+

in c ? they both erase the file where is the point of using

w+

w+

in c language ?

.maverkOP•9/2/23, 11:23 PM

i have checked :

https://en.cppreference.com/w/c/io/fopen#File_access_flags

https://en.cppreference.com/w/c/io/fopen#File_access_flags

but it is still not clear to me where the point of using

w+

w+

Eakam•9/2/23, 11:37 PM

w is writing only, w+ is reading and writing

EEakam w is writing only, w+ is reading and writing

.maverkOP•9/2/23, 11:41 PM

how reading i don't understand ?

.maverkOP•9/2/23, 11:41 PM

when i use w+ the file will be erased

.maverkOP•9/2/23, 11:41 PM

even with only w

.maverkOP•9/2/23, 11:42 PM

where is the point here i am confused

Eakam•9/2/23, 11:42 PM

If you use w, you can only write to the file

Eakam•9/2/23, 11:42 PM

If you use w+, you can write to the file and read from the file

Eakam•9/2/23, 11:42 PM

Using the file stream pointer that is returned

.maverkOP•9/2/23, 11:42 PM

wait let address this little more better:

the file will be erased before even reading it

.maverkOP•9/2/23, 11:43 PM

can you show me an example ?

.maverkOP•9/2/23, 11:43 PM

i used both w and w+ the file will be erased i cannot even read

.maverkOP•9/2/23, 11:44 PM

#include <stdio.h>

int main(){
    FILE *file = fopen("test.txt", "w+");

    char buffer[992];


    fscanf(file, "%s", buffer);

    printf("%s", buffer);
    
}

#include <stdio.h>

int main(){
    FILE *file = fopen("test.txt", "w+");

    char buffer[992];


    fscanf(file, "%s", buffer);

    printf("%s", buffer);
    
}

result:

░dVJf☺

░dVJf☺

Eakam•9/2/23, 11:45 PM

Do this:

Open a while in
```
w
```
```
w
```
mode
Write to it
Try to read from it

Eakam•9/2/23, 11:45 PM

All using the same file stream pointer that is returned

.maverkOP•9/2/23, 11:45 PM

that doesn't work

Eakam•9/2/23, 11:46 PM

Then try to do it using

w+

w+

.maverkOP•9/2/23, 11:46 PM

.maverkOP•9/2/23, 11:46 PM

absolutely no output

CaramelCorn•9/2/23, 11:51 PM

you need to rewind the pointer

CaramelCorn•9/2/23, 11:51 PM

the pointer is still at the end of the write when you go to read, so it reads nothing

CaramelCorn•9/2/23, 11:53 PM

otherwise yeah between w+ and w there will be no difference if you don't move the pointer around

CCaramelCorn the pointer is still at the end of the write when you go to read, so it reads no...

.maverkOP•9/3/23, 12:05 AM

very nice it works as expected

Eakam•9/3/23, 12:09 AM

shouldn't allow you to read the file using the same file pointer

CaramelCorn•9/3/23, 12:10 AM

yep it won't

Eakam•9/3/23, 12:10 AM

I thought it would fail, but it seems to fail silently

Eakam•9/3/23, 12:10 AM

Like just returns -1

.maverkOP•9/3/23, 12:11 AM

wait a second

.maverkOP•9/3/23, 12:11 AM

it works as expected but there is one thing confusing me

CaramelCorn•9/3/23, 12:11 AM

yeah C doesn't have the same try->catch of newer langs so the return values are how you need to handle errors

CaramelCorn•9/3/23, 12:11 AM

if it crashed outright that would be messy

Eakam•9/3/23, 12:12 AM

I had forgotten, am too used to errors being thrown

EEakam I had forgotten, am too used to errors being thrown

CaramelCorn•9/3/23, 12:12 AM

hah same

.maverkOP•9/3/23, 12:12 AM

#include <stdio.h>

int main(){
    FILE *file = fopen("test.txt", "w");

    fprintf(file, "hello world");


    char buffer[443];
    fscanf(file, "%s", buffer);
    printf("%s", buffer);
}

#include <stdio.h>

int main(){
    FILE *file = fopen("test.txt", "w");

    fprintf(file, "hello world");


    char buffer[443];
    fscanf(file, "%s", buffer);
    printf("%s", buffer);
}

there are 2 operations going on here right ?

it opens the file twice

first opening a file and writing to it hello world

and then opening the file again for reading

.maverkOP•9/3/23, 12:12 AM

am i correct ?

CaramelCorn•9/3/23, 12:12 AM

nope

.maverkOP•9/3/23, 12:12 AM

what ??? why

CaramelCorn•9/3/23, 12:12 AM

the file stays opened, the pointer is a reference to the file

CaramelCorn•9/3/23, 12:12 AM

you need to manually close the file when you're done

CaramelCorn•9/3/23, 12:13 AM

the file is opened once in fopen

CaramelCorn•9/3/23, 12:13 AM

then you perform operations on the open file

.maverkOP•9/3/23, 12:13 AM

aaaah oky oky i understand

.maverkOP•9/3/23, 12:13 AM

but

.maverkOP•9/3/23, 12:13 AM

why hello world get erased ?

CaramelCorn•9/3/23, 12:14 AM

it doesn't get erased, the file pointer is pointing to the end of the last thing you wrote at the end of fprintf, C doesn't reset the file pointer after each operation, which is actually very helpful

CaramelCorn•9/3/23, 12:15 AM

you're just reading from this point: Hello World_

CaramelCorn•9/3/23, 12:15 AM

the _ is essentially where the pointer is when you then go to read from that point on

.maverkOP•9/3/23, 12:16 AM

yes i understand this very well

.maverkOP•9/3/23, 12:16 AM

i understand the cursor never goes back to the begining after any operation

.maverkOP•9/3/23, 12:17 AM

but what i don't understand is my hello world gets erased and i don't find it in the file when i look into it

where is the difference between these two file modes ?

Similar Threads

Similar Threads

Similar Threads