From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: "Douglas A. Gwyn" <DAGwyn@null.net>
Message-ID: <3F051817.3050207@null.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
References: <200307031830.OAA05117@plg2.math.uwaterloo.ca>, <002701c341ce$35f939e0$d2944251@insultant.net>
Subject: Re: [9fans] sam hacking - a couple of fixes that may apply t
Date: Fri,  4 Jul 2003 08:59:53 +0000
Topicbox-Message-UUID: e89869b4-eacb-11e9-9e20-41e7f4b1d025

boyd, rounin wrote:
> rob wrote in one of the sam papers (iirc) that most people don't use
> complex sam commands.  i used to be like that, until i learnt the error
> of my ways, so now i construct fairly complex stuff and refine it till
> it's right.

In BRL's MUVES project, one of our Makefile targets was a
profiled source listing, i.e. execution counts (for a test
run) alongside each source line.  Since there was no tool
on our Unix systems that did that, I cobbled one up as a
combination of existing tools and a "sam" script that was
several hundred characters long.  Worked fine!

I have a file of "macors" for sam; I open that file as one
file within "sam", then snarf and send to execute when
needed.