| |
|
|
- Page 1 - |
|
 |
because You still not verständlich declared have, what nprocs are.
Hello Nico,
thanks for Info and the Thread here - unfortunately can I so but nothing begin I not know can, what You do not understand.
Perhaps. can You me under Beachtung the Documentation [...] say, what you unclear is.
Inline-Assembler:
|
|
|
| |
|
|
| |
|
- Page 6 - |
|
|
 Dietmar Horn | Hello together,
on the actual cover this Threads "Was are native functions?" thorough, here time one attempt the Statement, what nativer code really is.
statement from my XProfan-Textbook, part 8 (not yet published, one größeres Update becomes it expected against end the year give):
Nativer codeNativer code is solely another Bezeichnung for Maschinencode. these The systemnaheste Language, The of processor directly and without previous Compilation processing and carryed out go can. in the Contrast To Assembler or others Programmiersprachen (How z.B. XProfan) deals it itself hierbei circa a for Humans hardly verständlichen Binärcode (very vereinfacht framed only from "Nullen" and "Einsen" bestehend). The Maschinencode becomes in the rule of a Assembler or Compiler created. directly in Maschinensprache must only program go, if no Assembler for Zielprozessor available standing, what it nowadys well hardly yet give might. becomes from the Programming in Maschinensprache spoken, becomes today üblicherweise The Maschinenprogrammierung in Assemblersprache under usage one Assemblers meant, the the as Textdatei vorliegende Program in binäre Maschinenbefehle Translated. The Maschinensprache exists a follow of Bits or. Bytes, The in this shape for us as Humans useful unlesbar is. to that produce of Maschinencode are vereinfachende Tools created been - so z.B. The Assemblersprache. The Lesson the Assemblers exists therein, the Programmer some Unbequemlichkeiten the Programmierens in reiner Maschinensprache abzunehmen. too with XProfan can meanwhile nativer code created go, the for a multiple faster expires, as the of XProfan-Compiler self begot code. prerequisite this is the usage the free XPSE ("XProfan-Precompiler and -Syntax-Enhancer") of David "iF" Strutz (XPSE-Downloadmöglichkeit: [...] here some Feautures of XPSE: produce nativen Codes ex XProfan 11.  use Windows-APIs without tappt im dunkeln before deklarieren To must  Inline-Assembler  Echtes Multi-Threading and threadsichere Datentypen  Native Profan by nProc  Kinderleichter Inline-Assembler with Datentypenunterstützung  Echtes unterbrechungsfreies SubClassing  Nahtlose Integration importent Datentypen  Sicheres ProcAddr  No ASM-Vorkenntnisse necessary with XPSE are now then too Ausführungsgeschwindigkeiten of XProfan (as Interpretersprache) possible, The reinen Assembler- or C-Programs in nothing behind. an complicated installation of XPSE isn't necessary. it reicht completely from, The subesquent Files whom XProfan-Ordner To copy:  XPSE.exe [...]   Jwasm.exe [...]   POLink.exe [...]  subsequently is it solely yet necessary, in the XProfan-editor whom appeal the XProfan-Interpreters Profan.exe by the appeal of XPSE.exe To supplant. One angenehmer Nebeneffekt with the usage of XPSE as Precompiler exists therein, that XPSE to the Compile a strengeren Syntax-Check the Programmcodes durchführt as XProfan yourself. therefore can itself the Programmer one often zeitaufwändiges Search to Fehlern in its code save, which in the ungünstigsten entrapment first to the Disclosure the produce program at users noticeable make.
Greeting Dietmar |
|
|
| Multimedia für Jugendliche und junge Erwachsene - MMJ Hoyerswerda e.V. [...]  Windows 95 bis Windows 7 Profan² 6.6 bis XProfan X2 mit XPSE Das große XProfan-Lehrbuch: [...]  | 11/29/09 ▲ |
|
|
|
|
 Jörg Sellmeyer | [offtopic]I Have The left time in anklickbare transformed. there seems a bow in the Forum To his. If the left behind the Arrow stand, go tappt im dunkeln not as such recognized![/offtopic] |
|
|
| Windows XP SP2 XProfan X4... und hier mal was ganz anderes als Profan ...  | 11/29/09 ▲ |
|
|
|
|
 Frank Abbing | Have me times the Info over the Inline-Assembler of PureBasic durchgelesen. this is IMHO primitivster Mist, one must at all only 3 tab use in the 32 bit-Version. too otherwise there Einschränkungen without end. there praise I me whom XPIA, the everything zulässt, what at all possible is with MASM32/JWASM, even Macros.
Have here now red, the XPSE The engineering of XPIA copies and ditto JWASM/POLINK using, around the interne Dll to make up. Codes Have I do not splendid discover. which Libs are installed and which Macros. How can I further Libs integrate? such Info are missing yet gänzlich. |
|
|
| |
|
|
|
 Nico Madysa | small inquire: would be because one Access to something How globale variables possible? the could for XProfan whom Use with suit Subclassprocs relieve. |
|
|
| |
|
|
|
 | [offtopic] Jörg Sellmeyer, Beitrag=55211, Zeitpunkt=29.11.2009I Have The left time in anklickbare transformed. there seems a bow in the Forum To his. If the left behind the Arrow stand, go tappt im dunkeln not as such recognized! The problem was one on the Link klebendes TAB-characters!  [/offtopic] |
|
|
| |
|
|
|
 | Nico Madysa, Beitrag=55217, Zeitpunkt=29.11.2009
small inquire: would be because one Access to something How globale variables possible? the could for XProfan whom Use with suit Subclassprocs relieve.
Per Global . CompileMarkSeparationdeclare owp&
cls
owp&=setWindowLong(hWnd,gwl_wndProc,procaddr(hwnd.wndProc,4))
waitinput
end
nProc hwnd.wndProc
Parameters wnd&,msg&,wp&,lp&
global owp&
return callWindowProc(owp&,wnd&,msg&,wp&,lp&)
oc
|
|
|
| |
|
|
|
 Nico Madysa | |
|
| |
|
|
|
 | what How? You can still The address one Bereiches by Parameter transfer!
otherwise, look again: [...] (Have strain again dran turned)
for Debugging take I gladly exitprocess(long) or settext(hWnd,"blub"). ^^. |
|
|
| |
|
|
|
 Nico Madysa | whom entry mind I already, I reminded me only not its. 
my trouble was one Testkode following manner: 100 Buttons, its lever in a area are. an Nproc should by SetWindowLong to Subclassproc the Fensters to be with ~WM_SIZED The Buttongrößen anzupassen. only can I self of/ one Subclassproc Yes no Parameter transfer, but from from somewhere must The Proc The Handles relating. therefore globale variables.
I count The sec, up to your response, How all the vieeel plainer went.  |
|
|
| |
|
|
|
 | If you a memory Change want: CompileMarkSeparation or relating of 100 Handles: CompileMarkSeparation(ungetestet)
but dim m#,4 power almost none sense, can still same
var m&=globalAlloc(gPTR,4) write - might the same his.
In nProcs there too Dim, but as function: CompileMarkSeparationso too with byte, thatswhy Gibts too getByte setByte getLong and setLong vlt. for you interestingly. |
|
|
| |
|
|
|
 Nico Madysa | already clear. but a subclassende procedure call Yes in all rule not I, separate windows on. |
|
|
| |
|
|
|
 | what? the here functions (naturally) CompileMarkSeparationGemerkt/Separiert von http://xprofan.com/thread.core?p=55223#55223
declare owp&
cls
owp&=setWindowLong(hWnd,gwl_wndProc,procaddr(hwnd.wndProc,4))
waitinput
end
nProc hwnd.wndProc
Parameters wnd&,msg&,wp&,lp&
global owp&
return callWindowProc(owp&,wnd&,msg&,wp&,lp&)
| 11/29/09 ▲ | |
|
|
|