Hi Robert,
>> "Once virtual, always virtual", i.e., it isn't necessary to add
>"virtual" to
>> any overridden virtual functions, and in fact it's not possible to
>> "unvirtualize" once virtualized. I do try to maintain them as a
>stylistic
>> convention, but even I fall short sometimes ;-). Tha
I'm sorry Jorg, but I don't have the standard to reference. Do you know
of an on-line copy? (Googling for "c++ standard 10.3.2" gave me lots of
useless hits :})
I got my info from the C++ FAQS second edition (Cline Lomow & Girou),
FAQ 33.09.
Rob
===
- Original Message -
From: "Schaible,
My first foray into signals...
ChangeLog:
2002-01-08 Robert Collins [EMAIL PROTECTED]
* sigproc.cc (getsem): Rearrange code to be more readable, and to
always output an error if accessing or creating the semaphore fails.
getsem.patch
Description: Binary data
did not recognize, that Robert mailed twice - one private, one to the list
-Original Message-
From: Schaible, Jörg
Sent: Monday, January 07, 2002 3:24 PM
To: 'Robert Collins'
Subject: RE: [PATCH] Update 2 - Setup.exe property sheet patch
Hi Robert,
unfortunately is this document not f
On Tue, Jan 08, 2002 at 01:03:45AM +1100, Robert Collins wrote:
>My first foray into signals...
>
>ChangeLog:
>
>2002-01-08 Robert Collins [EMAIL PROTECTED]
>
>* sigproc.cc (getsem): Rearrange code to be more readable, and to
>always output an error if accessing or creating the semaphore
On Mon, Jan 07, 2002 at 11:41:40AM -0500, Christopher Faylor wrote:
>On Tue, Jan 08, 2002 at 01:03:45AM +1100, Robert Collins wrote:
>>My first foray into signals...
>>
>>ChangeLog:
>>
>>2002-01-08 Robert Collins [EMAIL PROTECTED]
>>
>>* sigproc.cc (getsem): Rearrange code to be more readabl
===
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
> If I'm reading the patch correctly, it changes the behavior of cygwin
so
> that cygwin will output an error in the case of a failing
OpenSemaphore.
> That's not right. The current behavior is correct. The only ti
On Tue, Jan 08, 2002 at 09:11:00AM +1100, Robert Collins wrote:
>
>===
>- Original Message -
>From: "Christopher Faylor" <[EMAIL PROTECTED]>
>
>> If I'm reading the patch correctly, it changes the behavior of cygwin
>so
>> that cygwin will output an error in the case of a failing
>OpenSema
===
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
> system_printf goes to the screen.
Doh. Do I need a braile screen or what?
Rob
This should make moving around a little easier.
--
Gary R. Van Sickle
Brewer. Patriot.
setup.diff
Description: Binary data
ChangeLog.setup.grvs
Description: Binary data
Glad to see it was trivial. I'm slowly grokking your code :].
Would you like to write a few words - a 'how pages work.txt' file?
I'll check this in shortly.
===
- Original Message -
From: "Gary R. Van Sickle" <[EMAIL PROTECTED]>
To: "Cygwin-Patches" <[EMAIL PROTECTED]>
Sent: Tuesday, J
11 matches
Mail list logo