XProfan

- Page 24 -

« this Posting watts as Solution marked. »

- Page 15 -

Jens-Arne
Reumschüssel

there's a new Version, The differently with the internen Messagehandling bypassing. Please probier The time from. Perhaps is the trouble so fixed.

XProfan X4
XProfan X4 * Prf2Cpp * XPSE * JRPC3 * Win11 Pro 64bit * PC i7-7700K@4,2GHz, 32 GB RAM
PM: jreumsc@web.de

09/24/22 ▲

Walter

OK!
have 0 reingeschrieben - and it's running!
These DLL have I on the Erzeuger-Homepage www.paehl.de/ neither More found.
there tappt im dunkeln but well functions, set I tappt im dunkeln furthermore one.
Thank you!

05/23/23 ▲

Jens-Arne
Reumschüssel

Probier time this small Program from:

Compile Mark Separation


{$NoExternal2CallConversion}
{$NoDef2ExternalConversion}
{$SetFbDllName Test_fbprocs}

DEF fbTestProc2(1) !"Test_fbprocs.dll","FBTESTPROC@4"

fbPROC fbTestProc(byval i as integer) as integer export
  return i
ENDPROC

cls
print "Direktaufruf: "+@st$(fbTestProc(chr$(0)))
print "via External: "+@st$(@external("Test_fbprocs.dll","FBTESTPROC@4",chr$(0)))
print "via Call: "+@st$(@call(@GetFbProcAddr("fbTestProc"),chr$(0)))
print "via DEF: "+@st$(@fbTestProc2(chr$(0)))
waitinput
end

on it becomes clear, that any Funktionsaufruf-modes always correctly to internal Typumwandlung The address one Strings transfer, the chr$(0) contains, only DEF not. DEF commit unkorrekt 0.

XProfan X4 * Prf2Cpp * XPSE * JRPC3 * Win11 Pro 64bit * PC i7-7700K@4,2GHz, 32 GB RAM
PM: jreumsc@web.de

05/23/23 ▲

Walter

mean you the fully!

try goes but not, there itself the thing in the Präcompiler on never see again dismisses.

need I moreover The Test_fbprocs.dll?

bild_2023-05-25_175200090.png	25 kB

Hochgeladen:	05/25/23

Downloadcounter:
		Download

05/25/23 ▲

Jens-Arne
Reumschüssel

means this is strange. I can the free from problems started, too with "<Tilde><Tilde>temp<Tilde><Tilde>.prf" as Dateiname. therefore again The admittedly something hilflose question: have You The neuste Version of JRPC3 using? otherwise know I do not, Why the lying could. and the File Test_fbprocs.dll becomes Yes straight first by the Program created, The must You means not before having.

XProfan X4 * Prf2Cpp * XPSE * JRPC3 * Win11 Pro 64bit * PC i7-7700K@4,2GHz, 32 GB RAM
PM: jreumsc@web.de

05/27/23 ▲

Walter

Sooooo ... geschafft.

trouble was probably, I The Source not stored having (?).
anyway is it to the Save now run - what about me see the Result!

now must I yet with freebasic keep busy, circa too Own DLLs produce to!

still same The next question

: Why becomes at call-appeal one other i zurückgegeben as at Direktaufruf and at external?
ought to still the worth same Adresse his?

bild_2023-05-27_174524520.png	4 kB

Hochgeladen:	05/27/23

Downloadcounter:
		Download

05/27/23 ▲

Jens-Arne
Reumschüssel

No, this is the ploy thereby: with eachone Übergabe of chr$(0) becomes of XProfan intern one new String created and which address transfer. directly to returns the DLL-function becomes the String with safety immediate again released. therefore has eachone appeal another, casually String-address.

this is even with XProfan-Strings self the case. each time, if you one String a new Content zuweist (even if it derselbe is How before), standing the String thereafter at a integrally others Speicheradresse. Intern becomes Yes always very so plenty memory angefordert, How for length the Strings necessary is. and there these length variable is, becomes the with eachone Zuweisung new undertaken. therefore is the works with übergebenen Strings in fb-/pbPROCs so tricky, because the Speicheradresse of Strings variable is, in the Contrast to Speicheradresse of z.B. Integer-variables.

example:

Compile Mark Separation

declare s$
cls
s$="123"
print @addr(s$)
s$="123"
print @addr(s$)
waitinput
end

XProfan X4 * Prf2Cpp * XPSE * JRPC3 * Win11 Pro 64bit * PC i7-7700K@4,2GHz, 32 GB RAM
PM: jreumsc@web.de

05/28/23 ▲

Jens-Arne
Reumschüssel

Version 9.17a available:

{$WrapDlls} introduced. so go The of fb-/pbPROCs begot DLLs directly in The XProfan-Exe-File integrate, so tappt im dunkeln not any more included go must. See Help-File To Kompilerdirektiven --> {$WrapDlls}.

best Regards, Jens-Arne

XProfan X4
XProfan X4 * Prf2Cpp * XPSE * JRPC3 * Win11 Pro 64bit * PC i7-7700K@4,2GHz, 32 GB RAM
PM: jreumsc@web.de

05/28/23 ▲

Walter

OK, thanks for Statement!

05/28/23 ▲

funkheld

goes the Please too for Purebasic?

Thank you.
greeting

XProfan 11

05/30/23 ▲

Jens-Arne
Reumschüssel

Hello funkheld,

Yes. one can even FreeBasic and PureBasic next to each other using, if one would like. then go with {$WrapDlls} both DLLs into Profan-Program installed.

XProfan X4
XProfan X4 * Prf2Cpp * XPSE * JRPC3 * Win11 Pro 64bit * PC i7-7700K@4,2GHz, 32 GB RAM
PM: jreumsc@web.de

05/31/23 ▲

Jens-Arne
Reumschüssel

V9.26:
pbPROCs with spare wählbaren Rückgabetypen installed

Deklarationsbeispiel: pbPROC ProcName.s() for a String as Return Value

The Typangabe comes means to the Prozedurnamen, not to "pbPROC", as in reinem PureBasic normally would [Procedure.s ProcName()].

ACHTUNG: From Integer abweichende Rückgabetypen can not pbPROCs uses go, The of XProfan-Program called go, there Rückgabewerte of DLL-Procedures ans Hauptprogramm always 4 Bytes wide his must. Very well but in "Hilfs-pbPROCs", The only of others pbPROCs called go.

Accurate said can with extern verwendeten functions no Rückgabetypen using go, The not four Bytes occupy. Single (.f in PureBasic) would means thoroughly weg. but the are delicacies.

with fbPROCs was everything no large trouble, there in FreeBasic The Rückgabetypdefinition with As ... to the Parameterklammer comes. for pbPROCs had but a Special spelling for since.

Greeting, Jens-Arne

XProfan X4 * Prf2Cpp * XPSE * JRPC3 * Win11 Pro 64bit * PC i7-7700K@4,2GHz, 32 GB RAM
PM: jreumsc@web.de

06/12/23 ▲

Jens-Arne
Reumschüssel

V9.31a:
it can now arbitrary DLLs directly in The XProfan-EXE integrate go. For this, is {$WrapDll <DLL-Name>} To use. The DLL-File must then not any more included go.

these though only relatively small DLLs meaningfully, because otherwise The Ladezeit the XProfan-Program To big go would. If one but z.B. prfdat32.dll integrate would like, then is these function perfect for suitable.

{$WrapDll ...} works How ImportDll(). The functions the DLL can means directly in the code uses go. One appeal over @external() remaining but ditto possible. Both becomes of JRPC3 in speedy @call()-Aufrufe verwandelt.

Greeting, Jens-Arne

XProfan X4 * Prf2Cpp * XPSE * JRPC3 * Win11 Pro 64bit * PC i7-7700K@4,2GHz, 32 GB RAM
PM: jreumsc@web.de

06/14/23 ▲