Re: [Fractdev] 2 probs w the 20.99.8 Fractint 4 Windows

21 Apr 2008

      --------- Tim Wegner said: --------------
...
Any hardcoded assumption that int = 16 bits would have created a 
problem with the Linux port. We generally tried to stick to short or 
long when the size mattered and avoid int except where the size 
didn't matter.
Would someone with a recent version of the Linux port please try 
and create Jim Muth's FoTD for 8/4/8 from his parameter/formula 
file and report the results?  

[This is the FoTD that gives a black screen after 'calculating' 
the 640x480 image essentially instantaneously per the <tab> 
command.]

Thanks!

Here's Jim's 8/4/8 FoTD parm file:

START PARAMETER FILE=======================================

Fierce_Fiery_Scene { ; time=0:07:37.14-SF5 on P4-2000
  reset=2004 type=formula formulafile=allinone.frm
  formulaname=MandelbrotBC3 function=ident passes=1
  center-mag=-0.6634403428163981/-1.406626216391897/\
  1.641796e+009/1/100/0 params=1.41421/0/4/0 float=y
  maxiter=1500 inside=0 proximity=0.002
  outside=fmod periodicity=10
  colors=0003B`3B`3Ba3Ba4Ba4Ba4Bb4Bb4Bb4Bb4Ac4Ac4Ac5\
  Ac5Ad5Ad5Ad5Ad5Ae5Ae5Ae5Ae36h48f5Ae5Bd6Dc6Eb7Ga7H`\
  8JZ9LY9MXAOWAPVBRUBSTCURDWQDXPEZOE_NFaMFbLGdJHfIHg\
  HIiGIjFJlEIoCJnDJmDJmDKlDKlDKkDLkDLjDLjDMiDMiDMhEN\
  hENgENgEOfEOfEOeEPeEPdEPdEQcEQcFQbFRbFRaFRaFS`FS`F\
  S_FT_FTZFTZFTZFU`GVaHWbHXcIYeJZfJ_gK`hKaiLbkMclMdm\
  NenNfpOgqPhrPisQjtQkvRlwSmxSnyTmzUnzTnySnxSnwRnvQn\
  uQntPnsOnrOnqNnpMnoMnnLnmKnlKnkJnjIniInhHngGnfGneF\
  ndEncEnbDt_6r`9paBnaDlbGkcIicKgdNedPdeRbfU`fWZgY_j\
  Z_l`Yg_WbYUYXSTVQOUOJSLFQMERMERMESNESNESNDTNDTODUO\
  DUODUODVPCVPCWPCWPCWQCXQCXQBYQBYRBYRBZRBZRBZRA_RA_\
  RBZSCYTDXVDWWEVXFUYFT_GS`HRaHQbIPdJOeJNfKMhLLiMKjM\
  JkNImOHnPGpQFrREtSDvTCxUBzUBzUAxTAvSAtRAsQAqQApPAo\
  OAnOAmNAkMAjMAiLAhKAgKAeJ9dI9cI9bH9aG9`G9ZF9XE9VE9\
  TD9RC9PC9NB9LAAJ9BIACHADGAEIAFKAGMAHNAIOAJPBKQBLRB\
  MSBNTBOUBPVBQWBRWCSXCTXCU }

frm:MandelbrotBC3   { ; by several Fractint users
  e=p1, a=imag(p2)+100
  p=real(p2)+PI
  q=2*PI*fn1(p/(2*PI))
  r=real(p2)+PI-q
  Z=C=Pixel:
    Z=log(Z)
    IF(imag(Z)>r)
      Z=Z+flip(2*PI)
    ENDIF
    Z=exp(e*(Z+flip(q)))+C
  |Z|<a }

END PARAMETER FILE=========================================

 - Hal Lane

#########################
# hallane@earthlink.net <mailto:hallane@earthlink.net>  #
#########################
...
-----Original Message-----
From: fractdev-bounces@mailman.xmission.com
[mailto:fractdev-bounces@mailman.xmission.com]On Behalf Of Tim Wegner
Sent: Monday, April 21, 2008 11:07 PM
To: Fractint developer's list
Subject: Re: [Fractdev] 2 probs w the 20.99.8 Fractint 4 Windows
Size of various types is very fundamental, and has to be well 
understood by programmers using C. By and large, for Fractint it was. 
The Microsoft DOS compiler had:
short = int = two bytes
long = four bytes
Until recently, most other systems (e.g. Unix/Linux) had:
short = two bytes
int = long = four bytes
Until the advent of 64 bit cpus, the most reliable of these were 
short and long, which you could count on as being 16 and 32 bits
It is unlikely to gain much to search for "2" :-) The parser pretty 
much had a different set of authors from the rest of Fractint, of 
varying skill and experience - Mark Peterson, George Martin, and 
Chuck Ebbert. I've studied the code enough to understand it and added 
some functions.
Any hardcoded assumption that int = 16 bits would have created a 
problem with the Linux port. We generally tried to stick to short or 
long when the size mattered and avoid int except where the size 
didn't matter.
Tim
_______________________________________________
Fractdev mailing list
Fractdev@mailman.xmission.com
http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev