- Original Message -
From: Robert Collins [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, January 28, 2002 20:25
Subject: Re: [PATCH]Reduce messages in setup.log
- Original Message -
From: Christopher Faylor [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January
- Original Message -
From: Robert Collins [EMAIL PROTECTED]
To: Michael A Chase [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, January 28, 2002 21:38
Subject: Re: [PATCH]Reduce messages in setup.log
- Original Message -
From: Michael A Chase [EMAIL PROTECTED
- Original Message -
From: Michael A Chase [EMAIL PROTECTED]
Essentially, yes thats why they are there: incomplete methods. When
I
review your patch I'll be looking at the function status.
There's no sense spending your time on the patch. I need to change it
drastically or
===
- Original Message -
From: Robert Collins [EMAIL PROTECTED]
1. If a method only returns a constant 0, the message should go to
setup.log.full to make it easier to tell where more work may be
needed.
Yes, LOG_TIMESTAMP (so that a casual inspection will have it visible).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Robert Collins
Sent: Tuesday, January 29, 2002 12:05 AM
To: Michael A Chase; [EMAIL PROTECTED]
Subject: Re: [PATCH]Reduce messages in setup.log
Ok, I've looked at the patch.
Most of the methods
===
- Original Message -
From: Gary R. Van Sickle [EMAIL PROTECTED]
for a
quick-and-dirtyish String class. Sigh, still no STL.
Rob, would you care to just graft more functionality onto my embryonic
cistring class? Or was that the plan?
I left it to the side for now, but yes I