Spider schrieb in Nachricht <36B8D2D3.DE77CCE7@bahnhof.se>...
>Lets start commenting on the discussion.
>
>
>> Only difference is the fact, that WinTree does the recursion once (in
Visual
>> Basic),
>*GASP*
>Whatta heck are you accusing me of?
>It is Delphi, admittedly using a very sloppy design, and rxlib, and
>dElphi 3, but... "VISUAL BASIC" ????! *gasp* *choke*

Sorry! No offense intended! I really thought so, but I must have had another
program in mind. I thought I remembered your program needed the VB runtimes.
Must have been one of the other utilities I recently downloaded. And now you
mention it, I remember the RXLib type of spin buttons (the diagonal ones).

To the innocent bystander I *must* explain, that telling someone who is a
Delphi freak, that he is using VB is one of the worst accustions a person
can make <g> (like telling Kenneth Starr voted for Bill Clinton last
election).


>> producing an include file with all objects already spelled out, and
>> the recursive parser does this while parsing. So parsing is definitely
the
>> culprit here, not allocation.

>Yes, it is. That's why I made the prog. the allocation takes around 4-8
>seconds, depending on the size of the tree.

Hmmm. I must definitely have a look at the parser and allocation code one
day. It's said to be plain ANSI C, so I think I can read it well enough.

What would interest me, if there are big differences in parsing/rendering
ratio on various systems, and using different compilers on the same system.
E.g. are the different patches for Win32 almost equally efficient, or is one
more efficient in parsing and the other more in rendering? I think Ron
should be able to answer part of that. I think he uses VC6, while the
official build is done in Watcom C. Perhaps someone should try BCB and BC
too. (Sorry guys, don't know the other platforms well enough).

>> Perhaps there would be demand for a small program, which unravels #while
>> loops and macros and creates (huge) include files out of them, taking a
bit
>> out of the parsing POV-Ray does. This could work like WinTree, but
perhaps a
>> bit more generalized.

[...]

>yes, this might be helpful, but perhaps not good enough. This is a thing
>too look deper into.

I think Ron Parker had some very good suggestions on this.

--
Rudy

Post a reply to this message