On Thu, Jun 18, 2009 at 4:34 AM, Matthew Fluet <span dir="ltr"><<a href="mailto:fluet@tti-c.org">fluet@tti-c.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
MLton.Process.create (on Cygwin) has used cygwin_conv_to_full_win32_path since your 20041202 patch</blockquote><div><br>Oh. :) From your examples I thought it was using windows paths, not cygwin.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
But, I'm not convinced that it is worth it.</blockquote><div><br>That's a reasonable position. The whole useWindowsProcess was implemented AFAIK because we were using VirtualAlloc instead of mmap. At this pointis there still any advantage to using VitrualAlloc? Use-mmap seems to work quite reliably. It might be reasonable to just use fork()/exec() for Process.create and eliminate the native memory management for cygwin.<br>
</div></div><br>