POV-Ray : Newsgroups : povray.beta-test : Visual Studio 2017 or 2019 : Re: Visual Studio 2017 or 2019 Server Time
21 Sep 2021 13:38:40 EDT (-0400)
  Re: Visual Studio 2017 or 2019  
From: clipka
Date: 19 Jun 2021 20:37:08
Message: <60ce8db4$1@news.povray.org>
Am 19.06.2021 um 21:46 schrieb Mr:

> /// @def POVRAY_IS_BETA should stay commented right ? (these @ are some comment
> convention or actual code? sorry, I know nothing about compiled languages yet
> :-)

To a C++ compiler, anything from `//` to the end of the line is a 
comment (same deal as in POV-Ray's scene language), period. Tampering 
with them will not affect the compiled program.

The `///` and `@def` are indeed comment conventions, namely of a tool 
named Doxygen.

Doxygen is a tool similar to Javadoc, which can build HTML pages listing 
all of the software's functions and classes and methods and stuff. By 
its convention, any comment starting with `///` instead of `//` is 
(generally) a documentation of whatever C++ construct follows, and 
included in those HTML pages accordingly; and certain character 
sequences starting with `@` have special meaning according to that 
convention.

(Specifically, `@def POVRAY_IS_BETA` means that the following 
Doxygen-style comment block is NOT related to the next C++ construct, 
but the preorpcessor macro `POVRAY_IS_BETA` - which happens to be the 
next C++ construct, but only if it isn't commented out.)


> So I un-commented only line 114 of version.h and commented out line  128 and got
> this error when running the same test scene : "Cannot Find Home entry in
> registry (and cannot infer it)", screenshot attached.

That error is to be expected in this situation when everything works 
"properly".


Which leaves the question why we can't build nice working binaries on 
GitHub using the v142 (VS 2019) toolset.


Post a reply to this message

Copyright 2003-2021 Persistence of Vision Raytracer Pty. Ltd.