Re: [fpc-devel]Minor differences with Delphi

2003-11-08 Thread Johannes Berg
On Fri, 2003-11-07 at 12:55, David Butler wrote: Sorry, I should have guessed. Yes, it basically takes the OS error and raises some exception. The exception message is the OS error message as returned by an OS function call. Here's a basic implementation that works for me (*): const

Re: [fpc-devel]Minor differences with Delphi

2003-11-08 Thread Marco van de Voort
On Fri, 2003-11-07 at 12:55, David Butler wrote: Sorry, I should have guessed. Yes, it basically takes the OS error and raises some exception. The exception message is the OS error message as returned by an OS function call. Here's a basic implementation that works for me (*): const

Re: [fpc-devel]Minor differences with Delphi

2003-11-08 Thread Johannes Berg
On Sat, 2003-11-08 at 12:41, Johannes Berg wrote: Here's a basic implementation that works for me (*): And before someone complains about Delphi compatibility: type EOSError = class(Exception) protected FErrorCode: Integer; public property ErrorCode: Integer read FErrorCode;

Re: [fpc-devel]Minor differences with Delphi

2003-11-07 Thread David Butler
On Fri, 7 Nov 2003 09:15:17 +0100 (CET), you wrote: I had a look at Kylix's RaiseLastOSError function. It uses GetLastError which calls '__errno_location' from 'libc.so.6'. On Windows this uses the GetLastError WinAPI call. This is Delphi's implementation for RaiseLastOSError: [/me pinches

Re: [fpc-devel]Minor differences with Delphi

2003-11-06 Thread David Butler
On Thu, 6 Nov 2003 23:31:27 +0100 (CET), you wrote: * Minor difference with Delphi units: * RaiseLastOSError is not defined in SysUtils. What is it supposed to do, specifically on non windows, or should it be windows only? I had a look at Kylix's RaiseLastOSError function. It uses