Hi!

Internal source editor of
PovRay for Windows 3.5 RC2
does not colorize atan2d.
Similar problems with some new
functions may occur.
I didn't test all of them.

Vic

Post a reply to this message

In article <3cc98d76@news.povray.org> , "Vic" <let### [at] fwhu> wrote:

> Internal source editor of
> PovRay for Windows 3.5 RC2
> does not colorize atan2d.
> Similar problems with some new
> functions may occur.
> I didn't test all of them.

"atan2d" is no POV-Ray keyword in any official version.  Are you sure you are
talking about POV-Ray 3.5 and not some unofficial patch?

    Thorsten


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

> "atan2d" is no POV-Ray keyword in any official version.

Hmm, it's listed in "7.10.1  Float functions and macros" in the docs as a
function like atan2 that uses degrees.

- Slime
[ http://www.slimeland.com/ ]
[ http://www.slimeland.com/images/ ]

Post a reply to this message

Slime <noo### [at] hotmailcom> wrote:
>> "atan2d" is no POV-Ray keyword in any official version.

> Hmm, it's listed in "7.10.1  Float functions and macros" in the docs as a
> function like atan2 that uses degrees.

  That doesn't make it a keyword.

  Only keywords are highlighted, not identifiers defined somewhere in some
include file.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

>   Only keywords are highlighted, not identifiers defined somewhere in some
> include file.


Ah, you're right, it's in an include file. Sorry, didn't notice that.

- Slime
[ http://www.slimeland.com/ ]
[ http://www.slimeland.com/images/ ]

Post a reply to this message

"Warp" <war### [at] tagpovrayorg> wrote:
> >> "atan2d" is no POV-Ray keyword in any official version.
>
> > Hmm, it's listed in "7.10.1  Float functions and macros" in the docs as a
> > function like atan2 that uses degrees.
>
>   That doesn't make it a keyword.
>
>   Only keywords are highlighted, not identifiers defined somewhere in some
> include file.

Aside from the fact, that this _IS_ defined in an include, and that
this will probably called a feature request:
Wouldn't it be nice, to have the Codemax-editor highlight also the
identifiers of macros and funtions, that come in includes with a
vanilla-distribution of POV? I mean, there _are_ powerful macros
and functions that come with the includes, so why not make them colored?

..
... Ah, I see... It would probably a lot work, and there are other jobs
with higher priority ... OK, don't bother ...

Just some thoughts, that came into mind ...

Post a reply to this message

In article <3ccc6b94$1@news.povray.org> , "Jan Walzer" <jan### [at] lzernet> wrote:

> Aside from the fact, that this _IS_ defined in an include, and that
> this will probably called a feature request:

This feature already exists - in the Mac version - which highlights all*
declares and macros found in #include files :-)


    Thorsten


* Actually, as it is computationally not solvable without parsing the whole
scene, it cannot trace include file names which are assembled using an
expression.

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Jan Walzer wrote:
> 
> "Warp" <war### [at] tagpovrayorg> wrote:
> > >> "atan2d" is no POV-Ray keyword in any official version.
> >
> > > Hmm, it's listed in "7.10.1  Float functions and macros" in the docs as a
> > > function like atan2 that uses degrees.
> >
> >   That doesn't make it a keyword.
> >
> >   Only keywords are highlighted, not identifiers defined somewhere in some
> > include file.
> 
> Aside from the fact, that this _IS_ defined in an include, and that
> this will probably called a feature request:
> Wouldn't it be nice, to have the Codemax-editor highlight also the
> identifiers of macros and funtions, that come in includes with a
> vanilla-distribution of POV? I mean, there _are_ powerful macros
> and functions that come with the includes, so why not make them colored?

No, please do NOT do that !

There are many useful macros (and constants ?)
defined in those include files, but some of
them are in my opinion less useful. And some
have names that I find misleading.

So if someone choose to make a set of macros/
constants of their own that happen to have the
same name, then I think it could be very con-
fusing if some of those are coloured differently.


Tor Olav

Post a reply to this message

> No, please do NOT do that !
>
> There are many useful macros (and constants ?)
> defined in those include files, but some of
> them are in my opinion less useful. And some
> have names that I find misleading.
>
> So if someone choose to make a set of macros/
> constants of their own that happen to have the
> same name, then I think it could be very con-
> fusing if some of those are coloured differently.

You're good. This tree has started by my inadvertence about atan2d. It could
be turned off if implemented. Anyway, the PovRay for Windows and it's editor
is very good! As I think, (for example) a good texture library is more
important than syntax highlighting. - Vic

Post a reply to this message

On Mon, 29 Apr 2002 10:07:53 +0200, "Vic" <let### [at] fwhu> wrote:
> As I think, (for example) a good texture library is more
> important than syntax highlighting. - Vic

what you mean ? texture browser ?
have you checked portfolio features ?
have you checked screen.inc as universal
include file for texture developing ?

follow-ups to povray.general

ABX

Post a reply to this message