tag:old.nabble.com,2006:forum-14095Nabble - Erlang2009-11-26T13:32:06ZErlang is a programming language which has many features more commonly associated with an operating system than with a programming language: concurrent processes, scheduling, memory management, distribution, networking, etc. Erlang home is <a href="http://www.erlang.org/" target="_top" rel="nofollow">here</a>.tag:old.nabble.com,2006:post-26535172Re: R13B03: dialyzer --apps option not documented2009-11-26T13:32:06Z2009-11-26T13:32:06ZKostis Sagonas-2Bernard Duggan wrote:
<div class='shrinkable-quote'><br>> Kostis Sagonas wrote:
<br>>> Ulf Wiger wrote:
<br>>>> The new --apps option for Dialyzer is mentioned in the release notes,
<br>>>> and
<br>>>> seems to work, but it is not mentioned in the reference manual, user
<br>>>> guide
<br>>>> or the built-in help (dialyzer --help).
<br>>> Indeed it isn't. It will be. Thanks for bringing this to our attention.
<br>>>
<br>>> Kostis
<br>> I'm sure you would have noticed when adding --apps, but the same also
<br>> goes for the new -Wrace_conditions
</div><br>Yep. Did notice and since three hours ago it's checked in to our
<br>repository.
<br><br>> (which, having taken for a test-drive yesterday, I have to say is really cool).
<br><br>I would be curious to know what/how many bugs you have discovered but we
<br>can take that off this list...
<br><br>Cheers,
<br>Kostis
<br><br>________________________________________________________________
<br>erlang-bugs mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-bugs (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Bugs-f14097.html" embed="fixTarget[14097]" target="_top" >Erlang Bugs</a></p>tag:old.nabble.com,2006:post-26535033Re: R13B03: dialyzer --apps option not documented2009-11-26T13:20:36Z2009-11-26T13:20:36ZBernard Duggan-2Kostis Sagonas wrote:
<div class='shrinkable-quote'><br>> Ulf Wiger wrote:
<br>>> The new --apps option for Dialyzer is mentioned in the release notes,
<br>>> and
<br>>> seems to work, but it is not mentioned in the reference manual, user
<br>>> guide
<br>>> or the built-in help (dialyzer --help).
<br>>
<br>> Indeed it isn't. It will be. Thanks for bringing this to our attention.
<br>>
<br>> Kostis
</div>I'm sure you would have noticed when adding --apps, but the same also
<br>goes for the new -Wrace_conditions (which, having taken for a test-drive
<br>yesterday, I have to say is really cool).
<br><br>Cheers,
<br><br>Bernard
<br><br><br>________________________________________________________________
<br>erlang-bugs mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-bugs (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Bugs-f14097.html" embed="fixTarget[14097]" target="_top" >Erlang Bugs</a></p>tag:old.nabble.com,2006:post-26534630Which postgresql driver2009-11-26T12:34:46Z2009-11-26T12:34:46ZMax Lapshin-2There are several of postgresql drivers and I cannot select which is
<br>supported currently.
<br>It seems, that this one is best for now:
<br><a href="http://github.com/joshuamiller/epgsql-utf8" target="_top" rel="nofollow">http://github.com/joshuamiller/epgsql-utf8</a>, epgsql is used in zootonic
<br>and this fork claims to support utf8 properly (haven't look at code,
<br>to get out, what it means).
<br><br>So, which are working?
<br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26534346Re: A little update on submitting patches2009-11-26T12:05:58Z2009-11-26T12:05:58ZBjörn GustavssonOn Thu, Nov 26, 2009 at 8:36 PM, Vincent de Phily
<br><<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26534346&i=0" target="_top" rel="nofollow">vincent.dephily@...</a>> wrote:
<br><br>> Should I use this as an occasion to re-submit patches that have only received
<br>> a general aknowledgement a while ago, and never got merged ?
<br><br>Yes, that is a good idea.
<br><br>--
<br>Björn Gustavsson, Erlang/OTP, Ericsson AB
<br><br>________________________________________________________________
<br>erlang-patches mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-patches (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Patches-f14098.html" embed="fixTarget[14098]" target="_top" >Erlang Patches</a></p>tag:old.nabble.com,2006:post-26534061Re: A little update on submitting patches2009-11-26T11:36:34Z2009-11-26T11:36:34ZVincent de PhilyOn Thursday 26 November 2009 19:57:26 Björn Gustavsson wrote:
<br>> There is now a basic wiki page on-line about submitting patches:
<br>>
<br>> <a href="http://wiki.github.com/erlang/otp/submitting-patches" target="_top" rel="nofollow">http://wiki.github.com/erlang/otp/submitting-patches</a><br><br>Should I use this as an occasion to re-submit patches that have only received
<br>a general aknowledgement a while ago, and never got merged ? We have a couple
<br>of those that we use in production, and would like to either see them merged,
<br>or work around the issues in our application code instead of maintaining a
<br>patched erlang.
<br><br>--
<br>Vincent de Phily
<br>Mobile Devices
<br>+33 (0) 142 119 325
<br>+353 (0) 85 710 6320
<br><br>Warning
<br>This message (and any associated files) is intended only for the use of its
<br>intended recipient and may contain information that is confidential, subject
<br>to copyright or constitutes a trade secret. If you are not the intended
<br>recipient you are hereby notified that any dissemination, copying or
<br>distribution of this message, or files associated with this message, is
<br>strictly prohibited. If you have received this message in error, please
<br>notify us immediately by replying to the message and deleting it from your
<br>computer. Any views or opinions presented are solely those of the author
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26534061&i=0" target="_top" rel="nofollow">vincent.dephily@...</a> and do not necessarily represent those of
<br>the
<br>company. Although the company has taken reasonable precautions to ensure no
<br>viruses are present in this email, the company cannot accept responsibility
<br>for any loss or damage arising from the use of this email or attachments.
<br><br>________________________________________________________________
<br>erlang-patches mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-patches (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Patches-f14098.html" embed="fixTarget[14098]" target="_top" >Erlang Patches</a></p>tag:old.nabble.com,2006:post-26533797Requests for comments on proposed updates of README2009-11-26T11:08:50Z2009-11-26T11:08:50ZBjörn Gustavssonngerakines has cleaned up the README:
<br><br><a href="http://github.com/erlang/otp/blob/pu/README" target="_top" rel="nofollow">http://github.com/erlang/otp/blob/pu/README</a><br><br>The diff can be found here:
<br><br><a href="http://github.com/erlang/otp/commit/b1d712bcc0c7b44abc357147e568da4d76d36e47" target="_top" rel="nofollow">http://github.com/erlang/otp/commit/b1d712bcc0c7b44abc357147e568da4d76d36e47</a><br><br>Is the new README easier to read? Is the old README better in some way?
<br><br>--
<br>Björn Gustavsson, Erlang/OTP, Ericsson AB
<br><br>________________________________________________________________
<br>erlang-patches mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-patches (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Patches-f14098.html" embed="fixTarget[14098]" target="_top" >Erlang Patches</a></p>tag:old.nabble.com,2006:post-26533680Re: Re: PATCH: update of non existing row returns {error,"No SQL-driver information available."}2009-11-26T10:59:36Z2009-11-26T10:59:36ZBjörn Gustavsson2009/11/26 Paul Oliver <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26533680&i=0" target="_top" rel="nofollow">puzza007@...</a>>:
<div class='shrinkable-quote'><br>> 2009/11/26 Björn Gustavsson <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26533680&i=1" target="_top" rel="nofollow">bgustavsson@...</a>>:
<br>>> Do you think you could do a "git commit --amend" and put the information
<br>>> from your two emails into the commit message? That is, why you do this
<br>>> change (the bug that it will fix described in your first email), and also the
<br>>> mention of MSDN and the URL in this email.
<br>>>
<br>>> (Advice like the above on what to include in commit messages will be added
<br>>> to the wiki pages.)
<br>>
<br>> Done.
<br>>
</div><br>Thanks!
<br><br>Now merged to the 'pu' branch.
<br><br>--
<br>Björn Gustavsson, Erlang/OTP, Ericsson AB
<br><br>________________________________________________________________
<br>erlang-patches mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-patches (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Patches-f14098.html" embed="fixTarget[14098]" target="_top" >Erlang Patches</a></p>tag:old.nabble.com,2006:post-26533663A little update on submitting patches2009-11-26T10:57:26Z2009-11-26T10:57:26ZBjörn GustavssonThere is now a basic wiki page on-line about submitting patches:
<br><br> <a href="http://wiki.github.com/erlang/otp/submitting-patches" target="_top" rel="nofollow">http://wiki.github.com/erlang/otp/submitting-patches</a><br><br>It will be updated with more information and guidelines.
<br><br>We will merge all patches to the branch 'pu' ("proposed updates")
<br>so that we will have all proposed patches in one place.
<br><br>As we review patches, patches may graduate and be included
<br>in the development branch for the next release (ccase/r13b04_dev).
<br><br>You should not base any branches on 'pu', since it will be
<br>rewinded very often as patches graduate or an initial patch is
<br>replaced with an improved version.
<br><br>At the moment, 4 patch series (branches) have been merged
<br>to the 'pu' branch.
<br><br>--
<br>Björn Gustavsson, Erlang/OTP, Ericsson AB
<br><br>________________________________________________________________
<br>erlang-patches mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-patches (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Patches-f14098.html" embed="fixTarget[14098]" target="_top" >Erlang Patches</a></p>tag:old.nabble.com,2006:post-26531061Re: Re: PATCH: update of non existing row returns {error,"No SQL-driver information available."}2009-11-26T07:29:22Z2009-11-26T07:29:22Zpuzza0072009/11/26 Björn Gustavsson <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26531061&i=0" target="_top" rel="nofollow">bgustavsson@...</a>>:
<div class='shrinkable-quote'><br>> On Thu, Nov 26, 2009 at 3:04 PM, Paul Oliver <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26531061&i=1" target="_top" rel="nofollow">puzza007@...</a>> wrote:
<br>>> I've changed the patch to follow the advice given on MSDN
<br>>> (<a href="http://msdn.microsoft.com/en-us/library/ms715424%28VS.85%29.aspx" target="_top" rel="nofollow">http://msdn.microsoft.com/en-us/library/ms715424%28VS.85%29.aspx</a>) and
<br>>> check for SQL_NO_DATA combined with SQLSTATE 00000. The resulting
<br>>> patch is on github:
<br>>>
<br>>> <a href="http://github.com/puzza007/otp/tree/odbc_update_delete_no_rows" target="_top" rel="nofollow">http://github.com/puzza007/otp/tree/odbc_update_delete_no_rows</a><br>>
<br>> Thanks!
<br>>
<br>> Do you think you could do a "git commit --amend" and put the information
<br>> from your two emails into the commit message? That is, why you do this
<br>> change (the bug that it will fix described in your first email), and also the
<br>> mention of MSDN and the URL in this email.
<br>>
<br>> (Advice like the above on what to include in commit messages will be added
<br>> to the wiki pages.)
</div><br>Done.
<br><br>Thanks!
<br><br>Paul.
<br><br>________________________________________________________________
<br>erlang-patches mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-patches (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Patches-f14098.html" embed="fixTarget[14098]" target="_top" >Erlang Patches</a></p>tag:old.nabble.com,2006:post-26530672Re: Re: PATCH: update of non existing row returns {error,"No SQL-driver information available."}2009-11-26T07:02:46Z2009-11-26T07:02:46ZBjörn GustavssonOn Thu, Nov 26, 2009 at 3:04 PM, Paul Oliver <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26530672&i=0" target="_top" rel="nofollow">puzza007@...</a>> wrote:
<br>> I've changed the patch to follow the advice given on MSDN
<br>> (<a href="http://msdn.microsoft.com/en-us/library/ms715424%28VS.85%29.aspx" target="_top" rel="nofollow">http://msdn.microsoft.com/en-us/library/ms715424%28VS.85%29.aspx</a>) and
<br>> check for SQL_NO_DATA combined with SQLSTATE 00000. The resulting
<br>> patch is on github:
<br>>
<br>> <a href="http://github.com/puzza007/otp/tree/odbc_update_delete_no_rows" target="_top" rel="nofollow">http://github.com/puzza007/otp/tree/odbc_update_delete_no_rows</a><br><br>Thanks!
<br><br>Do you think you could do a "git commit --amend" and put the information
<br>from your two emails into the commit message? That is, why you do this
<br>change (the bug that it will fix described in your first email), and also the
<br>mention of MSDN and the URL in this email.
<br><br>(Advice like the above on what to include in commit messages will be added
<br>to the wiki pages.)
<br><br>--
<br>Björn Gustavsson, Erlang/OTP, Ericsson AB
<br><br>________________________________________________________________
<br>erlang-patches mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-patches (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Patches-f14098.html" embed="fixTarget[14098]" target="_top" >Erlang Patches</a></p>tag:old.nabble.com,2006:post-26529906Re: PATCH: update of non existing row returns {error,"No SQL-driver information available."}2009-11-26T06:04:34Z2009-11-26T06:04:34Zpuzza007I've changed the patch to follow the advice given on MSDN
<br>(<a href="http://msdn.microsoft.com/en-us/library/ms715424%28VS.85%29.aspx" target="_top" rel="nofollow">http://msdn.microsoft.com/en-us/library/ms715424%28VS.85%29.aspx</a>) and
<br>check for SQL_NO_DATA combined with SQLSTATE 00000. The resulting
<br>patch is on github:
<br><br><a href="http://github.com/puzza007/otp/tree/odbc_update_delete_no_rows" target="_top" rel="nofollow">http://github.com/puzza007/otp/tree/odbc_update_delete_no_rows</a><br><br>Cheers,
<br>Paul.
<br><br>On Tue, Nov 24, 2009 at 11:02 AM, Paul Oliver <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26529906&i=0" target="_top" rel="nofollow">puzza007@...</a>> wrote:
<div class='shrinkable-quote'><br>> Hi all,
<br>>
<br>> I noticed the following when no rows were updated for an update statement:
<br>>
<br>> 4> odbc:param_query(Ref, "update tbadger set status = ? where
<br>> badger_id = ?", [{{sql_varchar,1},["R"]}, {sql_integer, [61111]}]).
<br>> {error,"No SQL-driver information available."}
<br>> 5> odbc:param_query(Ref, "update tbadger set status = ? where
<br>> badger_id = ?", [{{sql_varchar,1},["R"]}, {sql_integer, [61]}]).
<br>> {updated,1}
<br>>
<br>> The attached patch, which requires the ODBC patch from Andrew
<br>> Thompson, should fix it:
<br>>
<br>> 3> odbc:param_query(Ref, "update tbadger set status = ? where
<br>> badger_id = ?", [{{sql_varchar,1},["R"]}, {sql_integer, [61111]}]).
<br>> {updated,0}
<br>> 4>
<br>>
<br>> Cheers,
<br>> Paul.
<br>>
</div><br>________________________________________________________________
<br>erlang-patches mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-patches (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Patches-f14098.html" embed="fixTarget[14098]" target="_top" >Erlang Patches</a></p>tag:old.nabble.com,2006:post-26527386Re: R13B03: dialyzer --apps option not documented2009-11-26T02:31:38Z2009-11-26T02:31:38ZKostis Sagonas-2Ulf Wiger wrote:
<br>> The new --apps option for Dialyzer is mentioned in the release notes, and
<br>> seems to work, but it is not mentioned in the reference manual, user guide
<br>> or the built-in help (dialyzer --help).
<br><br>Indeed it isn't. It will be. Thanks for bringing this to our attention.
<br><br>Kostis
<br><br>________________________________________________________________
<br>erlang-bugs mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-bugs (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Bugs-f14097.html" embed="fixTarget[14097]" target="_top" >Erlang Bugs</a></p>tag:old.nabble.com,2006:post-26527349R13B03: dialyzer --apps option not documented2009-11-26T02:29:00Z2009-11-26T02:29:00ZUlf WigerThe new --apps option for Dialyzer is mentioned in the release notes, and
<br>seems to work, but it is not mentioned in the reference manual, user guide
<br>or the built-in help (dialyzer --help).
<br><br>BR,
<br>Ulf W
<br><br><br>________________________________________________________________
<br>erlang-bugs mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-bugs (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Bugs-f14097.html" embed="fixTarget[14097]" target="_top" >Erlang Bugs</a></p>tag:old.nabble.com,2006:post-26524812Reia: moving closer to Erlang2009-11-25T22:19:01Z2009-11-25T22:19:01ZTony ArcieriReia is a language with Ruby-like syntax on top of the Erlang VM:
<br><br><a href="http://reia-lang.org/" target="_top" rel="nofollow">http://reia-lang.org/</a><br><br>It's been undergoing a bit of a transition, abandoning many of the features
<br>which differentiate it from Erlang and focusing on merely providing a
<br>cleaner syntax with destructive assignment:
<br><br><a href="http://www.unlimitednovelty.com/2009/11/new-reia-now-without-rainbow-farting.html" target="_top" rel="nofollow">http://www.unlimitednovelty.com/2009/11/new-reia-now-without-rainbow-farting.html</a><br><br>This is inspired to a large degree by Robert Virding's Lisp Flavoured Erlang
<br>(LFE), which does something similar.
<br><br>Future versions of the language will focus on additional features which are
<br>not present in the Erlang language itself, Until then, Reia will focus on
<br>attaining complete feature parity with Erlang and reaching a
<br>production-quality implementation.
<br><br>--
<br>Tony Arcieri
<br>Medioh/Nagravision
<br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26524795Re: Fastest pseudo-random number-generator: erlang:statistics(io) ?2009-11-25T22:14:30Z2009-11-25T22:14:30ZKenji RikitakeWriting a linked-in driver with SFMT will give you much faster solution.
<br>Or probably in NIF?
<br><br>SIMD-oriented Fast Mersenne Twister (SFMT)
<br><a href="http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/SFMT/index.html" target="_top" rel="nofollow">http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/SFMT/index.html</a><br>(C code available)
<br><br>Kenji Rikitake
<br><br>In the message <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26524795&i=0" target="_top" rel="nofollow">af660f57-3816-44fd-8f96-57676ecd6d36@...</a>>
<br>dated Tue, Nov 24, 2009 at 06:59:45AM -0800,
<br>Thijs <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26524795&i=1" target="_top" rel="nofollow">thijsterlouw@...</a>> writes:
<br>> Today I needed a faster alternative for erlang:now(). It turns out
<br>> that using erlang:now() is quite slow: it requires a system call. I
<br>> decided to test some alternatives. My requirements are: speed, speed,
<br>> speed :) I will use it in a server that is quite busy, so I figured I
<br>> could use various system metrics to generate random numbers. I use
<br>> these pseudo-random numbers to do load-balancing, log requests at
<br>> random etc.
<br><br>(rest snapped)
<br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26524677Re: Erlang/OTP now at Github2009-11-25T21:52:36Z2009-11-25T21:52:36ZBjörn GustavssonOn Wed, Nov 25, 2009 at 3:20 PM, Juan Jose Comellas <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26524677&i=0" target="_top" rel="nofollow">juanjo@...</a>> wrote:
<br>> Why was the commit history discarded? Wouldn't it be better to at
<br>> least preserve the history corresponding to the public releases? Maybe
<br>> you could use Matthew Foemmel's repository[1] in Github as a base.
<br>>
<br>> [1] <a href="http://github.com/mfoemmel/erlang-otp/" target="_top" rel="nofollow">http://github.com/mfoemmel/erlang-otp/</a><br><br>I have added a wiki page explaining how you can prepend
<br>mfoemmel's history to our history by using two
<br>simple commands:
<br><br><a href="http://wiki.github.com/erlang/otp/extending-the-history-of-erlangotp" target="_top" rel="nofollow">http://wiki.github.com/erlang/otp/extending-the-history-of-erlangotp</a><br><br>--
<br>Björn Gustavsson, Erlang/OTP, Ericsson AB
<br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26524058Re: Fastest pseudo-random number-generator: erlang:statistics(io) ?2009-11-25T19:57:40Z2009-11-25T19:57:40ZThijs TerlouwThe new nif (native implemented functions) provide a great alternative
<br>to generate random numbers and timestamps, much faster than the Erlang
<br>alternatives!
<br><br>The speed is about 1/2 to 1/3 of statistics(io), but still much faster
<br>than erlang:now().
<br>I simply used time(0) for the nif_now() and gettimeofday(&tv, NULL)
<br>for the nif_random() functions.
<br><br>nif's are a great addition to the language!
<br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><div class="signature">- Thijs Terlouw, <a href="http://www.startinchina.com" target="_top" rel="nofollow">Shenzhen, China</a></div><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26523813Erlang R13B03 *EXPERIMENTAL* FreeBSD port2009-11-25T18:29:00Z2009-11-25T18:29:00ZKenji RikitakeFreeBSD *EXPERIMENTAL* (unofficial) port for R13B03
<br>available at
<br><a href="http://www.ne.jp/asahi/bdx/info/software/erlang-r13b03,1-20091126-1.tar.gz" target="_top" rel="nofollow">http://www.ne.jp/asahi/bdx/info/software/erlang-r13b03,1-20091126-1.tar.gz</a><br><br>KNOWN issues:
<br><br>* NO JAVA test yet (WITHOUT_JAVA=yes set in the Makefile)
<br>* Makefile.man has been put dupes of snmp*.3 in MAN3/MAN6/MAN7
<br> (necessary to remove errors on "make package")
<br>* r13b02_1,1 fix (of Steve Vinocki's erlang.el) hasn't been merged
<br><br>I've sent this port to Giacomo Olgeni (the official port maintainer) so
<br>I hope he'll use mine as a feedback source.
<br><br>Kenji Rikitake
<br><br><br><br>________________________________________________________________
<br>erlang-patches mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-patches (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Patches-f14098.html" embed="fixTarget[14098]" target="_top" >Erlang Patches</a></p>tag:old.nabble.com,2006:post-26523566Erlang R13B03 *EXPERIMENTAL* FreeBSD port2009-11-25T18:29:00Z2009-11-25T18:29:00ZKenji RikitakeFreeBSD *EXPERIMENTAL* (unofficial) port for R13B03
<br>available at
<br><a href="http://www.ne.jp/asahi/bdx/info/software/erlang-r13b03,1-20091126-1.tar.gz" target="_top" rel="nofollow">http://www.ne.jp/asahi/bdx/info/software/erlang-r13b03,1-20091126-1.tar.gz</a><br><br>KNOWN issues:
<br><br>* NO JAVA test yet (WITHOUT_JAVA=yes set in the Makefile)
<br>* Makefile.man has been put dupes of snmp*.3 in MAN3/MAN6/MAN7
<br> (necessary to remove errors on "make package")
<br>* r13b02_1,1 fix (of Steve Vinocki's erlang.el) hasn't been merged
<br><br>I've sent this port to Giacomo Olgeni (the official port maintainer) so
<br>I hope he'll use mine as a feedback source.
<br><br>Kenji Rikitake
<br><br><br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26522575Re: How to match on a nested record against a dict2009-11-25T16:09:28Z2009-11-25T16:09:28ZIgor Ribeiro SucupiraIf you don't need the values that you store in the dict (in your
<br>example, you store [] and never use it), you can use a sets instead of
<br>a dict. Usage is a little bit simpler:
<br><br>-------------------------
<br>1> D = dict:store("_see._tcp.local", [], dict:new()).
<br>{dict,1,16,16,8,80,48,
<br> {[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[]},
<br> {{[],[],[],[],
<br> [["_see._tcp.local"]],
<br> [],[],[],[],[],[],[],[],[],[],[]}}}
<br>2> dict:find("_see._tcp.local", D).
<br>{ok,[]}
<br><br>3> S = sets:add_element("_see._tcp.local", sets:new()).
<br>{set,1,16,16,8,80,48,
<br> {[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[]},
<br> {{[],[],[],[],
<br> ["_see._tcp.local"],
<br> [],[],[],[],[],[],[],[],[],[],[]}}}
<br>4> sets:is_element("_see._tcp.local", S).
<br>true
<br>-------------------------
<br><br><br>See also gb_sets and ordsets.
<br><br>Igor.
<br><br>On Tue, Nov 24, 2009 at 7:25 PM, Jarrod Roberson <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26522575&i=0" target="_top" rel="nofollow">jarrod@...</a>> wrote:
<div class='shrinkable-quote'><br>> On Tue, Nov 24, 2009 at 3:18 PM, Jarrod Roberson <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26522575&i=1" target="_top" rel="nofollow">jarrod@...</a>>wrote:
<br>>
<br>>>
<br>>> process_dnsrec1(Sub,[#dns_rr{domain=Dom}|Rest]) ->
<br>>> case dict:find(Dom,Sub) of
<br>>> [Result] ->
<br>>> io:format("Interesting domain ~p=~p~n",[Dom,Result]);
<br>>>
<br>>
<br>> thanks for reading I figured it out by trial and error.
<br>> I replaced the [Result] with {ok,Result} and it started working as expected
</div><br><br><br>--
<br>"The secret of joy in work is contained in one word - excellence. To
<br>know how to do something well is to enjoy it." - Pearl S. Buck.
<br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26522541Re: A Generic API for controlling software components2009-11-25T16:06:44Z2009-11-25T16:06:44ZGarrett Smith-5On Wed, Nov 25, 2009 at 3:50 PM, Jayson Vantuyl <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26522541&i=0" target="_top" rel="nofollow">kagato@...</a>> wrote:
<br><br>> If you want to deprecate applications, that's fine, but understand that two packaging / distribution formats is a horrible idea. It took forever in Python to unify eggs and setuptools.
<br><br>I'd heartily second this. Python still doesn't have a unified
<br>packaging schema/toolset -- distutils and setuptools are still both in
<br>mainstream use, and it's a total pain.
<br><br>I've done a fair amount of work in package management systems in the
<br>commercial/proprietary work. I've never seen a packaging scheme that
<br>didn't have some pretty annoying warts. This tends to lead to package
<br>manager proliferation as it's very tempting to start anew on this
<br>common problem. Unfortunately, what initially looks like not-a-wheel
<br>is probably just another wheel.
<br><br>Unfortunately, I can only hand wave as I don't have a deep
<br>understanding of Erlang's current application/release scheme (though I
<br>have managed to used it :) I do think there's a reasonable burden to
<br>demonstrate why Erlang's application abstraction can't be evolved to
<br>support Python Egg or Ruby Gem like features. If the application
<br>scheme doesn't work, could application be morphed into components, or
<br>packages (also a common term for this)?
<br><br>Is there something from Faxien that gets us closer to Joe's goal?
<br><br><a href="http://code.google.com/p/faxien/" target="_top" rel="nofollow">http://code.google.com/p/faxien/</a><br><br>Garrett
<br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26522304Re: Erlang/OTP now at Github2009-11-25T15:40:03Z2009-11-25T15:40:03ZSteve Davis-5An event of significance -> mojombo has featured this on the GitHub
<br>main blog :)
<br><br><a href="http://github.com/blog/554-erlang-otp-now-on-github" target="_top" rel="nofollow">http://github.com/blog/554-erlang-otp-now-on-github</a><br><br>/s
<br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26521030Re: A Generic API for controlling software components2009-11-25T13:59:35Z2009-11-25T13:59:35ZRichard O'Keefe<br>On Nov 25, 2009, at 10:56 PM, Joe Armstrong wrote:
<br>> Rule4: All components C must have a file called
<br>>
<br>> $HOME/eComponents/C.ec/Preferences.pl
<br>>
<br>> The extension .pl means the file contains a property
<br>> list. Here is an example:
<br><br>We already have .pl meaning Prolog and .pl meaning Perl.
<br>Since the property list uses Erlang syntax, how about
<br>.epl (Erlang Property List)?
<br>>
<br>> Rule6: Code upgrade
<br>>
<br>> We should upgrade an component C when it's expiry date has
<br>> been reached. To update an component we delete the entire
<br>> component under $HOME/eComponents/C.ec we install the
<br>> new component and run the command: C:install().
<br><br>What happens if the expiry date is reached and there _isn't_ any
<br>new version, or the site the new version should be obtained from
<br>is unreachable?
<br>>
<br><br>There are many kinds of components.
<br>For example,
<br> - there should be exactly one instance
<br> - there should be at most one instance
<br> - there can be up to N instances to share work
<br> - there should be one instance per client
<br>...
<br>It isn't clear to me what range of component types this proposal
<br>is meant to cover.
<br><br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26520917Re: A Generic API for controlling software components2009-11-25T13:50:03Z2009-11-25T13:50:03ZJayson Vantuyl-2> I guess you mean OTP applications? - If so then I disagree. To start
<br>> with the directory structure within
<br>> an OTP application is fixed which I don't really like. Also there is
<br>It's fine that you don't like it, however, what use case justifies it. "Because I want to" is not really a reason. If you don't want to do it for a reason, it's probably bad design. No offense, really.
<br><br>Here's what I don't want. I don't want each component to have radically different layouts that require a ton of work to adapt to. I want contributing to projects and deploying them to be easy. Conventions solve this. Unless you have a problem that "rigid directory structures" prevent you from solving, that's just not good enough.
<br><br>> no construction rule
<br>> that says you are not allowed to write anything in the application
<br>> directory tree. I'd like to put the
<br>> entire component in a read-only area of disk for safety reasons (once
<br>> an initial install has been performed).
<br>This is a good idea. Separate the mutable data from code. This can be done perfectly well by convention, though.
<br><br>> I have a differnt proposal for reducing duplicates - this is a
<br>> different problem.
<br>If the problem is that deployment and installation is a hassle, I beg to differ. Part of the problem is that the core Erlang developers are often changing internal modules, so it is natural that their deployment system duplicates the entire system. For most of us, we just need to overlay our little modules on top of the giant Erlang environment. That's why I've been suggesting an overlay approach.
<br><br>> Yes to deploying Erlang components *and upgrading them*
<br>Applications are in modules and have versions. The upgrade case for Erlang applications is pretty much solid. Now, the way that releases do it (mutating an existing installation) is not exactly ideal, and I'd love to make adapt it to something smarter.
<br><br>> Sure. epkg etc. will be just a thin shell script layer over the API I suggested.
<br>> The CLI can be written as a thin layer over the API as well.
<br>I would welcome that. I think that a gen_event is a good model for handling runtime CLI functions.
<br><br>> because 90% is not enough
<br>Perhaps I wasn't clear. I was suggesting you start from 90% done instead of start from 0% done. Also, components and applications have enough conceptual overlap that it would only serve to be confusing.
<br><br>If you want to deprecate applications, that's fine, but understand that two packaging / distribution formats is a horrible idea. It took forever in Python to unify eggs and setuptools.
<br><br>> Of course. I just want to download yaws, ejabberd etc. drop them into
<br>> my eComponent Directory
<br>> and that's it - they are installed and runnable.
<br>No, you don't. :) A list of steps is not what you want. You want "installing components to be easy". Downloading a file and dropping it in can't run any code, can't make any decisions custom to your system, and can't autogenerate configuration. All of these things are great strengths of "gem install" and "easy_install". The last thing you want is to have a dozen different component downloads.
<br><br>For example, assume that RabbitMQ gets a bunch of C components that need building for three OSes. Now assume that it gets a special federated mode that requires different configuration. Next assume that it develops a multi-hosted version for hosting providers. If each combination has to be packaged separately (i.e. because we can't build the C extensions or mutate the configuration on install) then we end up with 12 (3*2*2) packages!
<br><br>Being devil's advocate here, let's say we do it your way and have "install code" that runs when you start it the first time we do a deployment. Even with this code, it has very weird behavior. The first time startup may take forever or fail if the extension fails to build. Now we have to keep track of that process and recover gracefully from it. It would have been far better to have had the "install" or "deploy" step fail.
<br><br>Basically, I don't see any value to the extra step. It should be "install" then "deploy", and install should be smart. If "install" is downloading a file and working with directories it's not smart.
<br><br>Ironically, it's also not really that beneficial to anyone in terms of user experience. Power users won't mind a single command in the shell. Non-power users would rather click an icon (moving files around for them is scary). It lands in a middle-ground that is probably less populated than you would think.
<br><br>> Ok, I didn't fully specify this - fine to change the details here or
<br>> use an environment variable to point
<br>> to the directory.
<br>I think unobtrusive default + environmental variable is good here.
<br><br>> This is the bit that is not enforced in OTP applications - I think
<br>> users are even encouraged to use the /priv
<br>> directory in an otp application
<br>Is there something about this that is hard to retrofit into applications? The great thing is that it's all abstracted already--just change what comes back from code:priv_dir/1. If people are doing it properly, their data should go where you want it to go.
<br><br>I'd really recommend having a cascading/overlaying/shadowing setup. Have everything search the deploy location, user location, and system location in that order. Mutable data never is found outside of the deploy.
<br><br>> Ok .eplist then?
<br>That sounds good.
<br><br>> Because I might not want to follow that particular convention. For
<br>> simple applications I usually put everything in one directory.
<br>> Actually this could be dropped, the system could scan the filesystem
<br>> to find the code paths
<br>> the first time you run the program.
<br>> directory
<br>One of the most misunderstood things about the Ruby community is their intolerance. Don't get me wrong, some of them are intolerant bigots, just like you get anywhere. However, a lot of the intolerance comes from a desire to have solid conventions. If you have to write applications all day long, knobs are only helpful if they're invisible. Every required parameter and every choice about where to put a directory is extra time before I have a working project and extra trouble when I come back to it six months later.
<br><br>Having the ability to override a convention is fine, but it should have a default and it should require no configuration.
<br><br>The scanning the filesystem part is a good one. One of the ugly things about Python, Java, Ruby, and Erlang is management of the code path. Java has it down with a set of mostly ugly conventions. Ruby still does a lot of manhandling (mostly generating stub files that know where the real code is). Python has, in my opinion, the best solution. Specifically, in the "system" directory, you can drop .pth files that point to additional code paths. This is fabulous in that it helps package managers (i.e. dpkg, rpm) plug in code in a manageable way. If Erlang were to have, for example, .epth files in /usr/lib/erlang/bin, that would make an awesome hook for distribution managers. Adding a .erlang directory (in the $HOME) with the same semantics would make it easy for users. It would be nice to move the cookie and hosts file into that directory, but I understand that might be asking too much too soon.
<br><br>> It's a hint to tell the package manager how often to check for updates
<br>> - I havn't thought through all the details
<br>> it could be something else:
<br>>
<br>> {checkForUpdates, everyTimeYouStart | dayly | hourly | weekly |
<br>> {after,Year,Month,Day} | {every, 10, minutes}}
<br>>
<br>> etc.
<br>Most system administration tasks are done rarely (i.e. running updates with the package manager, which this is a hint for). In this case, everybody else just downloads the current package list and compares it locally. I don't think that hints are all that useful in comparison. They can only generate false positives (expired but no update) and false negatives (not expired, but new update is out there).
<br><br>> The designer of the program knows what is a sensible value here
<br>Upgrades can trash data. It is not the designer's data. I don't think it takes more than blowing away the data in your RabbitMQ or losing your ejabberd user database to see why this could be extraordinarily bad on a large scale. Bugs happen. Best to let the administrator be in the loop.
<br><br>>> Again, I humbly suggest more traditional Unix pathnames. How about $HOME/.erlang/library/<component>/<vsn>/prefs.epl?
<br>>
<br>> No worries ...
<br>Thank you.
<br><br>> I guess the component framework would use the check for updates or
<br>> expiry date or whatever
<br>> to decide whether to do a check. The check would return a list of
<br>> improvements and the user would decide
<br>> whether or not to install them.
<br>Almost everything under the sun has an update command, but never does anything automatically. I really think it would be prudent. If you want to do "automatic updates", I would at least suggest that you have it turned off by default, and have it turned on by a project, not the user. The rationale is that the user of a component probably doesn't know enough about how the data is stored to keep it safe, but that the component developer should know.
<br><br>> I guess we should also be able to roll back a version (which is why I
<br>> have eLibrary/ComponentName/VSN/data ..
<br>> tags.
<br>Definitely. This is another reason that I suggested having a separate "deploy" step. You no longer have to worry about upgrading an installation. Each "version" is another deployment. In this scenario, you can specify "migrations" to upgrade/downgrade the data, but the code is managed as a separate entity.
<br><br>> It is pretty similar
<br>One is better than two. :)
<br><br><br>--
<br>Jayson Vantuyl
<br><a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26520917&i=0" target="_top" rel="nofollow">kagato@...</a>
<br><br><br><br><br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26520958Re: Erlang "object-oriented" after all?2009-11-25T13:49:11Z2009-11-25T13:49:11ZOlivier BoudevilleHi,
<br><br>This is surely a shameless plug, but, in terms of OOP with Erlang, one
<br>might give WOOPER a try
<br>(<a href="http://ceylan.sourceforge.net/main/documentation/wooper/" target="_top" rel="nofollow">http://ceylan.sourceforge.net/main/documentation/wooper/</a>), as it
<br>basically provides most OOP constructs in order to rely on concurrent
<br>instances in pure Erlang.
<br><br>Best regards,
<br><br>Olivier.
<br><br>Jachym Holecek a écrit :
<div class='shrinkable-quote'><br>> # Michael Turner 2009-11-24:
<br>>
<br>>> I ran across a very interesting exchange with Alan Kay, who most likely
<br>>> coined the term "object-oriented programming."
<br>>>
<br>>> <a href="http://userpage.fu-berlin.de/~ram/pub/pub_jf47ht81Ht/doc_kay_oop_en" target="_top" rel="nofollow">http://userpage.fu-berlin.de/~ram/pub/pub_jf47ht81Ht/doc_kay_oop_en</a><br>>>
<br>>> If you'll excuse some (only slightly tendentious) editing of his remarks:
<br>>>
<br>>> ----
<br>>> "I thought of objects being like biological cells and/or individual
<br>>> computers on a network, only able to communicate with messages . . . .
<br>>>
<br>>
<br>> No, you didn't. If you did, you would certainly have noticed that individual
<br>> cells/computers live concurrently and communicate asynchronously, which is not
<br>> how your objects behave.
<br>>
<br>> :-)
<br>>
<br>> SCNR, I still remember the disappointment of discovering (ages back) that
<br>> Objective-C objects didn't really fulfill the "they behave like real-world
<br>> objects" promise given by the (otherwise pretty good) NeXT book because
<br>> you couldn't "run objects in parallel" which sounded like something that
<br>> should obviously be possible.
<br>>
<br>> Regards,
<br>> -- Jachym
<br>>
<br>> ________________________________________________________________
<br>> erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>> erlang-questions (at) erlang.org
<br>>
<br>>
<br>>
<br>>
</div><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26519993Re: github and patch submission2009-11-25T12:44:54Z2009-11-25T12:44:54ZMax Lapshin-2For me, as maintainer of some packages on github, most preferred way is:
<br><br>1) someone forks repository
<br>2) makes branch
<br>3) push to the branch
<br>4) I add his repo as new origin
<br>5) fetch his branch to my local branch with same name
<br>6) merge with master
<br>7) push to my repo
<br>8) other developer fetches new master with his patches applied.
<br><br>It seems to be very convenient.
<br><br>________________________________________________________________
<br>erlang-patches mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-patches (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Patches-f14098.html" embed="fixTarget[14098]" target="_top" >Erlang Patches</a></p>tag:old.nabble.com,2006:post-26519165Re: github and patch submission2009-11-25T11:49:29Z2009-11-25T11:49:29ZBjörn GustavssonOn Wed, Nov 25, 2009 at 6:26 PM, Paul Oliver <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26519165&i=0" target="_top" rel="nofollow">puzza007@...</a>> wrote:
<br><br>> Do you have a preferred way of receiving patches now that the code is
<br>> mirrored on github? Is this in a readme somewhere that I've missed?
<br><br>We have not written a readme about patch submission yet.
<br><br>But am I pretty sure that the recommendation for sending patches
<br>will be send a reference to a branch to a git repository that we can
<br>pull the patch from.
<br><br>We have some ideas of how we will handle the patches, but we
<br>haven't worked out all the details yet. As we work out the details,
<br>we will add more wiki pages to the wiki for erlang/otp at github.
<br><br>--
<br>Björn Gustavsson, Erlang/OTP, Ericsson AB
<br><br>________________________________________________________________
<br>erlang-patches mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-patches (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Patches-f14098.html" embed="fixTarget[14098]" target="_top" >Erlang Patches</a></p>tag:old.nabble.com,2006:post-26516876github and patch submission2009-11-25T09:26:04Z2009-11-25T09:26:04Zpuzza007Hi OTP guys,
<br><br>Do you have a preferred way of receiving patches now that the code is
<br>mirrored on github? Is this in a readme somewhere that I've missed?
<br><br>Thanks!
<br>Paul.
<br><br>________________________________________________________________
<br>erlang-patches mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-patches (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Patches-f14098.html" embed="fixTarget[14098]" target="_top" >Erlang Patches</a></p>tag:old.nabble.com,2006:post-26517003Re: Question about erlang.log2009-11-25T09:24:29Z2009-11-25T09:24:29ZRob Charlton-3Wael Ebrahim wrote:
<div class='shrinkable-quote'><br>> I have a question about Erlang log.
<br>>
<br>> I have a target system and I want to increase the size and number of log
<br>> files named erlang.log.1 ....erlang.log.5 in the directory ROOT_DIR/log/
<br>>
<br>>
<br>> The default values are 5 files each one is 100K , but I had a very big
<br>> crash that was repeated multiple times causing these files to be
<br>> overwritten, and I couldn't reach its start.
<br>>
<br>> I know I can use sasl for this kind of monitoring, but it doesn't log
<br>> the user input on the erlang shell as the erlang.log.x does.
<br>> Also sasl doesn't log any output except from standard applications, or
<br>> error_logger.
<br>>
<br>> Any ideas about increasing size of these files "erlang.log.x" ???
<br>>
<br>> Thanks in advance,
<br>>
<br>> Wael Ebrahim
<br>>
<br>>
<br>>
</div>Before starting run_erl, you can set these environment variables:
<br><br>export RUN_ERL_LOG_GENERATIONS=10
<br>export RUN_ERL_LOG_MAXSIZE=1000000
<br><br>see <a href="http://www.erlang.org/doc/man/run_erl.html" target="_top" rel="nofollow">http://www.erlang.org/doc/man/run_erl.html</a> for more details
<br><br>Cheers
<br><br>Rob
<br><br>--
<br>Erlang Training and Consulting Ltd
<br>www.erlang-consulting.com
<br><br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26515384Re: Erlang/OTP now at Github2009-11-25T08:00:46Z2009-11-25T08:00:46ZBjörn GustavssonOn Wed, Nov 25, 2009 at 3:20 PM, Juan Jose Comellas <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26515384&i=0" target="_top" rel="nofollow">juanjo@...</a>> wrote:
<br>> Why was the commit history discarded? Wouldn't it be better to at
<br>> least preserve the history corresponding to the public releases? Maybe
<br>> you could use Matthew Foemmel's repository[1] in Github as a base.
<br><br>Including the history would require approximately 300 Mb.
<br><br>However, we will probably provide an *optional* Erlang/OTP
<br>history that can be added using the new replace mechanism in
<br>git 1.6.5.
<br><br>--
<br>Björn Gustavsson, Erlang/OTP, Ericsson AB
<br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26513833Re: Erlang/OTP R13B03 has been released2009-11-25T06:30:37Z2009-11-25T06:30:37ZzambalHi,
<br><br>Thanks a lot for another OTP release!
<br><br>I just wanted to say that the links to the torrent files are not
<br>correct. The correct links should be:
<br><br><a href="http://www.erlang.org/download/torrents/otp_src_R13B03.tar.gz.torrent" target="_top" rel="nofollow">http://www.erlang.org/download/torrents/otp_src_R13B03.tar.gz.torrent</a><br><a href="http://www.erlang.org/download/torrents/otp_win32_R13B03.exe.torrent" target="_top" rel="nofollow">http://www.erlang.org/download/torrents/otp_win32_R13B03.exe.torrent</a><br><br>-
<br>vincent
<br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26513772Question about erlang.log2009-11-25T06:21:27Z2009-11-25T06:21:27ZWael EbrahimI have a question about Erlang log.
<br>
<br>I have a target system and I want to increase the size and number of log
<br>files named erlang.log.1 ....erlang.log.5 in the directory ROOT_DIR/log/
<br><br>
<br>The default values are 5 files each one is 100K , but I had a very big
<br>crash that was repeated multiple times causing these files to be
<br>overwritten, and I couldn't reach its start.
<br>
<br>I know I can use sasl for this kind of monitoring, but it doesn't log
<br>the user input on the erlang shell as the erlang.log.x does.
<br>Also sasl doesn't log any output except from standard applications, or
<br>error_logger.
<br>
<br>Any ideas about increasing size of these files "erlang.log.x" ???
<br>
<br>Thanks in advance,
<br><br>Wael Ebrahim
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26513702Re: Erlang/OTP now at Github2009-11-25T06:20:14Z2009-11-25T06:20:14ZJuan Jose Comellas-4Why was the commit history discarded? Wouldn't it be better to at
<br>least preserve the history corresponding to the public releases? Maybe
<br>you could use Matthew Foemmel's repository[1] in Github as a base.
<br><br>[1] <a href="http://github.com/mfoemmel/erlang-otp/" target="_top" rel="nofollow">http://github.com/mfoemmel/erlang-otp/</a><br><br><br>2009/11/25 Björn Gustavsson <<a href="http://old.nabble.com/user/SendEmail.jtp?type=post&post=26513702&i=0" target="_top" rel="nofollow">bgustavsson@...</a>>
<div class='shrinkable-quote'><br>>
<br>> The official git repository for Erlang/OTP can now be found at Github:
<br>>
<br>> <a href="http://github.com/erlang/otp" target="_top" rel="nofollow">http://github.com/erlang/otp</a><br>>
<br>> Build instructions can be found at:
<br>>
<br>> <a href="http://wiki.github.com/erlang/otp" target="_top" rel="nofollow">http://wiki.github.com/erlang/otp</a><br>>
<br>> We plan to add more wiki pages with additional information in the
<br>> near future.
<br>>
<br>> --
<br>> Björn Gustavsson, Erlang/OTP, Ericsson AB
<br>>
<br>> ________________________________________________________________
<br>> erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>> erlang-questions (at) erlang.org
<br>>
</div><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26513562Re: Erlang "object-oriented" after all?2009-11-25T06:14:06Z2009-11-25T06:14:06ZJachym Holecek-3# Michael Turner 2009-11-24:
<div class='shrinkable-quote'><br>>
<br>> I ran across a very interesting exchange with Alan Kay, who most likely
<br>> coined the term "object-oriented programming."
<br>>
<br>> <a href="http://userpage.fu-berlin.de/~ram/pub/pub_jf47ht81Ht/doc_kay_oop_en" target="_top" rel="nofollow">http://userpage.fu-berlin.de/~ram/pub/pub_jf47ht81Ht/doc_kay_oop_en</a><br>>
<br>> If you'll excuse some (only slightly tendentious) editing of his remarks:
<br>>
<br>> ----
<br>> "I thought of objects being like biological cells and/or individual
<br>> computers on a network, only able to communicate with messages . . . .
</div><br>No, you didn't. If you did, you would certainly have noticed that individual
<br>cells/computers live concurrently and communicate asynchronously, which is not
<br>how your objects behave.
<br><br>:-)
<br><br>SCNR, I still remember the disappointment of discovering (ages back) that
<br>Objective-C objects didn't really fulfill the "they behave like real-world
<br>objects" promise given by the (otherwise pretty good) NeXT book because
<br>you couldn't "run objects in parallel" which sounded like something that
<br>should obviously be possible.
<br><br>Regards,
<br> -- Jachym
<br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>tag:old.nabble.com,2006:post-26513316Erlang/OTP now at Github2009-11-25T06:01:24Z2009-11-25T06:01:24ZBjörn GustavssonThe official git repository for Erlang/OTP can now be found at Github:
<br><br><a href="http://github.com/erlang/otp" target="_top" rel="nofollow">http://github.com/erlang/otp</a><br><br>Build instructions can be found at:
<br><br><a href="http://wiki.github.com/erlang/otp" target="_top" rel="nofollow">http://wiki.github.com/erlang/otp</a><br><br>We plan to add more wiki pages with additional information in the
<br>near future.
<br><br>--
<br>Björn Gustavsson, Erlang/OTP, Ericsson AB
<br><br>________________________________________________________________
<br>erlang-questions mailing list. See <a href="http://www.erlang.org/faq.html" target="_top" rel="nofollow">http://www.erlang.org/faq.html</a><br>erlang-questions (at) erlang.org
<br><br><p>From forum: <a href="http://old.nabble.com/Erlang-Questions-f14096.html" embed="fixTarget[14096]" target="_top" >Erlang Questions</a></p>