9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Alexander Sychev <santucco@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] hoc output format
Date: Thu, 13 May 2010 18:06:29 +0400	[thread overview]
Message-ID: <op.vcndg3knhipq0d@santucco.avp.ru> (raw)
In-Reply-To: <158d5dc0571fa04cab44a99b3fdf5921@kw.quanstro.net>

On Thu, 13 May 2010 17:24:47 +0400, erik quanstrom <quanstro@quanstro.net>  
wrote:

> On Thu May 13 03:51:56 EDT 2010, santucco@gmail.com wrote:
>> Yes, I'm agree, but with one exception - awk(1) separates a data from a
>> code, hoc(1) doesn't do it. So hoc(1) can be used for plain calculation
>> tasks, not for  processing input files with a data.
>
> both awk and hoc accept standard input

Yes, but for hoc(1) it can be some program, for awk(1) it can be a data  
only :-) - that is what I meant :-)

> 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 ';'?

-- 
Best regards,
   santucco



  reply	other threads:[~2010-05-13 14:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 10:24 Rudolf Sykora
2010-05-12 10:41 ` Alexander Sychev
2010-05-12 18:06   ` Akshat Kumar
2010-05-13  7:51     ` Alexander Sychev
2010-05-13 13:24       ` erik quanstrom
2010-05-13 14:06         ` Alexander Sychev [this message]
2010-05-13 14:23           ` erik quanstrom
2010-05-13 15:04             ` Ethan Grammatikidis
2010-05-13 15:09             ` Gorka Guardiola
2010-05-13 15:37               ` erik quanstrom
2010-05-13 15:16             ` roger peppe
2010-05-13 15:31               ` erik quanstrom
2010-05-13 15:53                 ` roger peppe
2010-05-13 16:06                   ` erik quanstrom
2010-05-13 16:16                     ` roger peppe
2010-05-13 15:54               ` Ethan Grammatikidis
2010-05-13 16:08                 ` roger peppe
2010-05-13 15:20             ` Rudolf Sykora

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=op.vcndg3knhipq0d@santucco.avp.ru \
    --to=santucco@gmail.com \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).