|Builtin Interpretation email@example.com (Philip Herron) (2009-04-29)|
|Re: Builtin Interpretation firstname.lastname@example.org (BartC) (2009-05-03)|
|Re: Builtin Interpretation email@example.com (Philip Herron) (2009-05-05)|
|Re: Builtin Interpretation firstname.lastname@example.org (cr88192) (2009-05-06)|
|From:||Philip Herron <email@example.com>|
|Date:||Tue, 5 May 2009 10:16:06 +0100|
|Posted-Date:||05 May 2009 10:49:55 EDT|
BartC <firstname.lastname@example.org> wrote in message
> In one of my interpreted languages, these declarations look like:
> library "crtdll"
> clang function fopen (istring,istring)int
> library "kernel32"
> windows function DeleteFileA <erasefile> (istring)int
> (istring means something like char*, and maybe that library should be
This is a nice idea of doing it, i was thinking of maby having some
kind of __builtin__fopen() or somthing, but i think if i do what you
do, as in loadlib and it has a subset of functions i know as builtins
works a little better.
Was something bugging me and did really know which is the nicest way
of doing this.
Return to the
Search the comp.compilers archives again.