XProfan

Jörg
Sellmeyer

herewith come I on a Size of 64mb with of/ one String-Length of 32766.

Compile Mark Separation

Var File$ = $ GetDir("@") + "\\Test.ini"
Print File$

WhileLoop 100000

    writeini File$,"Test","Eintrag" =  + MkStr$("A",&Loop) + " " + Str $(Len(ReadIni$(File$,"Test","Eintrag")))
    'Case %ioresult:Break 'here's to few Einträgen Schluss, if one it drinlässt
    Locate 2,1
    Print FileSize(File$)'that here counts yet, if too The maximum String-Length access is!
    Print Len(ReadIni$(File$,"Test","Eintrag"))

Wend

'ShellExec(File$,"Open",0) ' not To recommend, if The File larger becomes
waitinput

Windows XP SP2 XProfan X4
... und hier mal was ganz anderes als Profan ...

XProfan X2
Vista (TM) Home Premium, SP2, Core(TM)2 Duo P8600 @ 2.40GHz

against with older Profan-versions The boundary imho with 32kB lying.

Jörg
Sellmeyer

The giilt Yes evident still. The Filesize is Yes irrelevant, if Readini not everything ausliest.

Windows XP SP2 XProfan X4
... und hier mal was ganz anderes als Profan ...

XProfan X2
Win7 Enterprise, SP1, Xeon X5670 @ 2.93GHz

Andreas
Koch

Therefore would but only The Size of a EINTRAGS in a ini-File 32kb terminable and accordingly The Begrenzung for functions "readini" and "writeini".

I have the finished ini-File from obigem example a additional entry angefügt and this subsequently successful read can. The File on itself can means larger his as 64kb.
interestingly would it for me now, to know, whether it for Filesize the ini-File a constraint gives.

Jörg
Sellmeyer

You need Yes only time a Inidatei with x Einträgen of each 32k create. building You The Loop supra something circa.

Windows XP SP2 XProfan X4
... und hier mal was ganz anderes als Profan ...

XProfan X2
Vista (TM) Home Premium, SP2, Core(TM)2 Duo P8600 @ 2.40GHz

Schade the for XProfan (yet) no assoziativen Arrays velvet functions How
"serialze"/ "unserialize" existieren.

XProfan X2
Win7 Enterprise, SP1, Xeon X5670 @ 2.93GHz

Andreas
Koch

I have Jörgs suggestion umgesetzt and the "Beschreibenvorgang" after a knappen hour with 100MB aborted. subsequently have I under again a entry appended and this successful read can. apparently there means no boundary for Size, me wealthy 100MB in each drop.

I have of course no idea, what a assoziatives aray is

, would but already with a dynamic 2D-Array and a couple funktionsfähigen Matrixoperationen happy.

anyway once more thanks for Help.

XProfan X2
Vista (TM) Home Premium, SP2, Core(TM)2 Duo P8600 @ 2.40GHz

dynamic 2D-Arrays and Matrixoperationen are against with XProfan no
trouble.

The Difference between one indizierten and assoziativen Arrays is,
that in the Contrast to that Indizierten instead of numbers sooner Keywords as Indizes
uses go:

Compile Mark Separation

'normal
a[0]=10
a[1]=20
'assoz
a["jux"]=10
a["dallerei"]=20

such Arrays are a very mächtiges tool.

XProfan X2
Win7 Enterprise, SP1, Xeon X5670 @ 2.93GHz

Andreas
Koch

hears not badly on, with the whom assoziativen Arrays.

but:
If dynamic 2D Arrays and Matrixoperationen with XprofanX2 no trouble are, make I something wrong.

yet could I dynamic 2D Arrays only in a procedure, the I The Size commit, deklarieren and Edit. the schränkt already very one, particularly, if to the aray too global use could.
Also let The MAT-Operationen by me always the program "abschmieren". there there were too once one Forumthema To.

Presumably be I simply of MATLAB verwöhnt....