MESSAGE
DATE | 2011-06-07 |
FROM | Ruben Safir
|
SUBJECT | Subject: [NYLXS - HANGOUT] (fwd) Re: C++ File Lokcing
|
From owner-hangout-outgoing-at-mrbrklyn.com Tue Jun 7 14:56:00 2011 Return-Path: X-Original-To: archive-at-mrbrklyn.com Delivered-To: archive-at-mrbrklyn.com Received: by www2.mrbrklyn.com (Postfix) id 70811100B40; Tue, 7 Jun 2011 14:56:00 -0400 (EDT) Delivered-To: hangout-outgoing-at-www2.mrbrklyn.com Received: by www2.mrbrklyn.com (Postfix, from userid 28) id 5877A100B42; Tue, 7 Jun 2011 14:56:00 -0400 (EDT) Delivered-To: hangout-at-nylxs.com Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by www2.mrbrklyn.com (Postfix) with ESMTP id BD52B100B37 for ; Tue, 7 Jun 2011 14:55:59 -0400 (EDT) Received: from panix2.panix.com (panix2.panix.com [166.84.1.2]) by mailbackend.panix.com (Postfix) with ESMTP id 9907D329E5 for ; Tue, 7 Jun 2011 14:56:24 -0400 (EDT) Received: by panix2.panix.com (Postfix, from userid 20529) id 8CF1033C69; Tue, 7 Jun 2011 14:56:24 -0400 (EDT) From: Ruben Safir To: hangout-at-nylxs.com Subject: [NYLXS - HANGOUT] (fwd) Re: C++ File Lokcing User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (NetBSD/5.1 (i386)) Message-Id: <20110607185624.8CF1033C69-at-panix2.panix.com> Date: Tue, 7 Jun 2011 14:56:24 -0400 (EDT) Sender: owner-hangout-at-mrbrklyn.com Precedence: bulk Reply-To: hangout-at-mrbrklyn.com
-- forwarded message -- Path: reader1.panix.com!panix!newsfeed-00.mathworks.com!newsfeed2.dallas1.level3.net!news.level3.com!postnews.google.com!p21g2000yqh.googlegroups.com!not-for-mail From: =?ISO-8859-1?Q?=D6=F6_Tiib?= Newsgroups: comp.lang.c++ Subject: Re: C++ File Lokcing Date: Tue, 7 Jun 2011 00:32:21 -0700 (PDT) Organization: http://groups.google.com Lines: 19 Message-ID: <8d5fbd3b-b73f-4c85-82fd-7b2566571c4a-at-p21g2000yqh.googlegroups.com> References: <9559f9Fh2bU1-at-mid.individual.net> NNTP-Posting-Host: 212.47.207.1 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1307431941 10452 127.0.0.1 (7 Jun 2011 07:32:21 GMT) X-Complaints-To: groups-abuse-at-google.com NNTP-Posting-Date: Tue, 7 Jun 2011 07:32:21 +0000 (UTC) Complaints-To: groups-abuse-at-google.com Injection-Info: p21g2000yqh.googlegroups.com; posting-host=212.47.207.1; posting-account=pysjKgkAAACLegAdYDFznkqjgx_7vlUK User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HUALESNKRC X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110420 Firefox/3.6.17 (.NET CLR 3.5.30729),gzip(gfe) Xref: panix comp.lang.c++:1086167
On Jun 7, 9:33=A0am, r...-at-zedat.fu-berlin.de (Stefan Ram) wrote: > "osmium" writes: > >"ruben safir" wrote: > >>Is there a C++ specific means of file locking? > >No. =A0File locking is provided by the operating system, not an ordinary= user > >program, which is what a C++ compiler produces. > > =A0 This must be the correct answer, because Linus Torvalds also > =A0 says that a C++ compiler cannot produce an operating system! > > =A0 (The real reason is - of coures - just that the C++ standard > =A0 library does not provide this feature, but this might change > =A0 in the future.)
Actually it is feature of file system. If it is some network file system then the code that your compiler produces are not implementing it but the server is. So implementation can do nothing there in order to achieve that the locks work or not. -- end of forwarded message --
|
|