<html><body bgcolor="#FFFFFF"><div>Yes a little unfortunate but very portable.<br><br> - Jay (phone<span class="Apple-style-span" style="-webkit-composition-fill-color: rgba(175, 192, 227, 0.231373); -webkit-composition-frame-color: rgba(77, 128, 180, 0.231373); ">)</span></div><div><br>On May 19, 2009, at 10:27 AM, Dragiša Durić <<a href="mailto:dragisha@m3w.org">dragisha@m3w.org</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>
VARIABLES?<br>
<br>
Now every1 who was using CASE with error results has to adapt one's code?<br>
<br>
What is rationale here? Portability?<br>
<br>
TIA!<br>
<br>
INTERFACE Uerror;<br>
<br>
FROM Ctypes IMPORT int;<br>
<br>
(* CONST *)<br>
<*EXTERNAL "Uerror__EACCES"*> VAR EACCES: int;<br>
<*EXTERNAL "Uerror__EADDRINUSE"*> VAR EADDRINUSE: int;<br>
<*EXTERNAL "Uerror__EADDRNOTAVAIL"*> VAR EADDRNOTAVAIL: int;<br>
<*EXTERNAL "Uerror__EAGAIN"*> VAR EAGAIN: int;<br>
<br>
<br>
<table cellspacing="0" cellpadding="0" width="100%">
<tbody><tr>
<td>
-- <br>
Dragiša Durić <<a href="mailto:dragisha@m3w.org"><a href="mailto:dragisha@m3w.org">dragisha@m3w.org</a></a>>
</td>
</tr>
</tbody></table>
</div></blockquote></body></html>