-
Notifications
You must be signed in to change notification settings - Fork 283
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into autobuild/alpha
- Loading branch information
Showing
70 changed files
with
2,142 additions
and
1,646 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -49,6 +49,22 @@ Prior to the release of 3.7.1, the following items still need urgent attention: | |
New Features | ||
------------ | ||
|
||
- A new finish parameter, `use_alpha`, has been added to suppress highlights | ||
and reflections depending on pigment transparency. | ||
|
||
- Array elements no longer have to be of the same type. | ||
|
||
- Support for variable-size arrays has been added. | ||
|
||
- A new data container, `dictionary`, has been added to support structured | ||
storage of data. | ||
|
||
- Pseudo-dictionaries `local` and `global` have been added, allowing to | ||
specifically access local or global identifiers, respectively. | ||
|
||
- A new special pigment pattern, `user_defined`, has been added to define the | ||
pigment colour directly in terms of a set of functions. | ||
|
||
- A new pattern, `potential`, has been added to define a pattern based on the | ||
potential field of a blob or isosurface object. | ||
|
||
|
@@ -86,9 +102,6 @@ New Features | |
assignments. The main purpose is to allow macros to return a set of values | ||
rather than just a single one. | ||
|
||
- `local()` and `global()` pseudo-functions have been added to specifically | ||
refer to a local or global identifier, respectively. | ||
|
||
- The macro syntax has been extended to allow for optional parameters. | ||
|
||
- Light sources' distance-based fading can now be set to obey an inverse-power | ||
|
@@ -196,16 +209,35 @@ Fixed or Mitigated Issues Reported by Static Code Analysis | |
|
||
Coverity Scan defects targeted deliberately: | ||
|
||
- CID 967251: 'Constant' variable guards dead code | ||
- CID 967254: 'Constant' variable guards dead code | ||
- CID 967261: Logically dead code | ||
- CID 967262: Logically dead code | ||
- CID 967273: Explicit null dereferenced | ||
- CID 967296: Parse Warning | ||
- CID 967297: Parse Warning | ||
- CID 967377: Uninitialized pointer field | ||
- CID 967400: Uninitialized pointer field | ||
- CID 967410: Structurally dead code | ||
- CID 967412: Structurally dead code | ||
- CID 1129008: Division or modulo by zero | ||
- CID 1129016: Uninitialized pointer read | ||
- CID 1129017: Uninitialized scalar variable | ||
- CID 1372548: Non-virtual destructor | ||
- CID 1372552: Unchecked return value | ||
- CID 1372555: Operands don't affect result | ||
- CID 1372556: Wrong operator used | ||
- CID 1372557: Wrong operator used | ||
- CID 1372558: Resource leak in object | ||
- CID 1372560: Logically dead code | ||
- CID 1372562: Non-array delete for scalars | ||
- CID 1372566: Unchecked dynamic_cast | ||
- CID 1372567: Unchecked dynamic_cast | ||
- CID 1372603: Resource leak | ||
- CID 1372604: Dereference before null check | ||
- CID 1372605: Dereference before null check | ||
- CID 1372606: Dereference before null check | ||
- CID 1372607: Dereference before null check | ||
- CID 1372608: Sizeof not portable | ||
- CID 1372626: Uninitialized scalar variable | ||
- CID 1372636: Uninitialized pointer field | ||
|
@@ -224,6 +256,12 @@ Coverity Scan defects targeted deliberately: | |
- CID 1372655: Structurally dead code | ||
- CID 1372656: Structurally dead code | ||
- CID 1372657: Unused value | ||
- CID 1373648: Out-of-bounds access | ||
- CID 1373649: Free of address-of expression | ||
- CID 1373651: Logically dead code | ||
- CID 1373652: Dereference before null check | ||
- CID 1373653: Write to pointer after free | ||
- CID 1373654: Use after free | ||
|
||
Coverity Scan defects eliminated in passing: | ||
|
||
|
@@ -342,6 +380,8 @@ Reported via GitHub: | |
- #49 ("Latest version from Git won't build with MS Visual Studio 2015") | ||
- #50 ("Make error in Ubuntu 14.04") | ||
- #53 ("Standard include files may mess up the language version") | ||
- #129 ("Port of FS331 - Intersection causes quadric to disappear") | ||
- #153 ("vector list trailing comma error sor lathe sphere_sweep") | ||
|
||
Reported via FlySpray: | ||
|
||
|
@@ -354,9 +394,15 @@ Reported via FlySpray: | |
- FS#316 ("inverse keyword does not work properly with fractals") | ||
- FS#317 ("problem with +D option at specific output file dimensions") | ||
- FS#318 ("method 3 (default) scattering media is too bright & causes artifacts when nested") | ||
- FS#331 ("Intersection causes quadric to disappear") | ||
- FS#336 ("#fopen w/o OPEN_TYPE crash povray (segfault)") | ||
|
||
Reported via the Newsgroups: | ||
|
||
- <[email protected]> | ||
(2002-01-21, povray.beta-test, "<1, 0, 0> + 1*t") | ||
Inconsistency in automatic scalar-to-vector promotion. | ||
|
||
- <[email protected]> | ||
(2014-08-12, povray.binaries.images, "unexplained") | ||
Precision issue led to `<1,1,1>.grey` not evaluating to 1 on sone systems. | ||
|
@@ -414,6 +460,10 @@ Reported via the Newsgroups: | |
(2016-08-17, povray.binaries.scene-files, "Wrong normal direction on triangle{ }s") | ||
Bug in flat trianges that could cause interior_texture to show on the wrong side. | ||
|
||
- <[email protected]> | ||
(2016-10-20, povray.programming, "Re: solving polynomials") | ||
Misplaced `break` in polynomial solving code. | ||
|
||
Reported via Windows Crash Reports: | ||
|
||
- crash report #???, dump file #988 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -54,7 +54,7 @@ namespace pov_base | |
|
||
#else | ||
|
||
#error TODO! | ||
#error "TODO!" | ||
|
||
#endif | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.