public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: subrata@linux.vnet.ibm.com
Cc: LTP <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [rfc] extend test type field with tst_* functions
Date: Fri, 10 Jul 2009 10:06:12 -0400	[thread overview]
Message-ID: <200907101006.13796.vapier@gentoo.org> (raw)
In-Reply-To: <1247222795.6630.28.camel@subratamodak.linux.ibm.com>


[-- Attachment #1.1: Type: text/plain, Size: 1387 bytes --]

On Friday 10 July 2009 06:46:35 Subrata Modak wrote:
> On Thu, 2009-07-09 at 03:03 -0400, Mike Frysinger wrote:
> > the perceived problem: many many tests duplicate errno display and
> > they do so inconsistently.  many times the display is crappy and a lot
> > less helpful than it could & should be.  a test should merely have to say
> > "include the errno in the test output" so it can focus on its own details. 
> > much like the multitude of C library functions out there like perror() or
> > printf's %m.
> >
> > the proposed fix: extend the first argument to (1) take a define for
> > the test result and (2) also accept optional bit fields to further
> > manipulate the output.  the advantage here is we dont have to add a whole
> > lot of helper functions to complement the existing ones.  i.e. a new
> > tst_resmp() that would behave like tst_resm() but also append the errno
> > output.
>
> I like this idea. Very few comments:
>
>      1. The new patch does not show the implementation of tst_resmp(),

my point was that things like tst_resmp() are not the way to go but instead we 
should use the first argument as an optional bit field.  which is what my 
patch implements.

>      2. If there are changes on this regard, the corresponding
>         information should be updated in ltp/doc/man3/tst_res.3,

thanks, i wasnt aware of this
-mike

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 389 bytes --]

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2009-07-10 14:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09  7:03 [LTP] [rfc] extend test type field with tst_* functions Mike Frysinger
2009-07-10 10:46 ` Subrata Modak
2009-07-10 14:06   ` Mike Frysinger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200907101006.13796.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=subrata@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox