Displaying 3 results from an estimated 3 matches for "throwoserror".
Did you mean:
throwerror
2004 Sep 14
0
[LLVMdev] Files to lib/System/Win32
On Mon, 13 Sep 2004 20:54:57 -0700
Reid Spencer <reid at x10sys.com> wrote:
> On the other hand, no one has submitted any Win32 patches yet, so first
> come first served :)
>
> Reid.
Consider this a down payment :) The Win32 version of Memory.cpp attached.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Memory.cpp
Type:
2004 Sep 14
4
[LLVMdev] Files to lib/System/Win32
Yes, it should. I haven't reviewed Henrik's change set yet but if it
doesn't look like clean Win32 code then I will create a separate target
named MingW and adjust the configure script accordingly.
On the other hand, no one has submitted any Win32 patches yet, so first
come first served :)
Reid.
On Mon, 2004-09-13 at 19:35, Jeff Cohen wrote:
> Uh... shouldn't a Win32 port use
2004 Sep 14
3
[LLVMdev] Files to lib/System/Win32
...ersion of Memory.cpp attached.
On further reflection, I think we need to abstract the operation of
throwing a formatted OS error message. This is done in many places, and
the Windows way of doing it differs substantially from Unix. Basically
take the ThrowError function and turn it into Process::ThrowOSError or
something like that.