[futurebasic] FBII->3 Source Conversions Success!

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : September 1999 : Group Archive : Group : All Groups

From: Mel Patrick <mel@...>
Date: Sat, 18 Sep 1999 18:57:59 -0700
>jonathan said,
>
>function even under 8.6, this doesn't worry me. The problem is not with
>FB^3, I hasten to add, but with me!

I just managed to convert one of my smaller projects (3 include 
files, one global and a main) and got it working in FB3! Aw the sweet 
smell of success.

One of my errors was naming the DIM RECORD and DIM RECORD END with 
the same variable. It didn't flag it as an error during compiles or 
anything else (contrary to what the conversion docs say) and it let 
me shove stuff into the records in a function, but once outside of 
the function it was gone. Somplace. Very far away. Never to be seen 
again.

I compiled my corrected app as a 68K application (since it has a fair 
bit of inline assembler in it). It works exactly the same as the 
original FBII project. But...well it needs to go on a serious size 
diet.

    FBII App                  FB3 App
Size : 203,652            Size : 330,552

The FB3 compiled app runs....slower. But only during the display 
portion of the program. Ie. drawing a bunch of data text lines to a 
window. FBII is significantly faster. Perhaps the inline asm code 
slows it down slightly (anyone got a native PPC TRUNCSTRING laying 
around?).

So how do I cut 126,900K from the finished FB3 application?

FB3 took it on itself to change the "suggested memory size" to a 
number I didn't put in my size resource. Matter of fact I don't know 
where it found the number but its almost twice the suggested size 
FBII used. So why put a size in a resource if the compiler is going 
to make its own suggestions? Odd bird this one.

I know there's a lot of beta users here, so how do you get the 
references to your functions like the old project manager did? i.e. 
click on a function name and the next reference to it pops up in the 
editor window.

Do you actually "need" all that extra function stuff in the FBIIrntm 
header file?
Or do you just need the library references?
Whats the difference between the lite, regular or fat free run time?
Is there a list of what ToolBox commands the compiler supports (help 
only has a few)?
How come in a compiled PPC app only, the main part of the code 
doesn't end up in the datafork as other compiled languages do? And 
does anyone see this as a problem?
If the compiler is going to write in its own resources, can we get a 
list of them so we don't try and create the same ones?
Is there a way to get rid of that blue background in the editor 
window but keep the styled text?
How come window names can't be longer than about 6 or 7 characters? 
Mine all get chopped off. And it changed something in my OS since ALL 
my windows won't go beyond 6 or 7 characters now. I hope restarting 
will fix it.

Disclaimer, I am not bashing FB3. Rather to the contrary, I think its 
going to be great in future releases. But it's got one mean learning 
curve for us FBII vets and the sooner I get a handle on it and manage 
to learn to stay out of its way, the better. Which means I get to ask 
a lot of dumb questions about how it works so I can best use it for 
my own programming style.

Mel Patrick
mel@...