Message from discussion
in-flight module transforms - request for comments
Received: by 10.204.7.214 with SMTP id e22mr247270bke.2.1318936505690;
Tue, 18 Oct 2011 04:15:05 -0700 (PDT)
X-BeenThere: erlang-programming@googlegroups.com
Received: by 10.204.146.137 with SMTP id h9ls410940bkv.1.gmail; Tue, 18 Oct
2011 04:15:05 -0700 (PDT)
Received: by 10.204.7.214 with SMTP id e22mr247264bke.2.1318936505393;
Tue, 18 Oct 2011 04:15:05 -0700 (PDT)
Received: by 10.204.7.214 with SMTP id e22mr247263bke.2.1318936505380;
Tue, 18 Oct 2011 04:15:05 -0700 (PDT)
Return-Path: <erlang-questions-boun...@erlang.org>
Received: from hades.cslab.ericsson.net (hades.cslab.ericsson.net. [192.121.151.104])
by gmr-mx.google.com with ESMTP id p10si285546bkq.2.2011.10.18.04.15.05;
Tue, 18 Oct 2011 04:15:05 -0700 (PDT)
Received-SPF: pass (google.com: domain of erlang-questions-boun...@erlang.org designates 192.121.151.104 as permitted sender) client-ip=192.121.151.104;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of erlang-questions-boun...@erlang.org designates 192.121.151.104 as permitted sender) smtp.mail=erlang-questions-boun...@erlang.org; dkim=neutral (body hash did not verify) header...@gmail.com
Received: from hades.cslab.ericsson.net (hades [192.121.151.104])
by hades.cslab.ericsson.net (Postfix) with ESMTP id 7BDA55C145;
Tue, 18 Oct 2011 13:15:00 +0200 (CEST)
X-Original-To: erlang-questi...@erlang.org
Delivered-To: erlang-questi...@erlang.org
Received: from mail-qy0-f174.google.com (mail-qy0-f174.google.com
[209.85.216.174])
by hades.cslab.ericsson.net (Postfix) with ESMTP id DA07B5C000
for <erlang-questi...@erlang.org>; Tue, 18 Oct 2011 13:14:58 +0200 (CEST)
Received: by qyk4 with SMTP id 4so3097589qyk.19
for <erlang-questi...@erlang.org>; Tue, 18 Oct 2011 04:14:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=E5r6w4nWZ+mvBKaUGL5wFuuDB0xqdZjhDEEtbCQRWuQ=;
b=Js9z4UsbBxb7gYT8w+pPCzGgJZC/hstzayjaZWtSs782Vx6yXcCeRLjSGwsdFT2IoA
4UernTh+qZVypAoZzbyl4Oiw09+Ycjy26jfP8c/agHo1HW3UFTN89l/2HiyPPl+hO6CN
fTIXKfG5cXvHl+uMB6j9wbZKxac1Jfdzzah+8=
MIME-Version: 1.0
Received: by 10.229.36.14 with SMTP id r14mr417171qcd.23.1318936498237; Tue,
18 Oct 2011 04:14:58 -0700 (PDT)
Received: by 10.229.237.209 with HTTP; Tue, 18 Oct 2011 04:14:58 -0700 (PDT)
In-Reply-To: <40EF3227-F8CA-472C-99DF-22195B9C3...@erlang-solutions.com>
References: <40EF3227-F8CA-472C-99DF-22195B9C3...@erlang-solutions.com>
Date: Tue, 18 Oct 2011 12:14:58 +0100
Message-ID: <CALhYyxMQ__oGz12xdyBcBDc9xT9XO+XuNwvy3Htr-PM0Jgh...@mail.gmail.com>
From: Tim Watson <watson.timo...@gmail.com>
To: Ulf Wiger <ulf.wi...@erlang-solutions.com>
Cc: "erlang-questi...@erlang.org Questions" <erlang-questi...@erlang.org>
Subject: Re: [erlang-questions] in-flight module transforms - request for
comments
X-BeenThere: erlang-questi...@erlang.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: General Erlang/OTP discussions <erlang-questions.erlang.org>
List-Unsubscribe: <http://erlang.org/mailman/options/erlang-questions>,
<mailto:erlang-questions-requ...@erlang.org?subject=unsubscribe>
List-Archive: <http://erlang.org/pipermail/erlang-questions>
List-Post: <mailto:erlang-questi...@erlang.org>
List-Help: <mailto:erlang-questions-requ...@erlang.org?subject=help>
List-Subscribe: <http://erlang.org/mailman/listinfo/erlang-questions>,
<mailto:erlang-questions-requ...@erlang.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============7881026006404939328=="
Errors-To: erlang-questions-boun...@erlang.org
Sender: erlang-questions-boun...@erlang.org
--===============7881026006404939328==
Content-Type: multipart/alternative; boundary=0016367b700a7570b304af90d594
--0016367b700a7570b304af90d594
Content-Type: text/plain; charset=ISO-8859-1
On 18 October 2011 11:06, Ulf Wiger <ulf.wi...@erlang-solutions.com> wrote:
> For those of you out there who have used similar things before, what kind
> of support would you like to see?
>
I'm interesting in writing up some simple code instrumentation tools so I
can do stuff like declaratively inserting performance counters and/or
logging statements into my code. I've already used parse_trans and love it,
but doing this without forcing users into using a parse_transform sounds
really good - a post compile step provided by a rebar plugin could transform
the beam code afterwards, or as you say this can even be done at runtime.
One thing that would be useful would be some kind of qlc-esque selection
mechanism for finding code that matches certain conditions. Whether these
are match specifications or something else, they would make a very useful
addition. Matching on type/spec information would be even better, although I
suspect that's a little outside of the scope you're looking at right now.
Cheers,
Tim
--0016367b700a7570b304af90d594
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_quote">On 18 October 2011 11:06, Ulf Wiger <span dir=3D=
"ltr"><<a href=3D"mailto:ulf.wi...@erlang-solutions.com">ulf.wiger@erlan=
g-solutions.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word"><div>For those of you out there who hav=
e used similar things before, what kind of support would you like to see?</=
div><div></div></div></blockquote></div><br><div>I'm interesting in wri=
ting up some simple code instrumentation tools so I can do stuff like decla=
ratively inserting performance counters and/or logging statements into my c=
ode. I've already used parse_trans and love it, but doing this without =
forcing users into using a parse_transform sounds really good - a post comp=
ile step provided by a rebar plugin could transform the beam code afterward=
s, or as you say this can even be done at runtime.</div>
<div><br></div><div>One thing that would be useful would be some kind of ql=
c-esque selection mechanism for finding code that matches certain condition=
s. Whether these are match specifications or something else, they would mak=
e a very useful addition. Matching on type/spec information would be even b=
etter, although I suspect that's a little outside of the scope you'=
re looking at right now.</div>
<div><br></div><div>Cheers,</div><div><br></div><div>Tim</div>
--0016367b700a7570b304af90d594--
--===============7881026006404939328==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions
--===============7881026006404939328==--