@Shannara: sorry, I don't even have Linux installed, my knowledge about Linux is very near 0. But anybody can try to port it, the core is mostly made of string operations.
@Iria:
1) Where do I declare variables, inside the procedures outside?
Like in PureBasic. Globals outside (declare, NOT use), shared and locals inside, etc.
2) Where do I do declares, strucutrues, enumerations
Wherever, like in PureBasic.
3) I guess a tutorial would sort most of these issues out
I wanted to avoid that... XD I must first finish the CGI and SQLite libs, we'll see then.
4) Are the lib procedure variable argument names used as the Japbe in editor help (at the bottom)...
I don't know. But here's a little example of a variable arguments function:
Code: Select all
ProdedureDLL MyFunction(arg1.s, arg2.f) ; This comment will be the PB IDE help line, don't know for japbe.
; Do whatever
EndProcedure
ProdedureDLL MyFunction2(arg1.s, arg2.f, arg3.b)
; Do whatever
EndProcedure
ProdedureDLL MyFunction3(arg1.s, arg2.f, arg3.b, arg4.s, arg5.l)
; Do whatever
EndProcedure
After TailBiting this, the PB IDE status bar will show:
Code: Select all
MyFunction(arg1.s, arg2.f, [arg3.b, [arg4.s, arg5.l]]) - This comment will be the PB IDE help line, don't know for japbe.
I hope this helps you. If there's anything I can do to make it more Japbe compatible, just tell me.
Ive been through all your example code and it seems to me that I would write a lib exactly like I would write a DLL, is that simply the case? Or are there any rules I need to be aware of?
It's all it the help file, but mostly, yes (but you don't use AttachProcess(), etc.)