XProfan

well You again - is still integrally simply:

Compile Mark Separation

assign #1,myDll.dll
openrw #1

whileloop 1000

    putbyte #1,rnd(256)

wend

closerw #1

How otherwise??

salvo, iF.

PS: well then say too yet one created so no .dll from XProfan out?!!! :/:

Sebastian
König

an Description, How one functions export have I unfortunately not found. an short explanation would nice.

Hello Thomas,

in the Help there still whom new cut offed Dynamic Link Libraries

. here one neckline from it:

The Direktive $DLL, The at the beginning the Source code stand ought to, divides Profan2Cpp with, that a DLL generiert go should.

Procedures, The export go should, go with dllproc eingeleitet. After the names the procedure becomes thereby as second argument The Number of Parameter, The The procedure expects, indicated. These number ought to naturally with the, what later with parameters specify becomes, coincide. with dllproc declared Procedures cannot nested go.

there's there also one kurzes Example for a DLL. everything clear?

MfG

Sebastian

Windows XP, XProfan/Profan² 4.5 bis 11
Profan2Cpp-Homepage: [...]

Alte Profan²-Seite: [...]

thanks first for Info with the Help

, I have only in the Versionhistorie geschaut. my otherwise functioning Testcode slopes I here time ran. Please rename in zipper.

testcode.zip.txt	5 kB

Hochgeladen:	07/25/05

Downloadcounter:
		Download

Fernando
Santos

Hello Sebastian

have attempts with your example a DLL to create, it'll a dll with the size of about 350KB
generiert and if I try the beispielprogramm to start appear The Message the The namedll.inc not found becomes. I must somehow something wrong make, or???

greeting

Pedro

Innovative Produkte für Aufzüge

Prf2CPP created at produce the DLL too another dazugehörige Includedatei. These ought to in the same directory lying as PRF which The Includedatei needed. copy The created Include means in your Programmierverzeichnis.

salvo, iF.

Hello Sebastian,
code ausserhalb of Proceduren becomes the DLLMain() added. so can I means globale Deklarationen perform. this corresponds to Yes vaguely AttachThread(), now missing me but the Gegenstück DetachThread() to that automatischen straighten up and memory enable. On the what with FreeDLL happens have I Yes otherwise no influence.
becomes Perhaps only seldom used, however if a Umsetzung no large Problems bereitet would it still beautiful if you this yet install could

07/26/05 ▲

Sebastian
König

[quote:32e8acf1bc]Hello Sebastian,
code ausserhalb of Proceduren becomes the DLLMain() added. so can I means globale Deklarationen perform. this corresponds to Yes vaguely AttachThread(), now missing me but the Gegenstück DetachThread() to that automatischen straighten up and memory enable. On the what with FreeDLL happens have I Yes otherwise no influence.
becomes Perhaps only seldom used, however if a Umsetzung no large Problems bereitet would it still beautiful if you this yet install could[/quote:32e8acf1bc]
Hello Thomas,

is correct, such a thing would really meaningfully. time see, How I the best umsetze... what hold You a manner CleanUp-procedure, which - if present - automatically at Entladen the DLL called becomes?

MfG

Sebastian

Windows XP, XProfan/Profan² 4.5 bis 11
Profan2Cpp-Homepage: [...]

Alte Profan²-Seite: [...]

Hello Sebastian,
very soetwas my I. Perhaps ought to too The Main optinal in a DLLProc laid go can (because of the Übersichtlichkeit). Z.B.:
DLLProc DLL_Init,0
DLLProc DLL_End,0

ought to still on it hingewiesen go, thats functions automatically carryed out and be not called go can.

would be cool if you the in anybody shape to assimilate could

Sebastian
König

[quote:ea11fb37e0]very soetwas my I. Perhaps ought to too The Main optinal in a DLLProc laid go can (because of the Übersichtlichkeit). Z.B.:
DLLProc DLL_Init,0
DLLProc DLL_End,0

ought to still on it hingewiesen go, thats functions automatically carryed out and be not called go can.

would be cool if you the in anybody shape to assimilate could[/quote:ea11fb37e0]
Hello Thomas,

I consider yet, How I the best resolve... one so, the others so gefällt me neither - but two different Opportunities to Initalisierung are sooner verwirrend, think I.

somehow bid itself the area the Hauptprogramms too really on... my favorisierte idea is therefore in the momentum, both on the equal place to house and the Hauptprogramm at Loading and Entladen the DLL aufzurufen. to distinction would I then a new Profan2Cpp-specific Systemvariabele to introduce. so could the then looks:

Compile Mark Separation

if %DLLInit

    code to Initialsierung

else

    code to that straighten up

endif

what hold You (and who otherwise mitliest

) of it?

MfG

Sebastian

Windows XP, XProfan/Profan² 4.5 bis 11
Profan2Cpp-Homepage: [...]

Alte Profan²-Seite: [...]

@Sebastian: make it as on the Reibungslosesten expires.

in the Endeffekt behaupte I is it alike How the whole dealt becomes.

i'd warscheinlich simply determine: If a DLL export go should - so must following 2 Procedures in the View source present his. dllproc DllInit and dllproc dllexit. means a One- and Ausstiegsprozedur. How You, the then intern regelst ought to into area your experience entrapments - with which You entscheidest what best functions.

salvo, iF.

DLLCode ausserhalb of Procedures feel so did i sooner as unüblich. I schließe me first iFs suggestion on, though in the Endeffekt is me The Syntax not so important, only The Possibility counts