 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
any idea how to add to string or write into file chr(0) ?
it is the only limit to write binary files :-(
(treat it as feature request if it is not possible)
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
> any idea how to add to string or write into file chr(0) ?
> it is the only limit to write binary files :-(
>
> (treat it as feature request if it is not possible)
>
> ABX
"\0" writes the null character.
--
signature{
"Grey Knight" contact{ email "gre### [at] yahoo com" }
site_of_week{ url "http://digilander.iol.it/jrgpov" }
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Skiba <abx### [at] babilonorg> wrote:
> any idea how to add to string or write into file chr(0) ?
> it is the only limit to write binary files :-(
As you might know, you are not supposed to be able to write binary files...
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 28 Feb 2002 12:14:05 +0100, "Thorsten Froehlich" <tho### [at] trfde>
wrote:
> > any idea how to add to string or write into file chr(0) ?
> > it is the only limit to write binary files :-(
>
> As you might know, you are not supposed to be able to write binary files...
Yes, I suppose there wasn't such idea in design of POV. Anyway I wan't try to
write DF3 file and use it within the same parse. It's just the 3d version of
image function and I found it useful in my current task.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 28 Feb 2002 11:10:41 +0000, Grey Knight <s16### [at] namtarqubacuk>
wrote:
> "\0" writes the null character.
#write(DF3,"\0" <----ERROR
Parse Error: Illegal escape sequence in string.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Oh dear. What exactly was \0 put in for if you can't write it to a file?
It's not like it makes any sense to put it in a text string...
>
> On Thu, 28 Feb 2002 11:10:41 +0000, Grey Knight <s16### [at] namtarqubacuk>
> wrote:
> > "\0" writes the null character.
>
> #write(DF3,"\0" <----ERROR
> Parse Error: Illegal escape sequence in string.
>
> ABX
--
signature{
"Grey Knight" contact{ email "gre### [at] yahoocom" }
site_of_week{ url "http://digilander.iol.it/jrgpov" }
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 28 Feb 2002 12:03:09 +0000, Grey Knight <s16### [at] namtarqubacuk>
wrote:
> Oh dear. What exactly was \0 put in for if you can't write it to a file?
> It's not like it makes any sense to put it in a text string...
From documentation: "Depending on what platform you are using, they may not be
fully supported for console output. However they will appear in any text file
if you re-direct a stream to a file."
When I tried it with #warning it produced the same error message.
So, does it means bug ? Should I repost it into beta-test ?
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Skiba <abx### [at] babilonorg> wrote:
> From documentation: "Depending on what platform you are using, they may not be
> fully supported for console output. However they will appear in any text file
> if you re-direct a stream to a file."
>
> When I tried it with #warning it produced the same error message.
>
> So, does it means bug ? Should I repost it into beta-test ?
Well, whatever the documentation wants to say with this, a "\0" is converted
to a backslash in at least 3.1 and 3.5. It is obvious that "\0" cannot be
supported because C strings use it as terminator, so it should probably be
removed from the documentation altogether.
BTW, note that the quote you provided only talks about output streams, not the
file #write directive!
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 28 Feb 2002 13:28:42 +0100, "Thorsten Froehlich" <tho### [at] trfde>
wrote:
> Well, whatever the documentation wants to say with this, a "\0" is converted
> to a backslash in at least 3.1 and 3.5. It is obvious that "\0" cannot be
> supported because C strings use it as terminator, so it should probably be
> removed from the documentation altogether.
Worse luck!
> BTW, note that the quote you provided only talks about output streams, not the
> file #write directive!
Yes, I noticed. But of course I tested it with #warning before quoting.
The solution I choosed is to limit range to 1-255. I hope it will be
sufficient.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3c7e10ff@news.povray.org...
> As you might know, you are not supposed to be able to write binary
files...
By the way, why there is such a limitation? It should be useful.
Gleb
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
