The current setup.exe source has quite a number of messages that announce
method calls. Most are being sent to setup.log and add bulk to that file
without providing diagnostic benefit. I have changed the log() calls to
send the messages to setup.log.full only.
I also shortened the messages in i
On Mon, Jan 28, 2002 at 08:00:36PM -0800, Michael A Chase wrote:
>A 2 io_stream_file.cc-patch [applica/octet-stre, quoted, 0.4K]
>A 3 archive.cc-patch [applica/octet-stre, quoted, 1.5K]
>A 4 compress.cc-patch [applica/octet-stre, quoted, 1.3K]
>A 5 co
===
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 29, 2002 3:14 PM
Subject: Re: [PATCH]Reduce messages in setup.log
> On Mon, Jan 28, 2002 at 08:00:36PM -0800, Michael A Chase wrote:
> >
- 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 PRO
===
- Original Message -
From: "Michael A Chase" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 29, 2002 3:41 PM
Subject: Re: [PATCH]Reduce messages in setup.log
> - Original Message -
> From: "Robert Collins" <[
- Original Message -
From: "Robert Collins" <[EMAIL PROTECTED]>
To: "Michael A Chase" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, January 28, 2002 20:55
Subject: Re: [PATCH]Reduce messages in setup.log
> I think you've m
===
- Original Message -
From: "Michael A Chase" <[EMAIL PROTECTED]>
> If the intention of those messages is to highlight methods that should
have
> been overridden but aren't, then setup.log is the right place.
Essentially, yes thats why they are there: incomplete methods. When I
revie
- 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 -
&g
Ok, I've looked at the patch.
Most of the methods are stubs that should warn when used. Some aren't,
and I'll try and merge those changes in by hand tonight. Don't bother
reissuing the patch - I'm about to cause everyone heartache by removing
much of the char * usage (I got sick of memleaks) for
- 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
===
- 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 visibl
> -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 look
===
- 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,
I think this covers the changes we discussed.
--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.
20
"Michael A Chase" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 29, 2002 6:35 PM
Subject: [PATCH]Reduce messages in setup.log (Revision 1)
> I think this covers the changes we discussed.
> --
> Mac :})
> ** I normally forward private questions to
15 matches
Mail list logo
