Page 2 of 2
Posted: Tue Sep 27, 2005 5:17 pm
by traumatic
Posted: Wed Sep 28, 2005 12:40 am
by va!n
@FloHimself:
Thanks for sharing this great tip/trick
@traumatic:
thanks for sharing! very nice work! respect!
@all people:
first i had some problems to get the code work but after some time i managed to get it work... so i have create a small example package including most required files for for the V2M replayer... (due fact of copyright and licence issue, i dont added any V2M related stuff to the package... you have to download it seperate!)
1. download the archive
2. copy the modded FASM to your PureBasic/Compilers directroy
3. copy the contest of Example/ from archive to C:\LinkStuff\
4. Download the libv2 package at:
http://1337haxorz.de/products.html
5. Unpack the LibV2M package and copy "libv2.lib" to your C:\LinkStuff\ folder!
6. Load the Example file and try to comile... should work...!?
here you can download the package:
www.superfilm.tv/LinkStuff.zip
Posted: Wed Oct 05, 2005 8:17 pm
by FloHimself
(CallFunctionFast() adds 1.5kb! )
you can use the invoke macro instead PUSHing arguments to stack and
using CALL. just copy the PROC32.INC include file from fasm
distribution to the purebasic compilers directory.
then you can replace:
Code: Select all
!PUSH dword [v_hwnd]
!PUSH dword [v_tuneadr]
!CALL [v_ssInit]
with something like this:
Code: Select all
!include 'PROC32.INC'
RequesterTitle$ = "FASM Macro Test"
RequesterText$ = "I was invoked."
Procedure MyMessageRequester(Title$, Text$)
ProcedureReturn MessageRequester(Title$, Text$)
EndProcedure
*MyReq = @MyMessageRequester()
!invoke p_MyReq, [v_RequesterTitle$], [v_RequesterText$]
Posted: Wed Oct 05, 2005 11:37 pm
by okasvi
again something useful
Posted: Thu Oct 06, 2005 5:00 am
by NoahPhense
This just reminds me how little I know about programming..
- np
Posted: Thu Oct 06, 2005 8:32 am
by Psychophanta
Hi FloHimself, great to know it.
And great that PB allows FASM directly
If we include 'PROC32.INC', the final executable will get bigger size than using PUSHes and CALL ? or not?
Posted: Thu Oct 06, 2005 6:53 pm
by FloHimself
Psychophanta wrote:If we include 'PROC32.INC', the final executable will get bigger size than using PUSHes and CALL ? or not?
the .exe won't get bigger in size. fasm's macro processor is replaceing
the "macro commands" with the "content of the macro".
so fasm will replace any:
Code: Select all
!invoke v_ssInit, [v_tuneadr], [v_hwnd]
with (not literally):
Code: Select all
!PUSH dword [v_hwnd]
!PUSH dword [v_tuneadr]
!CALL [v_ssInit]