From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <5B5AFBEB-D6BD-4218-89B3-CB7EA05C1AAB@fastmail.fm> From: Ethan Grammatikidis To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: <84f53dabe8357c852216d6c9024f6eb0@coraid.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Thu, 13 May 2010 16:04:41 +0100 References: <158d5dc0571fa04cab44a99b3fdf5921@kw.quanstro.net> <84f53dabe8357c852216d6c9024f6eb0@coraid.com> Subject: Re: [9fans] hoc output format Topicbox-Message-UUID: 2049aeb8-ead6-11e9-9d60-3106f5b1d025 On 13 May 2010, at 15:23, erik quanstrom wrote: >>> echo 1 2 | hoc -e '{while(read(x) != 0)y += x' ^ $nl ^ ' print y, >>> "\n"}' >> >> Maybe it makes a sense to add in hoc(1) expression delimiter like a >> ';'? > > i don't use hoc very often. i tend to use acid. (!) > this is because hoc won't do bit operations and doesn't > accept hex. Acid is nicer than dc or bc for this? I don't do much in the way of programming calculations at present and usually resort to dc to do them. Anything more convenient would be appreciated. :) As for hoc, I'm mostly doing floating-point work where presentation is irrelevant, so it's quite useful for me, but too often I find myself preferring to use one of those silly graphical calculator applications just to cut down on the visual noise. -- Simplicity does not precede complexity, but follows it. -- Alan Perlis