![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
I have applied David Sharp's bugfixes for
FastMacroPatch and cabs2, creal, and cimag
to the MegaPov 0.4 sourcecode zip file.
Thanks David.
Stu.
--
==================
MegaPov for MS-DOS
at www.sgib.co.uk
==================
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
I think he said: "This is an inelegant way to go about it, but arf".
Shouldn't the povray code be elegant, well made, high-quality,
easy-to-understand, portable, modular and in any sense almost perfect?
Is it good to content to solutions that are more a 'hack' than a real
fix?
This is not a flame, just asking... :)
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
I never claimed to understand the code. I'm just providing the 'fixed'
source so that everybody else can compile it and use it. If a 'hack' works,
that's usually good enough for most people who just want it to work. When
somebody writes a "proper" fix for a bug, it will probably get incorporated
into the next version anyway so the 'problem' goes away!
Stu.
"Nieminen Juha" <war### [at] punarastas cs tut fi> wrote in message
news:38993b51@news.povray.org...
> I think he said: "This is an inelegant way to go about it, but arf".
>
> Shouldn't the povray code be elegant, well made, high-quality,
> easy-to-understand, portable, modular and in any sense almost perfect?
> Is it good to content to solutions that are more a 'hack' than a real
> fix?
> This is not a flame, just asking... :)
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
I never claimed to understand the code. I'm just providing the 'fixed'
source so that everybody else can compile it and use it. If a 'hack' works,
that's usually good enough for most people who just want it to work. When
somebody writes a "proper" fix for a bug, it will probably get incorporated
into the next version anyway so the 'problem' goes away!
Stu.
"Nieminen Juha" <war### [at] punarastas cs tut fi> wrote in message
news:38993b51@news.povray.org...
> I think he said: "This is an inelegant way to go about it, but arf".
>
> Shouldn't the povray code be elegant, well made, high-quality,
> easy-to-understand, portable, modular and in any sense almost perfect?
> Is it good to content to solutions that are more a 'hack' than a real
> fix?
> This is not a flame, just asking... :)
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Nieminen Juha <war### [at] punarastas cs tut fi> wrote...
> I think he said: "This is an inelegant way to go about it, but arf".
>
> Shouldn't the povray code be elegant, well made, high-quality,
> easy-to-understand, portable, modular and in any sense almost perfect?
> Is it good to content to solutions that are more a 'hack' than a real
> fix?
Yes, but for a temporary fix so that things work at least closer to the way
they should, it is OK. Neither MegaPov nor the official version will use
this hack, but if DOS people want to use it for now, they can.
Be aware that an elegant solution does exist, though: just open the file
for binary read mode instead of text read mode. This fixes basically all
CRLF problems.
-Nathan
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
I have now removed the 'hack' and applied the 'proper' fix.
Thanks to David Sharp for sending me the patched tokenize.c source.
Stu. www.sgib.co.uk
"Nathan Kopp" <Nat### [at] Kopp com> wrote in message
news:389b4622@news.povray.org...
>
> Nieminen Juha <war### [at] punarastas cs tut fi> wrote...
> > I think he said: "This is an inelegant way to go about it, but arf".
> >
> > Shouldn't the povray code be elegant, well made, high-quality,
> > easy-to-understand, portable, modular and in any sense almost perfect?
> > Is it good to content to solutions that are more a 'hack' than a real
> > fix?
>
> Yes, but for a temporary fix so that things work at least closer to the
way
> they should, it is OK. Neither MegaPov nor the official version will use
> this hack, but if DOS people want to use it for now, they can.
>
> Be aware that an elegant solution does exist, though: just open the file
> for binary read mode instead of text read mode. This fixes basically all
> CRLF problems.
>
> -Nathan
>
>
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |