|
|
In article <Xns### [at] 204213191226>,
"Rafal 'Raf256' Maj" <raf### [at] raf256com> wrote:
> Would it be a big problem to allow syntax :
>
> #macro finWater1 reflection { .01 .2 } #end
> finish { finWater1 }
>
> instead of finish { finWater1() }
>
> this is a small change [probably] and shorten syntax is more comfortable
It isn't such a small change...you seem to assume that about anything.
I'm betting that POV uses the "(" to determine it is calling a macro or
function, and it makes a very helpful visual indicator as well. Your
version is shorter by one () pair...typing is not really any faster, and
readability is much worse, you have no way to tell a macro call from a
variable identifier. It also kills the possibility of passing a macro
parameter as a parameter in some future version without some weird
syntax.
Stop counting keystrokes, it is a stupid and useless exercise, and one
you seem to be obsessed with.
> btw. this will make pov macros act more like C preprocesor macros
That isn't necessarily a good thing. POV macros are not C preprocessor
macros.
--
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
|
|