open vs. fopen

From: Lowell Kirsh (lkirsh_at_cs.ubc.ca)
Date: 02/28/05 

Date: Sun, 27 Feb 2005 23:05:36 -0800

I'm wondering when to use one function versus the other. I know open is
Unix and fopen is standard C, so I was wondering when one would want to
use open and thus lose portability. I'd imagine there must be some
advantages to open, I was just wondering what they are.

Lowell

Relevant Pages

  • Re: Linux Sys Calls - int 80h
    ... >> the C calling conventions ... > implementation detail, which will vary from system to system, as ... wrapping this in a convenient form to the original UNIX C calls... ... parties) as an "agreed" _standard_ between parties to follow... ...
    (alt.lang.asm)
  • Re: Rewriting and predictions
    ... not led to any improvements worth porting. ... then you claim others would rewrite it into standard Forth, ... I thought they could run some sort of Unix ... But I expect Win32Forth will become WForth (the name WinForth ...
    (comp.lang.forth)
  • Re: How did C++ beat the competition?
    ... >>The fact that most of the big players have abandoned it for Java. ... >>I KNOW the Unix creators did. ... J2EE programmers? ... standard; any more than J2EE belonged in the Java Standard. ...
    (comp.lang.cpp)
  • Re: Alpha remembrance day
    ... project, Alpha the soup to nuts "Industry Standard" 64 bit processor, ... switching to TCPIP when the later replaced OSI as the "internetworking" ... VMS didn't. ... UNIX Server/Workstation. ...
    (comp.os.vms)
  • Re: mkdir() wont do it for me
    ... C standard apart from the odd bug. ... just accepting mkdir() as a fact of a "C" programmer's ... but only because I fished it out of the trash of "Unix house" I ... there are networking groups. ...
    (comp.lang.c)