Message from discussion
Erlang meets physics
Received: by 10.204.129.15 with SMTP id m15mr493171bks.2.1331771526257;
Wed, 14 Mar 2012 17:32:06 -0700 (PDT)
X-BeenThere: erlang-programming@googlegroups.com
Received: by 10.205.142.4 with SMTP id jg4ls3579695bkc.6.gmail; Wed, 14 Mar
2012 17:32:06 -0700 (PDT)
Received: by 10.204.131.75 with SMTP id w11mr495289bks.0.1331771525872;
Wed, 14 Mar 2012 17:32:05 -0700 (PDT)
Received: by 10.204.131.75 with SMTP id w11mr495288bks.0.1331771525829;
Wed, 14 Mar 2012 17:32: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 cs9si347266bkb.3.2012.03.14.17.32.05;
Wed, 14 Mar 2012 17:32: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
Received: from hades.cslab.ericsson.net (hades [192.121.151.104])
by hades.cslab.ericsson.net (Postfix) with ESMTP id 181EA5C2F5;
Thu, 15 Mar 2012 01:31:58 +0100 (CET)
X-Original-To: erlang-questi...@erlang.org
Delivered-To: erlang-questi...@erlang.org
Received: from mxout12.cac.washington.edu (mxout12.cac.washington.edu
[140.142.33.31])
by hades.cslab.ericsson.net (Postfix) with ESMTP id 096885C012
for <erlang-questi...@erlang.org>; Thu, 15 Mar 2012 01:31:54 +0100 (CET)
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.204] (may
be forged))
by mxout12.cac.washington.edu (8.14.4+UW11.03/8.14.4+UW12.02) with ESMTP id
q2F0U8sf019485
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
Wed, 14 Mar 2012 17:30:08 -0700
X-Auth-Received: from [10.0.1.3] (c-76-104-128-2.hsd1.wa.comcast.net
[76.104.128.2]) (authenticated authid=nancejk)
by smtp.washington.edu (8.14.4+UW11.03/8.14.4+UW11.03) with ESMTP id
q2F0U7NX019459
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
Wed, 14 Mar 2012 17:30:08 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
From: Jared Kofron <jared.na...@gmail.com>
In-Reply-To: <CAKrexV+JB2WpN+gW1s30E7hTM_RXavuzz6BAHVyF8uUxPfV...@mail.gmail.com>
Date: Wed, 14 Mar 2012 17:30:07 -0700
Message-Id: <40FAC330-B3A3-4123-BE08-FFF28A129...@gmail.com>
References: <BE8F08DF-B689-40E7-890F-1367143DB...@gmail.com>
<CAANBt-qSSS1O8G3+==4zsLu0zSkrWYXq0R+p39Np_fzLHQX...@mail.gmail.com>
<1331666426.33915.YahooMail...@web112614.mail.gq1.yahoo.com>
<E79D5C93-342E-4315-ACEE-59B959B76...@gmail.com>
<1331739205.24889.YahooMail...@web112620.mail.gq1.yahoo.com>
<CAKrexV+JB2WpN+gW1s30E7hTM_RXavuzz6BAHVyF8uUxPfV...@mail.gmail.com>
To: CGS <cgsmcml...@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-PMX-Version: 5.5.9.388399, Antispam-Engine: 2.7.2.376379,
Antispam-Data: 2012.3.15.1814
X-PMX-Server: mxout12.cac.washington.edu
X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='
FORGED_FROM_GMAIL 0.1, MIME_LOWER_CASE 0.05, SUPERLONG_LINE 0.05,
BODY_SIZE_10000_PLUS 0, CTYPE_MULTIPART_NO_QUOTE 0, DATE_TZ_NA 0,
ECARD_KNOWN_DOMAINS 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0,
__BOUNCE_NDR_SUBJ_EXEMPT 0, __CP_URI_IN_BODY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0,
__CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __FRAUD_BODY_WEBMAIL 0,
__FRAUD_WEBMAIL 0, __FRAUD_WEBMAIL_FROM 0, __FROM_GMAIL 0, __HAS_HTML 0,
__HAS_MSGID 0, __HAS_X_MAILER 0, __INT_PROD_COMP 0, __MIME_HTML 0,
__MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0,
__SANE_MSGID 0, __SUBJ_ALPHA_END 0, __TAG_EXISTS_HTML 0, __TO_MALFORMED_2 0,
__URI_NS , __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0'
Cc: Erlang Questions <erlang-questi...@erlang.org>
Subject: Re: [erlang-questions] Erlang meets physics
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="===============6715991477398015387=="
Errors-To: erlang-questions-boun...@erlang.org
Sender: erlang-questions-boun...@erlang.org
--===============6715991477398015387==
Content-Type: multipart/alternative; boundary=Apple-Mail-35--870594645
--Apple-Mail-35--870594645
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
On Mar 14, 2012, at 5:21 PM, CGS wrote:
> Hi,
>=20
> Firstly, I am glad to see physicists getting interest in Erlang.
>=20
> I see Erlang best usage in physics in few fields from =
Astrophysics/Astroparticle Physics/Elementary Particle Physics:
> 1. GRID;
> 2. integrated in the readout of an array of detectors for atmospheric =
showers,
Very true, these are great test cases for Erlang. EPICS is a project =
that accelerator folks wrote a long time ago (and still use and maintain =
to an extent)
that I think is a no-brainer application for Erlang: =
http://www.aps.anl.gov/epics/. It is written in C and forms a =
distributed data acquisition system.
> but there are few fields in which Erlang still cannot replace C/C++ =
(or Verilog in some cases):
> 1. accelerator (high and medium energy) physics (high frequency =
readout may not be compatible with Erlang, or vice-versa);
> 2. Monte Carlo simulations (even if it provides nice concurrency and =
code hot swap, it lacks some quite important characteristics).
>=20
> There may be some other fields from physics where Erlang may be =
suitable (except for communications for which is intended), but I am not =
the person to speak about. Nevertheless, it's good to know Erlang enters =
the above mentioned fields.
>=20
> Good luck!
> CGS
>=20
>=20
>=20
>=20
> On Wed, Mar 14, 2012 at 4:33 PM, Pablo Platt <pablo.pl...@yahoo.com> =
wrote:
> >which the device module (in this case hp8340b) translates into the =
GPIB command "OPCW", and based on the
> >device address (which is governed by the atom in the first argument), =
dispatches it over a bus handle that it owns
> >in a state variable via bus:send_query/2. =20
>=20
> Can you explain how the device module translate to the GPIB command =
"OPCW"?
> Is it pure erlang?
> Maybe you can share some code?
>=20
> Thanks
>=20
>=20
>=20
>=20
> ________________________________
> From: Jared Kofron <jared.na...@gmail.com>
> To: Erlang Questions <erlang-questi...@erlang.org>
> Sent: Wednesday, March 14, 2012 1:43 AM
> Subject: Re: [erlang-questions] Erlang meets physics
>=20
>=20
> Hi Pablo-
> My first project was on embedded hardware, and basically consisted of =
NIFs and Webmachine dispatching.
> Pretty fun stuff. =20
>=20
> My current project is a little more involved, but is also pretty =
interesting:
>=20
> Right now the bus over which communication takes place is abstracted =
away by having hardware modules
> which translate API functions into their appropriate wire =
representation and then transmit those representations
> over a handle that they have to the correct bus. =20
>=20
> In essence what I've done is taken instruments and buses and given =
them something like behaviors. =20
> Hardware can perform read,write,or configure, for example. So if I =
want to read the center frequency of a sweeper,
> I might say
>=20
> hp8340b:read(high_frequency_sweeper,<<"cw_freq">>).
>=20
> which the device module (in this case hp8340b) translates into the =
GPIB command "OPCW", and based on the
> device address (which is governed by the atom in the first argument), =
dispatches it over a bus handle that it owns
> in a state variable via bus:send_query/2. =20
>=20
> At the moment, we only communicate with things over GPIB via ethernet =
using prologix devices to do the translation
> for us - basically glorified telnet - but it gets the job done. =
Everything is in a very alpha stage right now for this project,
> but it is working really nicely so far.
>=20
> JK
>=20
> On Mar 13, 2012, at 12:20 PM, Pablo Platt wrote:
>=20
> How do you interact with the hardware?
> >Do you use GPIB C libr and wrap it with a NIF?
> >
> >
> >
> >________________________________
> > From: Joe Armstrong <erl...@gmail.com>
> >To: Jared Kofron <jared.na...@gmail.com>
> >Cc: Erlang Questions <erlang-questi...@erlang.org>
> >Sent: Tuesday, March 13, 2012 12:34 PM
> >Subject: Re: [erlang-questions] Erlang meets physics
> >
> >Great news - spread the word !
> >
> >Just for the record Erlang programmers numbers 1 and 2 (ie myself and
> >Robert Virding)
> >are both ex physicists.
> >
> >When I lecture I often point out the similarity between causality and
> >message reception.
> >You don't know that something has happened until you get a message
> >telling that it has happened.
> >
> >(In physics it's a ray of light, or a photon, or something -
> >forgetting entanglement for the moment)
> >
> >In computing it's the reception of a message.
> >
> >As a ex physicist I know that we can't say anything about =
simultaneous
> >events occurring
> >at different places in space-time - turn this into computer science
> >and the same arguments
> >apply to things like making sure replicated data is consistent on
> >remote sites - well you can't
> >- at least if you want to change it - Brewer's CAP theorem applies -
> >which for a physicist makes
> >perfect sense.
> >
> >Also as an ex physicist
> I realize that things do actually happen in
> >parallel in the real world,
> >so modelling them in a sequential programming language (if I wanted =
to do that)
> >is big time crazy - just describe the parallel stuff in a concurrent
> >language and the program
> >writes itself. Wait a few years till we have million core computers
> >and the parallel problems
> >can be solved 1:1 on parallel computers - and programming simulations
> >and so on will be
> >really easy - but don't even think about doing it in a sequential =
language...
> >
> >Cheers
> >
> >/Joe
> >
> >
> >On Mon, Mar 12, 2012 at 2:34 AM, Jared Kofron <jared.na...@gmail.com> =
wrote:
> >> Hi All,
> >> I've been using Erlang at work for a few years now, and I thought =
I'd throw my experience out there, as
> >> my application is a little different than what you usually see on =
the list - I am a graduate
> student at the
> >> Center for Nuclear Physics and Astrophysics at the University of =
Washington, and use Erlang extensively
> >> in my work.
> >>
> >> In my experience, something that Erlang is really great at but =
doesn't receive much attention for these days
> >> is managing and interacting with hardware. In any physics =
experiment of even modest sizes, you wind up
> >> having to keep track of the state of various pieces of equipment, =
often modify that state, and constantly
> >> interrogate particular values. For example, we might want to =
change the current in a magnetic trap, turn
> >> that trap off altogether, or simply read back the voltage drop =
across our superconducting magnet.
> >>
> >> So far, I have deployed Erlang in this zone for two separate =
experiments (SNO+, a large particle physics
> >> experiment in Canada) and Project 8 (a small nuclear physics =
experiment here in Seattle). Both times
> have
> >> been great successes, and I have found the reception of Erlang in =
this market to be great. In general, what
> >> I have done is wrap a hardware management layer with some kind of =
outside world interface. For SNO+, we
> >> used Webmachine and RESTful control, and for Project 8 we actually =
conduct all communication
> >> by using CouchDB as a message passing interface.
> >>
> >> Physicists are suspicious creatures, but once you demonstrate the =
feature set that you get for practically
> >> free with OTP, they see the advantage pretty quickly. On top of =
that, the development cycle for sophisticated
> >> applications can be greatly reduced - more than once it made my =
group float to the top in terms of meeting
> >> goals.
> >>
> >> In short, as far as I am concerned, Erlang has found a new niche in =
the world of Physics, and I intend to
> >> spread the word as much as I can!
> >>
> >> Jared
> Kofron
> >> _______________________________________________
> >> erlang-questions mailing list
> >> erlang-questi...@erlang.org
> >> http://erlang.org/mailman/listinfo/erlang-questions
> >_______________________________________________
> >erlang-questions mailing list
> >erlang-questi...@erlang.org
> >http://erlang.org/mailman/listinfo/erlang-questions
> >
> >
> >
>=20
> _______________________________________________
> erlang-questions mailing list
> erlang-questi...@erlang.org
> http://erlang.org/mailman/listinfo/erlang-questions
> _______________________________________________
> erlang-questions mailing list
> erlang-questi...@erlang.org
> http://erlang.org/mailman/listinfo/erlang-questions
>=20
> _______________________________________________
> erlang-questions mailing list
> erlang-questi...@erlang.org
> http://erlang.org/mailman/listinfo/erlang-questions
--Apple-Mail-35--870594645
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div><div><div>On Mar 14, 2012, at 5:21 PM, CGS =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Hi,<br><br>Firstly, I am glad to see physicists getting =
interest in Erlang.<br><br>I see Erlang best usage in physics in few =
fields from Astrophysics/Astroparticle Physics/Elementary Particle =
Physics:<br>1. GRID;<br>2. integrated in the readout of an array of =
detectors for atmospheric =
showers,<br></blockquote><div><br></div><div>Very true, these are great =
test cases for Erlang. EPICS is a project that accelerator folks =
wrote a long time ago (and still use and maintain to an =
extent)</div><div>that I think is a no-brainer application for =
Erlang: <a =
href=3D"http://www.aps.anl.gov/epics/">http://www.aps.anl.gov/epics/</a>. =
It is written in C and forms a distributed data acquisition =
system.</div><div><br></div><blockquote type=3D"cite">but there are few =
fields in which Erlang still cannot replace C/C++ (or Verilog in some =
cases):<br>1. accelerator (high and medium energy) physics (high =
frequency readout may not be compatible with Erlang, or =
vice-versa);</blockquote><blockquote type=3D"cite">
2. Monte Carlo simulations (even if it provides nice concurrency and =
code hot swap, it lacks some quite important =
characteristics).</blockquote><blockquote type=3D"cite"><br>There may be =
some other fields from physics where Erlang may be suitable (except for =
communications for which is intended), but I am not the person to speak =
about. Nevertheless, it's good to know Erlang enters the above mentioned =
fields.<br>
<br>Good luck!<br>CGS<br><br><br><br><br><div class=3D"gmail_quote">On =
Wed, Mar 14, 2012 at 4:33 PM, Pablo Platt <span dir=3D"ltr"><<a =
href=3D"mailto:pablo.pl...@yahoo.com">pablo.pl...@yahoo.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 class=3D"im">>which the device module (in this case hp8340b) =
translates into the GPIB command "OPCW", and based on the<br>
>device address (which is governed by the atom in the first =
argument), dispatches it over a bus handle that it owns<br>
>in a state variable via bus:send_query/2. <br>
<br>
</div>Can you explain how the device module translate to the GPIB =
command "OPCW"?<br>
Is it pure erlang?<br>
Maybe you can share some code?<br>
<br>
Thanks<br>
<br>
<br>
<br>
<br>
________________________________<br>
From: Jared Kofron <<a =
href=3D"mailto:jared.na...@gmail.com">jared.na...@gmail.com</a>><br>
To: Erlang Questions <<a =
href=3D"mailto:erlang-questi...@erlang.org">erlang-questi...@erlang.org</a=
>><br>
Sent: Wednesday, March 14, 2012 1:43 AM<br>
<div><div></div><div class=3D"h5">Subject: Re: [erlang-questions] Erlang =
meets physics<br>
<br>
<br>
Hi Pablo-<br>
My first project was on embedded hardware, and basically consisted of =
NIFs and Webmachine dispatching.<br>
Pretty fun stuff. <br>
<br>
My current project is a little more involved, but is also pretty =
interesting:<br>
<br>
Right now the bus over which communication takes place is abstracted =
away by having hardware modules<br>
which translate API functions into their appropriate wire representation =
and then transmit those representations<br>
over a handle that they have to the correct bus. <br>
<br>
In essence what I've done is taken instruments and buses and given them =
something like behaviors. <br>
Hardware can perform read,write,or configure, for example. So if I =
want to read the center frequency of a sweeper,<br>
I might say<br>
<br>
hp8340b:read(high_frequency_sweeper,<<"cw_freq">>).<br>
<br>
which the device module (in this case hp8340b) translates into the GPIB =
command "OPCW", and based on the<br>
device address (which is governed by the atom in the first argument), =
dispatches it over a bus handle that it owns<br>
in a state variable via bus:send_query/2. <br>
<br>
At the moment, we only communicate with things over GPIB via ethernet =
using prologix devices to do the translation<br>
for us - basically glorified telnet - but it gets the job done. =
Everything is in a very alpha stage right now for this =
project,<br>
but it is working really nicely so far.<br>
<br>
JK<br>
<br>
On Mar 13, 2012, at 12:20 PM, Pablo Platt wrote:<br>
<br>
How do you interact with the hardware?<br>
>Do you use GPIB C libr and wrap it with a NIF?<br>
><br>
><br>
><br>
>________________________________<br>
> From: Joe Armstrong <<a =
href=3D"mailto:erl...@gmail.com">erl...@gmail.com</a>><br>
>To: Jared Kofron <<a =
href=3D"mailto:jared.na...@gmail.com">jared.na...@gmail.com</a>><br>
>Cc: Erlang Questions <<a =
href=3D"mailto:erlang-questi...@erlang.org">erlang-questi...@erlang.org</a=
>><br>
>Sent: Tuesday, March 13, 2012 12:34 PM<br>
>Subject: Re: [erlang-questions] Erlang meets physics<br>
><br>
>Great news - spread the word !<br>
><br>
>Just for the record Erlang programmers numbers 1 and 2 (ie myself =
and<br>
>Robert Virding)<br>
>are both ex physicists.<br>
><br>
>When I lecture I often point out the similarity between causality =
and<br>
>message reception.<br>
>You don't know that something has happened until you get a =
message<br>
>telling that it has happened.<br>
><br>
>(In physics it's a ray of light, or a photon, or something -<br>
>forgetting entanglement for the moment)<br>
><br>
>In computing it's the reception of a message.<br>
><br>
>As a ex physicist I know that we can't say anything about =
simultaneous<br>
>events occurring<br>
>at different places in space-time - turn this into computer =
science<br>
>and the same arguments<br>
>apply to things like making sure replicated data is consistent =
on<br>
>remote sites - well you can't<br>
>- at least if you want to change it - Brewer's CAP theorem applies =
-<br>
>which for a physicist makes<br>
>perfect sense.<br>
><br>
>Also as an ex physicist<br>
I realize that things do actually happen in<br>
>parallel in the real world,<br>
>so modelling them in a sequential programming language (if I wanted =
to do that)<br>
>is big time crazy - just describe the parallel stuff in a =
concurrent<br>
>language and the program<br>
>writes itself. Wait a few years till we have million core =
computers<br>
>and the parallel problems<br>
>can be solved 1:1 on parallel computers - and programming =
simulations<br>
>and so on will be<br>
>really easy - but don't even think about doing it in a sequential =
language...<br>
><br>
>Cheers<br>
><br>
>/Joe<br>
><br>
><br>
>On Mon, Mar 12, 2012 at 2:34 AM, Jared Kofron <<a =
href=3D"mailto:jared.na...@gmail.com">jared.na...@gmail.com</a>> =
wrote:<br>
>> Hi All,<br>
>> I've been using Erlang at work for a few years now, and I =
thought I'd throw my experience out there, as<br>
>> my application is a little different than what you usually see =
on the list - I am a graduate<br>
student at the<br>
>> Center for Nuclear Physics and Astrophysics at the University =
of Washington, and use Erlang extensively<br>
>> in my work.<br>
>><br>
>> In my experience, something that Erlang is really great at but =
doesn't receive much attention for these days<br>
>> is managing and interacting with hardware. In any physics =
experiment of even modest sizes, you wind up<br>
>> having to keep track of the state of various pieces of =
equipment, often modify that state, and constantly<br>
>> interrogate particular values. For example, we might want =
to change the current in a magnetic trap, turn<br>
>> that trap off altogether, or simply read back the voltage drop =
across our superconducting magnet.<br>
>><br>
>> So far, I have deployed Erlang in this zone for two separate =
experiments (SNO+, a large particle physics<br>
>> experiment in Canada) and Project 8 (a small nuclear physics =
experiment here in Seattle). Both times<br>
have<br>
>> been great successes, and I have found the reception of Erlang =
in this market to be great. In general, what<br>
>> I have done is wrap a hardware management layer with some kind =
of outside world interface. For SNO+, we<br>
>> used Webmachine and RESTful control, and for Project 8 we =
actually conduct all communication<br>
>> by using CouchDB as a message passing interface.<br>
>><br>
>> Physicists are suspicious creatures, but once you demonstrate =
the feature set that you get for practically<br>
>> free with OTP, they see the advantage pretty quickly. On =
top of that, the development cycle for sophisticated<br>
>> applications can be greatly reduced - more than once it made my =
group float to the top in terms of meeting<br>
>> goals.<br>
>><br>
>> In short, as far as I am concerned, Erlang has found a new =
niche in the world of Physics, and I intend to<br>
>> spread the word as much as I can!<br>
>><br>
>> Jared<br>
Kofron<br>
>> _______________________________________________<br>
>> erlang-questions mailing list<br>
>> <a =
href=3D"mailto:erlang-questi...@erlang.org">erlang-questi...@erlang.org</a=
><br>
>> <a href=3D"http://erlang.org/mailman/listinfo/erlang-questions" =
target=3D"_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><=
br>
>_______________________________________________<br>
>erlang-questions mailing list<br>
><a =
href=3D"mailto:erlang-questi...@erlang.org">erlang-questi...@erlang.org</a=
><br>
><a href=3D"http://erlang.org/mailman/listinfo/erlang-questions" =
target=3D"_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><=
br>
><br>
><br>
><br>
<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a =
href=3D"mailto:erlang-questi...@erlang.org">erlang-questi...@erlang.org</a=
><br>
<a href=3D"http://erlang.org/mailman/listinfo/erlang-questions" =
target=3D"_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><=
br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a =
href=3D"mailto:erlang-questi...@erlang.org">erlang-questi...@erlang.org</a=
><br>
<a href=3D"http://erlang.org/mailman/listinfo/erlang-questions" =
target=3D"_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><=
br>
</div></div></blockquote></div><br>
_______________________________________________<br>erlang-questions =
mailing list<br><a =
href=3D"mailto:erlang-questi...@erlang.org">erlang-questi...@erlang.org</a=
><br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote><=
/div><br></body></html>=
--Apple-Mail-35--870594645--
--===============6715991477398015387==
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
--===============6715991477398015387==--