|
|
Am 15.03.2017 um 17:52 schrieb Bald Eagle:
> clipka <ano### [at] anonymousorg> wrote:
>
>> Why, yes, of course: Start your scene with
>>
>> #version version; // sic!
>> #if (version >= 3.71)
>> #define Tau_Is_Reserved = true;
>> #else
>> #define Tau_Is_Reserved = false;
>> #end
>> #version 3.7; // minimum version
>
> I haven't had a lot of time to think this through, but was wondering if a "fix"
> such as this could be conveniently added into an include file like "consts.inc"
> ?
Since such a file would come with a particular POV-Ray version, what use
would it be?
>>> Command aliases. A way to tell the parser to treat all instances of a statement
>>> as a command to do "X" - just like in a Unix shell.
>>
>> You mean, something like, say, a... /macro/ ?!
>> Yeah, I think it would be neat if POV-Ray had something like that ;)
>
>
> I actually wanted to add a bit of clarification about this:
> Writing a macro is similar to what I was thinking, but the real core of the idea
> is to have REAL aliases.
> https://en.wikipedia.org/wiki/Alias_(command)
"In computing, alias is a command in various command line interpreters
(shells) [...]"
Q: Is POV-Ray a command line interpreter?
A: No. It is an interpreted programming language.
=> "alias (command)" not applicable to this context.
> Invoking a macro would have a different syntax than the SDL directive.
> If I wanted to use, say, "define" instead of "declare",
> my thought was to have something along the lines of #alias {define, declare}
__
~ (__() ~ ~
~ ~
^
|
Can of worms, opened.
Post a reply to this message
|
|