<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE message PUBLIC
  "-//MLarc//DTD MLarc output files//EN"
  "../../mlarc.dtd"[
  <!ATTLIST message
    listname CDATA #REQUIRED
    title CDATA #REQUIRED
  >
]>

  <?xml-stylesheet href="../../mlarc.xsl" type="text/xsl"?>


<message 
  url="2003/11/76bfb2b8df6616335e079e0acbffab67"
  from="Dustin Sallings &lt;dustin@s...&gt;"
  author="Dustin Sallings"
  date="2003-11-19T06:09:01"
  subject="Re: [Caml-list] tail call optimization"
  prev="2003/11/74fd6d12b051517ef4b87994851705ad"
  next="2003/11/cfdde01e96dd3fcc2e53c6be05b8a419"
  prev-in-thread="2003/11/b3024c61f50d75b522f680a905aa2286"
  prev-thread="2003/11/f112840855ba7fadd40cd35228f1ee0a"
  next-thread="2003/11/222e3da9e074f94c1e735e19b5df6c54"
  root="../../"
  period="month"
  listname="caml-list"
  title="Archives of the Caml mailing list">

<thread subject="[Caml-list] tail call optimization">
<msg 
  url="2003/11/1f551b7bf53f76d0b573b176d6687798"
  from="Dustin Sallings &lt;dustin@s...&gt;"
  author="Dustin Sallings"
  date="2003-11-19T05:24:17"
  subject="[Caml-list] tail call optimization">
<msg 
  url="2003/11/74fd6d12b051517ef4b87994851705ad"
  from="Brian Hurt &lt;bhurt@s...&gt;"
  author="Brian Hurt"
  date="2003-11-19T05:52:29"
  subject="Re: [Caml-list] tail call optimization">
<msg 
  url="2003/11/cfdde01e96dd3fcc2e53c6be05b8a419"
  from="Dustin Sallings &lt;dustin@s...&gt;"
  author="Dustin Sallings"
  date="2003-11-19T06:24:25"
  subject="Re: [Caml-list] tail call optimization">
<msg 
  url="2003/11/27534b11b64fdea5311fde54c963c9c3"
  from="Frederic van der Plancke &lt;fvdp@d...&gt;"
  author="Frederic van der Plancke"
  date="2003-11-19T11:38:54"
  subject="Re: [Caml-list] tail call optimization">
</msg>
<msg 
  url="2003/11/030cefc60478232c72d1ae302af3e813"
  from="Brian Hurt &lt;bhurt@s...&gt;"
  author="Brian Hurt"
  date="2003-11-19T16:24:34"
  subject="Re: [Caml-list] tail call optimization">
<msg 
  url="2003/11/b3024c61f50d75b522f680a905aa2286"
  from="Dustin Sallings &lt;dustin@s...&gt;"
  author="Dustin Sallings"
  date="2003-11-19T17:46:34"
  subject="Re: [Caml-list] tail call optimization">
</msg>
</msg>
</msg>
</msg>
<msg 
  url="2003/11/76bfb2b8df6616335e079e0acbffab67"
  from="Dustin Sallings &lt;dustin@s...&gt;"
  author="Dustin Sallings"
  date="2003-11-19T06:09:01"
  subject="Re: [Caml-list] tail call optimization">
</msg>
</msg>
</thread>

<contents>

On Nov 18, 2003, at 21:40, Aleksey Nogin wrote:

&gt; On 18.11.2003 21:24, Dustin Sallings wrote:
&gt;
&gt;&gt;     Specifically, I've got an ``iter_lines'' function I'd like to 
&gt;&gt; turn into a ``fold_lines'' function that looks something like this (a 
&gt;&gt; few different functions for different things):
&gt;&gt; let rec fold_lines f init_value ch =
&gt;&gt;     try
&gt;&gt;         let v = f (input_line ch) init_value in
&gt;&gt;         fold_lines f v ch
&gt;&gt;     with End_of_file -&gt; init_value;
&gt;
&gt; My guess is that because the recursive call is inside the "try", the 
&gt; function is not really tail recursive.
&gt;
&gt; May be the following will work:
&gt;
&gt; let rec fold_lines f init_value ch =
&gt;    match
&gt;       try
&gt;          Some (f (input_line ch) init_value)
&gt;       with End_of_file -&gt; None
&gt;    with
&gt;       Some v -&gt; fold_lines f v ch
&gt;     | None -&gt; init_value

	Well, this does work, but I don't really like it.  How expensive is 
the match?  It seems to me that the try call shouldn't be relevant 
since the return value comes from the bottom of it.

--
SPY                      My girlfriend asked me which one I like better.
pub  1024/3CAE01D5 1994/11/03 Dustin Sallings &lt;dustin@spy.net&gt;
|    Key fingerprint =  87 02 57 08 02 D0 DA D6  C8 0F 3E 65 51 98 D8 BE
L_______________________ I hope the answer won't upset her. ____________

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners

</contents>

</message>

