 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 11 Sep 2002 15:32:30 -0400, Christopher James Huff <chr### [at] mac com>
wrote:
> > > Huh? The internal functions have names, they are just defined through
> > > the functions.inc file instead of being built-in.
> > So what's the problem to define keywords for types this way ?
>
> Slower parsing, for one. ;-)
But I can include only necessary files so can optimize parsing time.
> Requiring an external include file.
So many languages use header files with definitions so nothing new.
> > Interesting idea. Are you reserving rights to make patch for it ? ;-)
>
> Heh, implementing it in the current POV would take a huge amount of
> work. I'm mainly thinking of it as something to be considered for the
> 4.0 rewrite.
chicken ;-)
> I did something similar for Sapphire: when a
> symbol is resolved it moves to the front of the symbol table.
Any reference ? You mean http://sapphire.sourceforge.net/ ?
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Or the parser could do something similar on the fly: if a token is
> matched, move it to the front of the list. Tokens that occur more often
> will spend more time towards the front of the list. Not as efficient,
> but simpler and adapts to the scene...for example, a mesh file will have
> a very different occurance distribution from other scenes, mainly having
> "triangle" or "smooth_triangle", "{}" braces, ",", "<", and ">"
> characters, and numbers. After the first triangle, these will be at the
> top of the token list. I did something similar for Sapphire: when a
> symbol is resolved it moves to the front of the symbol table.
Do you mean that the current POV-Ray parser (which I never
really investigated) searches the full list of keywords to get the
proper token ? If so, what about hash tables as used when parsing
mesh triangles/textures ?
Putting the last resolved symbol at the beginning of the
list assumes a high probability to find the same symbol again. I
agree this is good for such big objects as meshes (and usually
a very big scene is made of very big meshes...). But I don't think
it's better than using hash tables in general. [A perfect hash table
would be appropriate for build-in keywords which number is fixed].
Forget all that if POV-Ray does it already :-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 10 Sep 2002 15:42:31 +0200, ABX <abx### [at] abxartpl> wrote:
> Any idea for nice name for interpolation without interpolation ?
Let's check voting. 'path_type' followed by parameter seems fine.
There are two votes for float parameter and two votes for keyword parameter.
Any help to fullfill democracy in this syntax designing ?
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ABX wrote:
> On Tue, 10 Sep 2002 15:42:31 +0200, ABX <abx### [at] abxartpl> wrote:
>
>>Any idea for nice name for interpolation without interpolation ?
>
>
> Let's check voting. 'path_type' followed by parameter seems fine.
> There are two votes for float parameter and two votes for keyword parameter.
> Any help to fullfill democracy in this syntax designing ?
>
> ABX
float !
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Forget all that if POV-Ray does it already :-)
We will forget it then ;-)
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> > Let's check voting. 'path_type' followed by parameter seems fine.
> > There are two votes for float parameter and two votes for keyword
parameter.
> > Any help to fullfill democracy in this syntax designing ?
> >
> > ABX
>
> float !
keyword!
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 12 Sep 2002 15:30:10 +0200, "Thorsten Froehlich" <tho### [at] trfde>
wrote:
> keyword!
>
> Thorsten
Are you representing general stategy of the team with this vote ? I'm just not
sure how many votes I should count ;-)
Serously if this is suggestion from the team I would like to follow it. So ?
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
>
> > > Any help to fullfill democracy in this syntax designing ?
> >
> > float !
>
> keyword!
float!
Christoph
--
POV-Ray tutorials, IsoWood include,
TransSkin and more: http://www.tu-bs.de/~y0013390/
Last updated 13 Aug. 2002 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christoph Hormann wrote:
>
> Thorsten Froehlich wrote:
> >
> > > > Any help to fullfill democracy in this syntax designing ?
> > >
> > > float !
> >
> > keyword!
>
> float!
Keyword!
--
Ken Tyler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <nvt0oukgaqekbtkt6l08bmml104qg5ujk1@4ax.com>,
ABX <abx### [at] abxartpl> wrote:
> Let's check voting. 'path_type' followed by parameter seems fine.
> There are two votes for float parameter and two votes for keyword parameter.
> Any help to fullfill democracy in this syntax designing ?
Keyword.
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
