Sponsored Content
Full Discussion: Why I don't get any output?
Top Forums Programming Why I don't get any output? Post 302089130 by Sharmin on Sunday 17th of September 2006 12:34:43 PM
Old 09-17-2006
Thank you

Quote:
Originally Posted by matrixmadhan
't' - mode specifier
to open the file in text mode and not in binary mode

default is 't' when it is not specified with fopen

default value is set in _fmode in /usr/include/stdio.h

Thank you a lot. Just to let you know, as I am learning Ansi C now, I will be coming here with questions. I hope that it is okay. I know that there are lots of manuels, but I hope that I could get a website with manpage details and also with more practical coding examples.
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Don't allow to editing !!!

Hi All, Assume that there is file1 file,userA and userB have got read,write and execute permission for file1. when userA open file1, userB cant change(write,editing file etc...) content of file1. after userA exit of file1 , userB can change(write, editing file etc..). Shortly i want... (1 Reply)
Discussion started by: temhem
1 Replies

2. Programming

std::cout and gfortran print*, don't output to the screen

I am not sure where to post this other than here. I am trying to figure out why an app gives different output when compiled under Ubuntu 10.10 and CentOS 5.5. I am pretty sure that the issue is that the Cent version has gcc 4.1 installed, while Ubuntu has gcc 4.4. I am trying to print from some... (20 Replies)
Discussion started by: LMHmedchem
20 Replies

3. Shell Programming and Scripting

AIX -/usr/bin/expect shows output Don't know why.

Hi, I have been programming with the expect program for a while now and have create a series of menu driven checks for the operations team. One thing I have noticed is that I call a remote script and pass parameters and this is display on the screen....for example. Within the script ... (0 Replies)
Discussion started by: yakky
0 Replies

4. Shell Programming and Scripting

Find command don't output anything, but file is there

Please if You can help me debug why nothing is found by this command? # echo "Zeus Robot" >> /home/vps/190/test # cat /home/vps/190/test Zeus Robot # find /home/vps -type f -mtime 2 -size -1000k -exec grep -l "Zeus Robot" {} \; >> out # cat out # cat /home/vps/190/test Zeus Robot Why... (6 Replies)
Discussion started by: postcd
6 Replies

5. Shell Programming and Scripting

A shell script to run a script which don't get terminated and send a pattern from the output by mail

Hi Guys, I am very new to shell script and I need your help here to write a script. Actually, I have a script abc.sh which don't get terminated itself. So I need to design a script to run this script, save the output to a file, search for a given string in the output and if it exists send those... (11 Replies)
Discussion started by: Sambit Sahu
11 Replies
FOPEN(3)						   BSD Library Functions Manual 						  FOPEN(3)

NAME
fopen, fdopen, freopen, fmemopen -- stream open functions LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <stdio.h> FILE * fopen(const char * restrict path, const char * restrict mode); FILE * fdopen(int fildes, const char *mode); FILE * freopen(const char *path, const char *mode, FILE *stream); FILE * fmemopen(void *restrict *buf, size_t size, const char * restrict mode); DESCRIPTION
The fopen() function opens the file whose name is the string pointed to by path and associates a stream with it. The argument mode points to a string beginning with one of the following letters: ``r'' Open for reading. The stream is positioned at the beginning of the file. Fail if the file does not exist. ``w'' Open for writing. The stream is positioned at the beginning of the file. Create the file if it does not exist. ``a'' Open for writing. The stream is positioned at the end of the file. Subsequent writes to the file will always end up at the then current end of file, irrespective of any intervening fseek(3) or similar. Create the file if it does not exist. An optional ``+'' following ``r'', ``w'', or ``a'' opens the file for both reading and writing. An optional ``x'' following ``w'' or ``w+'' causes the fopen() call to fail if the file already exists. An optional ``e'' following the above causes the fopen() call to set the FD_CLOEXEC flag on the underlying file descriptor. The mode string can also include the letter ``b'' after either the ``+'' or the first letter. This is strictly for compatibility with ISO/IEC 9899:1990 (``ISO C90'') and has effect only for fmemopen() ; otherwise the ``b'' is ignored. Any created files will have mode ``S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP | S_IROTH | S_IWOTH'' (0666), as modified by the process' umask value (see umask(2)). Reads and writes may be intermixed on read/write streams in any order, and do not require an intermediate seek as in previous versions of stdio. This is not portable to other systems, however; ANSI C requires that a file positioning function intervene between output and input, unless an input operation encounters end-of-file. The fdopen() function associates a stream with the existing file descriptor, fildes. The mode of the stream must be compatible with the mode of the file descriptor. The ``x'' mode option is ignored. If the ``e'' mode option is present, the FD_CLOEXEC flag is set, otherwise it remains unchanged. When the stream is closed via fclose(3), fildes is closed also. The freopen() function opens the file whose name is the string pointed to by path and associates the stream pointed to by stream with it. The original stream (if it exists) is closed. The mode argument is used just as in the fopen() function. If the path argument is NULL, freopen() attempts to re-open the file associated with stream with a new mode. The new mode must be compatible with the mode that the stream was originally opened with: Streams open for reading can only be re-opened for reading, streams open for writ- ing can only be re-opened for writing, and streams open for reading and writing can be re-opened in any mode. The ``x'' mode option is not meaningful in this context. The primary use of the freopen() function is to change the file associated with a standard text stream (stderr, stdin, or stdout). The fmemopen() function associates the buffer given by the buf and size arguments with a stream. The buf argument is either a null pointer or point to a buffer that is at least size bytes long. If a null pointer is specified as the buf argument, fmemopen() allocates size bytes of memory. This buffer is automatically freed when the stream is closed. Buffers can be opened in text-mode (default) or binary-mode (if ``b'' is present in the second or third position of the mode argument). Buffers opened in text-mode make sure that writes are terminated with a NULL byte, if the last write hasn't filled up the whole buffer. Buffers opened in binary-mode never append a NULL byte. RETURN VALUES
Upon successful completion fopen(), fdopen() and freopen() return a FILE pointer. Otherwise, NULL is returned and the global variable errno is set to indicate the error. ERRORS
[EINVAL] The mode argument to fopen(), fdopen(), freopen(), or fmemopen() was invalid. The fopen(), fdopen(), freopen() and fmemopen() functions may also fail and set errno for any of the errors specified for the routine malloc(3). The fopen() function may also fail and set errno for any of the errors specified for the routine open(2). The fdopen() function may also fail and set errno for any of the errors specified for the routine fcntl(2). The freopen() function may also fail and set errno for any of the errors specified for the routines open(2), fclose(3) and fflush(3). The fmemopen() function may also fail and set errno if the size argument is 0. SEE ALSO
open(2), fclose(3), fileno(3), fseek(3), funopen(3) STANDARDS
The fopen() and freopen() functions conform to ISO/IEC 9899:1990 (``ISO C90''), with the exception of the ``x'' mode option which conforms to ISO/IEC 9899:2011 (``ISO C11''). The fdopen() function conforms to IEEE Std 1003.1-1988 (``POSIX.1''). The ``e'' mode option does not con- form to any standard but is also supported by glibc. The fmemopen() function conforms to IEEE Std 1003.1-2008 (``POSIX.1''). The ``b'' mode does not conform to any standard but is also supported by glibc. BSD
January 30, 2013 BSD
All times are GMT -4. The time now is 08:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy