XProfan

- Page 2 -

Sebastian
König

The URL related sooner on one Dateiobjekt.

too this is naturally possible. mainly becomes the probably in the Context with Units usage find.

iF

with the Quotes is everything IO, you had only behind one Quote (and to the Gleichzeichen) one Freizeichen with installed, and [quote = blub] there not what iFBB in the reference aufs Quote to that turn off constraint.

Ah, ok.

iF

I had Yes so or so to very these Funktionalität into XIDE hineinzukatapultieren - Stichworte proposition-assistant/Explorer - vlt. takes Sebastian us thereby something work ex.

(presupposed his Parser shrug not XPSE-Codes and understand these likewise How normal XCodes.)

would be I self-evident gladly make

. I could for from my code a static Library with Low-Level-Access to The of me erstellte data base-class provide - with want too with of/ one not objektorientierten interface, because the grabbed hereon in ASM Perhaps something umständlich would. here could I integrally on Euren Wish orientieren.

Bislang processing my Parser only reines XProfan (and of it only a small part, I with the work on it straight first began have...) Support for XPSE would like I gladly install - but self parsen stops I for unnecessary work... one still simply XPSE Call and the spending weiterarbeiten, or?

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

Alte Profan²-Seite: [...]

09/11/07 ▲

The URL related sooner on one Dateiobjekt.

too this is naturally possible. mainly becomes the probably in the Context with Units usage find.

I thought there sooner not absolutely on Units, sooner a open (mini!) CVS what The XProfan.com already under the Haube carry (because of XIDE). herewith should it possible his from XIDE out one complete proposition to upload and within XIDE together zeitgleich in a proposition To works.

Sebastian king

Bislang processing my Parser only reines XProfan (and of it only a small part, I with the work on it straight first began have...) Support for XPSE would like I gladly install - but self parsen stops I for unnecessary work... one still simply XPSE Call and the spending weiterarbeiten, or?

would be komplizierter there one Verify should whether at all XPSE apply becomes (and then too yet each time a Process started - phew...) . solely to #include & include and a little {/} geparse is necessary (z.B. for Function/Prozedurerkennung)
in the principle is everything to { if it not if while & co is, a function/procedure.
Compile Mark Separation

#include meineinclude.inc// mit dem # davor ists ein include_once
include meineinclude.inc
myproc{}

while 1{}

The thing is only, I have here wg. the XIDE naturally one plenty neueren XPSE as it here to that DW gives, nevertheless ought to The actually here-downloadbare Version this suffice.

09/11/07 ▲

Sebastian
König

OK, so slow understand I, what you mean. it would well wealthy, instead of the file indicated simply alternatively or additional url To permit, or?

iF

Hmm... ok, in the principle could I the well too directly install. would be it because necessary, for my zeilenbasiertes Parsen (accurate: join of by Backslash connected Lines and anschließendes undo, if Doppelpunkte vorkommen) aufzugeben? your XPSE-Codes remind Yes in the meantime very on C++ or Java, where Zeilengrenzen just Leerräume are...

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

Alte Profan²-Seite: [...]

09/11/07 ▲

OK, so slow understand I, what you mean. it would well wealthy, instead of the file indicated simply alternatively or additional url To permit, or?

very, and if mgl. too another Dateiversionsangabe - z.B. FileVer. the stirs therefore the any XIDE-Panel/Plugin-SDK-Quelltextdateien a Versionsinfo in the Source carry which z.B. too of Updatecheck used becomes. Hierfür Gibts 2 mutants:
Compile Mark Separation

//Version:0.0.0
/Version:0.0.0e>

These Info could your Parser ditto from the Source reading and the XML enclose.

Sebastian king

objectively parst xpse not Zeilenbasiert, had there but ne idea How You your Parser nevertheless kleinhalten can where one not even the Semikolon as (xpse)possible Zeilentrenner wegdenken must. (the under but only functions there You Yes whom Source not really Verify must etc.)

see we times the three einfacheren Problemfälle on:
Compile Mark Separation

meineProc(string a,b,c,float x,y,z,long q,w,e){

    return true

}

//oder
meineProc(string a,b,c,float x,y,z,long q,w,e)

{

    return true

}

//oder
meineProc(string a,b,c,float x,y,z,long q,w,e){return trueFF>}

adopted the whole File lying in a String s and we've additional the pseudo whiletranslate (
Compile Mark Separation

whiletranslate(string s,from,to) {

    while instr(from,s) {s=translate $(s,from,to)}

    return s

}

) To Disposal, then counts:
Compile Mark Separation

//source säubern
s=translate(s,	,x20)
s=whiletranslate(s,x20x20,x20)
s=whiletranslate(s,
x20,
)
s=whiletranslate(s,x20
,
)
s=whiletranslate(s,
,
)
//others Zeilentrenner
s=translate(s,;,
)
s=translate(s,:,
)
//clinging solve

s=translate(s,{,

    {

        )

    s=translate(s,},

}

)
s=whiletranslate(s,
,
)

After this Pass lying really everything Zeilenbasiert to. can his that I something overlooking have there ichs here simply hineingetippt Have and it only to that understanding serve should. naturally is to this Pass the Source destroy - but I my your Parser need none useful Source and ought to whom Source quiet so zerhechseln can the slight The Information extrahierbar are which for XML necessary are.

The Parser should then only yet look whether The next row exakt one { is, in order to know the The actually row a Proc his should. (unless strain while if whileloop & co).

One small little gemeiner is the fact the xpse too the following rule:
Compile Mark Separation

string meineProc(string a,b,c,float x,y,z,long q,w,e){//hierbei would the Return Value True to Return in a String konvertiert

    return true

}

//or
long meineProc(string a,b,c,float x,y,z,long q,w,e)//hierbei would the Return Value 12 to Return into Long konvertiert

{

    return 12

}

//or
int meineProc(string a,b,c,float x,y,z,long q,w,e){return true}
// there's (xpse knows) bool, int, long, float, string and mem

hope the helps a little bit.

Sebastian
König

//Version:0.0.0
/Version:0.0.0e>

These Info could your Parser ditto from the Source reading and the XML enclose.

.

iF

Gewissermaßen... i'm now still again heavy the opinion, that these work not my Parser heard and it unnötigerweise on a multiple the recent Umfangs aufblähen would...

i think but, I have a lovely alternatively-suggestion: I could without large hoisted a interface install, The arbitrary Präprozessoren supported. it's running then simply so, that The address of/ one Callback-function indicated go must, which my internes GetNextLine() supplant. everything, what these function do should, is the Line in reinem XProfan and The zugehörige Zeilennummer from the Quelldatei To supplying.

in this Variante should my Parser then garnichts over additional Syntax-Features know and would completely generally held. Also would possible future XPSE-extensions and XPIA automatically supported go. and a zusätzlicher Process should neither launched go...

in the application liefe it then so, that one proposition How to that example XIDE simply two Bibliotheken (libxpdb.lib and libxpse.lib) dazulinkt and the XPDB-Parser the Plug-In bekanntmacht.

apiece longer I above nachdenke, so rather gefällt me these Solution. tappt im dunkeln holds both Aufgabenbereiche beautiful modular separated and permits accordingly very simple maintenance and expansion. what hold You of it?

MfG

Sebastian

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

Alte Profan²-Seite: [...]

GetNextLine could but not suffice in Make How this:
Compile Mark Separation

myproc(string abc)

{

    return abc

}<

Sebastian
König

GetNextLine could but not suffice in Make How this:
Compile Mark Separation

myproc(string abc)

{

    return abc

}<

Why not? it ought to in so one drop simply the following supplying (each row corresponds to one appeal of GetNextLine, in the comment standing The Zeilennummer, The additional supplied becomes):
Compile Mark Separation

proc myproc 1

    parameters abc$ 1
    return abc$ 3
    endproc 4

You understand?

MfG

Sebastian

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

Alte Profan²-Seite: [...]

Hrm i see sehrwohl, therefore my I Yes the GetNextLine not suffice could. In og. xpse row 1 is - without the row 2 famous isn't ermittelbar the it itself circa a proc deals! what hold You from the Variante whom code simply before You it passierst complete on a external Parser To give? You could then simply with the Rückgabeergebnis works which hold too whom kompletten code contains.

Sebastian
König

Hrm i see sehrwohl, therefore my I Yes the GetNextLine not suffice could. In og. xpse row 1 is - without the row 2 famous isn't ermittelbar the it itself circa a proc deals!

Hmm... möglicherweise understand we mutual wrong, but the ought to still no trouble his... the Prä-Parser ;) can already row 2 and for may part yet More beforehand reading - important would only, the Result then my Parser line by line vorzusetzen... (so meant I my example). but alike, because:

iF

what hold You from the Variante whom code simply before You it passierst complete on a external Parser To give? You could then simply with the Rückgabeergebnis works which hold too whom kompletten code contains.

Gefällt me very well!

in the Grunde lautete so Yes my first suggestion (appeal of XPSE through my Parser). naturally can the then How with the GetNextLine-Variante on the Plug-In/Callback-Base make and so the ständige started one further Prozesses avoid. important would only, that the whole on Include-plain stattfindet, means that always only very The angegebene File processing and is $I-instructions in the code stay. I take at times, it would no great hoisted, a suitable Lib from your existing XPSE-Code produce, or?

MfG

Sebastian

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

Alte Profan²-Seite: [...]

The hoisted holds itself in border, glue then but still again on me.

I mean but I would XPSE not as basis for Lib take - the Abspecken (or distribute of ifdefs) would explicit aufwändiger as the bisl Parserei. I mean I schreib but simply a function and schubs you whom C-code rüber whom You then directly same install can. That the Lib can we with the small part save.

09/13/07 ▲

Sebastian
König

The hoisted holds itself in border, glue then but still again on me.

OK, naturally can I The work on Base Your Codes gladly take - means only since so

. In which shape very I the whole einbaue, look I then time - i want The interface for In any drop generally hold...

priority has too first, that everything fundamentally functions what about me then only yet extensions for further Syntax-items install must. priority having first of all Includes, Header, Units and Procs.

MfG

Sebastian

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

Alte Profan²-Seite: [...]

09/13/07 ▲