* new output re-direction syntax
@ 2014-03-08 19:29 Per Bothner
0 siblings, 0 replies; only message in thread
From: Per Bothner @ 2014-03-08 19:29 UTC (permalink / raw)
To: kawa
So far we have:
&<{PATH} ;; read named file/resource
(set! &<{PATH} VALUE) ;; set named file/resource
I just checked in:
(&>{PATH} VALUE) ;; set named file/resource
&>{PATH} basically evaluates to:
(lambda (newvalue) (set! &<{PATH} newvalue))
That seems more readable.
I'm considering extending pipe-process to allow:
(pipe-process EXP1 ... EXPN &>{PATH})
as a short-hand for:
(&>{PATH} (pipe-process EXP1 ... EXPN))
It's not clear this shorthand worth it to save two parentheses.
It's also not clear how general to be. We could allow
arbitrary one-argument lambda in the final position - that
actually looks to be the easiest implementation.
I'm working on a JavaOne presentation focusing
on named literals and the new shell/process features.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-03-08 19:29 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-03-08 19:29 new output re-direction syntax Per Bothner
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 read-only IMAP folder(s) and NNTP newsgroup(s).