 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The same bug seems to be still alive in Pov-Ray for Windows 3.6 beta 4:
First create a file "temp.dat" that has only one numerical value in it
("0", without quotes, newline doesn't matter) in the same directory as
the scene below. When I try to render the scene, I get 'The instruction
at ".." referenced memory at "..". The memory could not be "read"'. This
is the scene:
#declare A = 0;
#macro Read_Data()
#fopen File "temp.dat" read
#read(File, A)
#fclose File
#end
Read_Data()
If the first line (#declare A=0;) is commented out I get the same error
expect '...could not be "written"'.
Now, if I place a comma "," (no quotes) after the "0" in temp.dat the
scene parses normally in both cases.
Interestingly, the next scene renders normally even _without_ the comma
mentioned above - also without the first declaration. The only
difference is that macro is not being used.
#declare A = 0;
#fopen File "temp.dat" read
#read(File, A)
#fclose File
Severi S.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <40816260$1@news.povray.org> , Severi Salminen
<sev### [at] NOT_THISsiba fi> wrote:
> The same bug seems to be still alive in Pov-Ray for Windows 3.6 beta 4:
As you reported it a day before the beta 4 was made, what chance could we
have had to fix it? And as the release notes do not claim that it was fix,
this is hardly unexpected...
Thorsten
____________________________________________________
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> > The same bug seems to be still alive in Pov-Ray for Windows 3.6 beta 4:
>
> As you reported it a day before the beta 4 was made, what chance could we
> have had to fix it? And as the release notes do not claim that it was
fix,
> this is hardly unexpected...
That was a bit unnecessary. I'm not making _any_ assumptions on how
fast/slow or often/seldom you correct bugs or what "chances" you have fixing
a certain bug, I make no assumptions on how hard/easy the bugs are to fix
nor do I make any assumptions on what things are changed between various
beta versions that might affect the bugs. I have no way knowing anything
about those things. I simply reported that the bug was still present in the
newest beta - nothing more, nothing less. I thought this was the purpose of
public beta testing and I still think.
Regards,
Severi S.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thanks for reporting this. We'll ensure it is fixed.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
