On 15 Oct 96, Rowan_Crowe wrote to Paul Wankadia --



You again :)



 PW> What sort of pointers does large model use?  Far?  Does huge model use

 PW> huge pointers?



[stuff deleted]



Thanks.



 R > Huge pointers are far pointers which are 'normalised' (ie: 0xb000:8000

 R > is normalised to 0xb800:0000) before each access to avoid segment

 R > overwrap, meaning you can address more than 64k with them. Due to this



But isn't 0xB800:0000 the same as 0xB000:8000 -- both turn out to be 0xB8000,

don't they?



 R > extra conversion overhead, you should only use the huge model if you

 R > really have to. (In general, very broadly, the smaller the model, the

 R > less overhead and memory used).



I read that far pointers are very slow -- is that true?



 PW> I was told (prior to this) that global variables should be cut down as

 R > Presumably global means a static variable, accessable across different



"Global" as in not local to a function...



 PW> BTW the way you said "global functions" -- is it possible
to declare

 PW> (this is a silly question) a "local" function, accessible
from inside

 R > Why would you want to do that? It's inline code then. :)



Just wondering, cuz he said GLOBAL functions as if there was such a thing as

LOCAL functions :)  BTW don't knock inline code 



 PW> always been a tad confused about that term.  BTW what non-portable

 PW> functions and stuff exist in Turbo C++ v3.0 that I should be aware of?

 R > Oh, heaappppssss. The online help in BCC 3.1 shows quite clearly how



Heaps?  Going on your example below, that's not a bad pun -- for you :>



 R > portable things are. For example, heapwalk:

 R >   Portability:

 R >   . DOS . UNIX . Windows . ANSI C . C++ Only .

 R >   . Yes .      .         .        .          .

 R > Obviously not very portable at all. :)



Neither is hi-ASCII in FidoNet :>



 PW> you haven't already replied about this, what EXACTLY does "extern

 PW> \"C\"" do and mean???

 R > The way I understand it, that's just a wrapper for C++... you see it a

 R > lot in header files:



 R > void _Cdecl _FARFUNC __assertfail( char _FAR *__msg,



I presume this _Cdecl does much the same thing?  BTW what do they actually

do?  I'm guessing they generate special code for calling and for variables?



 R > If you're just doing a C compile, the 'extern "C" {' and
'}' is never

 R > seen by the compiler.



I guessed as much...



Chow.



Junyer Hakker.



--- PPoint 2.00