mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cliff White <cliffw@osdl.org>
To: Ian Wienand <ianw@gelato.unsw.edu.au>
Cc: Con Kolivas <conman@kolivas.net>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Aggelos Economopoulos <aoiko@cc.ece.ntua.gr>,
	cliffw@osdl.org
Subject: Re: [ANNOUNCE] contest benchmark v0.60
Date: Wed, 15 Jan 2003 11:28:56 -0800	[thread overview]
Message-ID: <200301151928.h0FJSuW17921@mail.osdl.org> (raw)
In-Reply-To: Message from Ian Wienand <ianw@gelato.unsw.edu.au>  of "Wed, 15 Jan 2003 16:24:00 +1100." <20030115052400.GJ21742@cse.unsw.edu.au>

> On Wed, Jan 15, 2003 at 03:39:34PM +1100, Con Kolivas wrote:
> > more I tried to add to it. Also there were subtle things happening in the 
> > BASH version that made for much more variation in results than this version. 
> 
> I agree, it had begun to outgrow it's bash roots (e.g. i think it was
> the ratio section with variables named a b c d e which drove me nuts
> when I couldn't figure out which one was giving me a zero value).
> 
> > Possibly but clearly c has no major limitations once the hard part (the 
> > wrapper for the other applications) has been done. 
> 
> I would disagree.  For example, playing tricks with strings,
> pipes/redirects and files in C is a complete pain, compared with
> perl/python.  Most of the things I changed with the orignal bash
> version were in this subset, and it allowed me to customise it for
> what we were doing quickly and easily. 
> 

Good point. 
One other note, the C version should have a much smaller memory footprint then
Perl or Python - less likely to perturb test results. 
Speaking for myself, i think this is such a small pile of code, it might be fun
to have a parallel Perl/Python version. (it would be a good excuse for me to 
learn some Python)
My personal choice would be C to generate the data and Perl to pretty-print 
it.

 I need to get into the code more for STP integration, so i'll have more 
opinons
soon :)
cliffw


> -i
> ianw@gelato.unsw.edu.au
> http://www.gelato.unsw.edu.au
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



  reply	other threads:[~2003-01-15 19:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13 23:28 Con Kolivas
2003-01-15  3:16 ` Con Kolivas
2003-01-15  4:15   ` Ian Wienand
2003-01-15  4:39     ` Con Kolivas
2003-01-15  5:24       ` Ian Wienand
2003-01-15 19:28         ` Cliff White [this message]
2003-01-15 12:08     ` Άγγελος Οικονομόπουλος
2003-01-15 17:04     ` Cliff White

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=200301151928.h0FJSuW17921@mail.osdl.org \
    --to=cliffw@osdl.org \
    --cc=aoiko@cc.ece.ntua.gr \
    --cc=conman@kolivas.net \
    --cc=ianw@gelato.unsw.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®