Close Topic Options

Welcome to winasm.net, Gerome

Thanks for the info, you could even try to develop the FBSL language in Assembly. The advantages are obvious.

Regards,

Antonis

Hello Antonis,

Thanks for the welcome
BTW, FBSL already has a part developped in ASM : its APICALL engine part wich is capable of loading / calling any DLL (cdecl, stdcall ones) on the fly without precising its parameters types nor prototypes !

example :
Apicall( "MessageBoxA", "user32", Null, "Hello", "Title", MB_OK )

Kinda magic ?

Yours,
Gerome GUILLEMIN
http://www.fbsl.net

Not exaclty magic, but nice!

BTW, why don't you submit your site to the Programming Tools directory at http://protools.winasm.net so that more people learn about it?

Regards

Thanks for the invitation Antonis,

Gerome didn't do it at the time for some unknown reason but I gladly will.

TheWatcher
a.k.a. Mike Lobanovsky

PS: Oh sorry Antonis, I can't do that just now because I don't dare change the website code itself for the sake of a reciprocal link. I'd love to provide a link to this site/domain in our "Other Links" section in exchange but no automatic googlified links, sorry. Just being on the safe side, you know.

I played a little with Tiny C Compiler (TCC) and I did a stripped version for Windows XP (my current OS). No configure. No make file. Just the source + tcc.exe + build.bat.

The batch script (build.bat) does the following:
- generates the libtcc1.a from the source files using tcc.exe
- generates tcc1.exe from the source files using tcc.exe
- generates tcc2.exe from the source files using tcc1.exe
tcc1.exe and tcc2.exe should be identical!
They are YOUR new version of Tiny C compiler.

ar.exe - archiver for the object files generated from the source code
libtcc1.c -> libtcc1.o -> ar.exe ->libtcc1.a

Archive too big!
http://www.esnips.com/doc/678404c7-1da8-4dc5-a06d-1d0fe1527bf7/tcc-0.9.25_bin_src_win32