Re: Windows IO lib

[The Doctor <the_doctor@...>]

I don't know enough about programming to follow that easily, but I'm trying. :)
It seems to mean that the main Lua executable has this extra code that makes writing functions easy, whereas it might be desirable to use system calls to bypass that for speed or size reduction in finished code. If this is right, it makes sense in a way, but if Lua contains the stuff I used in the manual, and it is a core part of Lua, it seems that this might be taking reductionism to the point where it seems odd to go to such lengths to undercut Lua after taking the time to build/use it. Or is this basically a way to bypass the usual layers that seperate the user's program from the hardware?



Rob Kendrick <lua-l@nun.org.uk> wrote:
(31/08/2004 23:30)

>
>For a very very minimal footprint, using the FILE* operations in the libc 
>means you have to use the libc.  Using direct system calls means you don't, so 
>you can use a smaller runtime library.  Under UNIX for example, some small 
>bindings to open/read/write/close will be many times smaller than bindings to 
>fopen/fscanf/fprintf/fclose and the required support code, for example.
>
>-- 
>Rob Kendrick, Pepperfish Ltd.         +44 (0)845 226 4146  www.pepperfish.net
>PGP signed or encrypted mail welcome                         Key ID: 3651D17A