delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Date: | Tue, 23 Jul 2002 21:37:57 +0200 |
From: | Pavel Tsekov <ptsekov AT gmx DOT net> |
Reply-To: | Pavel Tsekov <ptsekov AT gmx DOT net> |
X-Priority: | 3 (Normal) |
Message-ID: | <3632490659.20020723213757@gmx.net> |
To: | cygwin AT cygwin DOT com |
Subject: | How does mmap () relate to the binary / text mode flag of open () |
MIME-Version: | 1.0 |
Does the O_BINARY / O_TEXT flag change the behaviour of mmap () ? I red some mmap() manpages but none of them give a clear explanation :( It looks like mmap () on Cygwin doesn't care about it and just maps the file as it is on the disk. Can anyone confirm this ? I want to be sure, because I'm trying to find any places in MC where the open() call is missing the O_BINARY flag, where it would be better to have it. Thanks! :) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |