This is about Windows version of POV-Ray 3.6 beta 2 on Windows 2000.

First create a file "temp.dat" that has only one numerical value in it 
("0", without quotes for example) 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"'. In both cases I can read the next in 
the message window:

"File context (5 lines):
0
Parse error: End of file reached but #end expected".

Now, if I place a comma 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 declaration. The only difference is 
that macro is not used.

#declare A = 0;

#fopen File "temp.dat" read
#read(File, A)
#fclose File

Also, if the "temp.dat" file does not exist POV-Ray gives "Runtime 
Error!" and exits instantly.

Severi Salminen

Post a reply to this message

In article <40573a61$1@news.povray.org> , Severi Salminen 
<sev### [at] NOT_THISsibafi>  wrote:

> First create a file "temp.dat" that has only one numerical value in it
> ("0", without quotes for example) in the same directory as the scene
> below.

Is the number followed by a newline?

    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

Thorsten Froehlich wrote:

  >>First create a file "temp.dat" that has only one numerical value in it
>>("0", without quotes for example) in the same directory as the scene
>>below.
> 
> 
> Is the number followed by a newline?

It doesn't seem to matter: it crashes with or without a newline (when 
the macro is being used).

Severi S.

Post a reply to this message

I'm experiencing some similar problems connected to file I/O in 3.6b2 on
Mac OS (3.6b2 build 189, Mac OS X 10.3.2, PPC G4 867MHz, 768MB RAM).

The minimal scene is the following, the (slightly modified) example from
the docs (2.1.2.3.3):

#fopen MyFile "mydata.txt" read
#while (defined(MyFile))
  #read(MyFile, Var1, Var2, Var3)
  #debug concat(
    str(Var1, 0, 3), " ",
    str(Var2, 0, 3), " ",
    str(Var3, 0, 3), "\n"
  )
#end

When mydata.txt doesn't exist, I get "Possible Parse Error: Could not find
file 'mydata.txt' File test.pov line 1" in the Messages window, and the
Render Progress window indefinitely displays "00:00:00 Reclaiming memory"
with a barber pole. When I click "Stop", the Message window says "Stopping
render, please wait...", but nothing else happens - I have to quit POV-Ray
and restart it to get it into a working state again.

When mydata.txt contains N comma-terminated floats, and possibly one more
without trailing comma, the first (floor(N/3)) #reads succeed and the
corresponding debug messages appear, afterwards the Messages window says
"Parse Error: End of file reached but #end expected. File test.pov line 3"
and POV-Ray crashes shortly after (I can send the crash log if it helps).

By the way, #read and #write are not syntax-colored in the editor window.

 -Christian

Post a reply to this message

Severi Salminen wrote:
> This is about Windows version of POV-Ray 3.6 beta 2 on Windows 2000.

The same comma/macro related bug(s) exist (excluding the last bug when 
the file doesn't exist - that is handled now correctly) also in Windows 
version of POV-Ray 3.6 beta 3.

Severi S

Post a reply to this message

In article <407bcb7f$1@news.povray.org> , Severi Salminen 
<sev### [at] NOT_THISsibafi>  wrote:

> Severi Salminen wrote:
>> This is about Windows version of POV-Ray 3.6 beta 2 on Windows 2000.
>
> The same comma/macro related bug(s) exist (excluding the last bug when
> the file doesn't exist - that is handled now correctly) also in Windows
> version of POV-Ray 3.6 beta 3.

I am missing the context.  Please post a small example for what exactly is
still wrong.  Only the example is important.

    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

Thorsten Froehlich wrote:
>>The same comma/macro related bug(s) exist (excluding the last bug when
>>the file doesn't exist - that is handled now correctly) also in Windows
>>version of POV-Ray 3.6 beta 3.
> 
> 
> I am missing the context.  Please post a small example for what exactly is
> still wrong.  Only the example is important.

Sorry, I was referring to my previous report. It is included below:

-------------------

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