| |
|
|
- Page 1 - |
|
| XProfan Precompiler and Syntax-Enhancer [XPSE] [...] Updates and Notes: |
|
|
| |
|
|
| |
|
- Page 2 - |
|
|
| small Update wg. BugFix on 11.0.1.7.t [...]
One larger View source of Jac having xpse crash let, the Error is fixed.
@Jac: thanks! |
|
|
| |
|
|
|
| Experimentelle Version 11.0.1.7.u [...] , einfacherer Use with Arrays
Arraydefinitionen (too Funktionsparameter) simply over Plural the Typenangaben, Wegfall the Variablensuffix and -type. its simply fine...
as always: CompileMarkSeparation//als Beispiel am long: long(s) definieren:
long a,b,c,...
//auch möglich
long a=20,b=50,c=a*b
//oder Beispiel als Funktionsparameter
myFunc1(long a,b,c) so now too with Arrays: CompileMarkSeparation//as example on Long-Arrays: longarray(s) define:
longs a,b//longs instead of long!
//now can we here:
a[100]=20
b[50]=a[100]
print sizeOf(a)//if one a&[] means reicht one simple a
//or.
myFunc1(longs a,b)...
instead of: (Langsyntax*) CompileMarkSeparation Arraydefinitionen to the Langsyntax stay naturally hiervon unberührt.
* XProfan-Syntax
Update: [...] |
|
|
| |
|
|
|
RGH | and How distinguish You The variables a!, a%, a&, a$, a![], a%[], a&[] and a$[]?
Greeting Roland |
|
|
| Intel Duo E8400 3,0 GHz / 4 GB RAM / 1000 GB HDD - ATI Radeon HD 4770 512 MB - Windows 7 Home Premium 32Bit - XProfan X4 | 07/10/08 ▲ |
|
|
|
|
Jac de Lad | I take at times, that long only for variables is and longs only for arrays. |
|
|
| Profan² 2.6 bis XProfan 11.1+XPSE+XPIA+XPRR (und irgendwann XIDE) Core2Duo E8500/T2250, 8192/1024 MB, Radeon HD4850/Radeon XPress 1250, Vista64/XP | 07/10/08 ▲ |
|
|
|
|
| a!, a%, a&, a$, a![], a%[], a&[] and a$[] are Langsyntax - means distinction by Variablensuffix, so How You it vormachst*.
one Variablenbezeichner several Types zuzuordnen stops I do not for lehrwürdig.
Deklariert one variables to Kurzsyntax, so are whom deklarierten Variablenbezeichnern naturally The Types by Deklaration zugeordnet and Redeklarationen go angemeckert**. (as well as in C#, Pascal (Delphi) and others lehrwürdigen Languages...)
in example is imho in Delphi neither zulässig; CompileMarkSeparation or in C not without warning: CompileMarkSeparation it remaining as always thereby: XPSE-Codes liable strengeren Richtlinien what durchschnittlich viewing To better Programs/Ergebnissen lead.
* same Variablenbezeichner by Langsyntax with unterschiedlichen Types deklarieren becomes of XPSE not always geduldet, in the entrapment go Warnmeldungen outputted.
** there's syntaktische situations in them XPSE not know can (means would like), whether a Redeklaration permitted is or. as Redeklaration respected go can, there XPSE whom code not to Laufzeit viewing can. In this case schweigt XPSE rather instead of with of/ one Redeklarationsfehlermeldung to interrupt.
in example is it therefore under Umständen too without warning possible: CompileMarkSeparationTo deklarieren what to CompileMarkSeparationaufgelöst becomes.
uses one however now a without Variablensuffix, so becomes The first Typendeklaration (in the example: string) uses circa a to a$ aufzulösen. uses one however a with Variablensuffix, so counts naturally this - vorrausgesetzt vorhergehender Deklaration to beliebiger Syntax there otherwise a warning outputted becomes.
Jac
I take at times, that long only for variables is and longs only for arrays.
Exakt, even if the imho not Rolands question was.
but not long, string, int, bool, mem and float for Arrays simply: longs, strings, ints, bools, mems and floats
Hiernach one Stringarray define and same time befüllen: CompileMarkSeparation to Langsyntax something umständlicher: CompileMarkSeparation but the really crazy is the the following possible is: CompileMarkSeparation with Deklaration can one aray immediate values allocated go z.B. from functions which one aray zurückliefern or from vorhandenen Arrays. |
|
|
| |
|
|
|
RGH | Hello iF, The Lehrwürdigkeit isn't my Topic. Einbuchstabige Bezeichner are in principle not lehrwürdig. Variablennamen should always sprechend his and Sparchen without Typkennzeichen whom type through Prefix in the names having, as under C++- and others Programmierern always ambulation and give is (Related Bezeichner in windows-API-Documentation).
Greeting Roland |
|
|
| Intel Duo E8400 3,0 GHz / 4 GB RAM / 1000 GB HDD - ATI Radeon HD 4770 512 MB - Windows 7 Home Premium 32Bit - XProfan X4 | 07/10/08 ▲ |
|
|
|
|
| Update on 11.0.1.7.v [...] - Anpassung on XProfan 11, among other things because of the END-Befehls. |
|
|
| |
|
|
|
| Update on V11.0.1.7w [...] - profalt.inc power now no Problems More. |
|
|
| |
|
|
|
| Ooops! there's me well one Malör happens, I werd well a working Version nachreichen must. |
|
|
| |
|
|
|
| Update on V11.0.1.7y [...] - profalt.inc power now no Problems More. (having yet something overlooking...) |
|
|
| |
|
|
|
| Update on V11.0.1.7z [...] - Error in For-creep because of veraltetem ADD fixed.
Thanks on: Jens-Arne Reumschüssel
with FOR-creep, a others Schrittweite as 1 having, becomes of XPSE z.B. the commands "ADD i%,10" uses. XPSE self bleats this then the Syntax-Check on (procedure ADD not declared), sodaß the suitable Program not any more from XPSE out kompilierbar is. i think, instead of "ADD" ought to "INC" uses go, there "ADD" ex XProfan 11 antiquated is and not any more uses go can.
I give To, that this Perhaps no truer bow is, because XProfan11 first today official herausgekommen is, but at least bleats XPSE Yes self whom antiquated commands on.
thanks Jens! |
|
|
| |
|
|
|
| Update on V11.0.1.7za [...] - XPSE knew %BmpB not. |
|
|
| |
|
|