POV-Ray

The Persistence of Vision Raytracer (POV-Ray).

This is the legacy Bug Tracking System for the POV-Ray project. Bugs listed here are being migrated to our github issue tracker. Please refer to that for new reports or updates to existing ones on this system.

Attached to Project: POV-Ray
Opened by Mike H - 2010-06-06
Last edited by Jim Holsenback - 2010-12-20

FS#120 - More library paths, wildcards

20 library paths is a bit small given the sheer number of include files I’ve collected over the years. An increase in the number, and/or the ability to include wildcards in the search path, would be great.

Closed by  Jim Holsenback
Monday, 20 December 2010, 13:27 GMT
Reason for closing:  Fixed
Grimbert Jérôme commented on Thursday, 10 June 2010, 12:16 GMT

Agreed.
An open-ended handling of library path would get my vote.
Regular expression would not: too easily a problem (how do you sort the result...)

Mike H commented on Sunday, 20 June 2010, 00:04 GMT

Not regular expressions (too powerful!), but the normal * and ? wildcards used in (in this case MS-DOS) command-lines.

Mike H commented on Sunday, 20 June 2010, 00:05 GMT

Though something more structured like an XML file would be OK too. (There's only so much you can do in an INI file...)

Thorsten Fröhlich commented on Sunday, 20 June 2010, 06:03 GMT

There is no limit of 20 paths in POV-Ray 3.7 core code. This report seems to be platform specific. Please quote the exact error message and which platform you are using!

Mike H commented on Sunday, 20 June 2010, 08:23 GMT

I'm just repeating what the docs say.

Jim Holsenback commented on Monday, 28 June 2010, 17:01 GMT

The documentation does indeed say so:
Library Paths

I'm POV-Ray crippled at the moment, but when back in business I'll check unix/link platform (I'll just add legitimate, but not necessary path names) ... If someone (Mike) would verify on the windows platform. If there is NO LIMIT, I'll change the documentation appropriately.

Thorsten Fröhlich commented on Monday, 28 June 2010, 17:15 GMT

To clarify: The correct documentation should be that there is no limit. Or basically, the documentation should just not mention a limit, it is not necessary to say there is no limit.
There is no intentionally coded limit in any of the platform specific versions of POV-Ray. That is why I moved this from Compatibility Issue to Documentation. Any limit imposed would be a bug. Thus, all the places in the docs that mention this limit need to be fixed, probably by just removing them.

Jim Holsenback commented on Monday, 28 June 2010, 18:13 GMT
To clarify: The correct documentation should be that there is no limit.

Good then no testing required. I found Library_Path mentioned 9 times, of those, 7 were reference to:

Lirary Paths and it's been changed.

The 2nd one: Command Line Switches (4th paragraph) mentions a limit of 10 ... does this refer to limit of +L on the command line, or should I change that one as well.

Your silence ... and it remains the same.

Thorsten Fröhlich commented on Monday, 28 June 2010, 18:38 GMT

Technically, there is no difference between POV-Ray's treatment of command-line and INI file items. Hence, all limits apply (or do not apply respectively) to both. In short, no limit on the command-line either in this case.

Mike H commented on Wednesday, 30 June 2010, 00:46 GMT

There's a 256 character limit in Windows/DOS command-lines IIRC. Not sure if it's worth mentioning.

Thorsten Fröhlich commented on Wednesday, 30 June 2010, 05:33 GMT

"There's a 256 character limit in Windows/DOS command-lines IIRC. Not sure if it's worth mentioning."

There has been no such limit since Windows 95.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing