PW> What sort of pointers does large model use?  Far?
PE> Yes.

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

Which is longer - a piece of string, or 1 second?

PW> Does huge model use huge pointers?
PE> I don't know what a huge pointer is, although I can take a guess.

PW> I guess that's another Borland-only thing, perhaps?

It's a DOS thing.  I am not a DOS expert, I "never" do
DOS-specific programming.

PE> Then I realised that it was a complete yank.  Why is get_variable_x()

"wank" actually.

PE> OK, but x is not?  I then started using global variables freely,

PW> I don't quite understand "but x is not" -- where did
"x" come into this?  I
PW> don't follow... <%-\

If I need a variable that has say, the number of lines on my screen, an I
want to refer to it in lots of places, then I can do one of two things:

1. Create a global variable x, ie "int x;" and "extern int x;".

2. Create a function "int get_variable_x()" and "void
put_variable_x(int)".

Understand?

PE> although that later got replaced by PDS0004.TXT (available for FREQ

PW> What's in that file (I wanna know before I FREQ it :)

Object-oriented C.

PE> from 3:711/934).  I questioned someone giving a lecture once on
PE> something similar to structured programming, and asked him what was
PE> wrong with global variables over global functions, and the reaction I
PE> got was amusing.  At the end of the lecture, he asked us what we were

PW> Please give details of the abovementioned reaction... ;)

Well, it was quite obvious he'd never actually thought about it himself,
and now that he had to, he was in a pickle.

PE> have a different strategy in mind for when your customer says "This is
PE> a great program, here's $50,000, go and stick it on that computer over
PE> there (the one with 67-bit longs, integers and chars).

PW> Does any platform in existence have 67-bit data types?  

I don't know.  I do know they have ones with 36-bit integers, and 64-bit
integers.  If I was betting, I would lay odds that there is no machine with
a 67-bit integer.  Why do you ask, anyway?

BTW I was reading a
PW> little and read something about the "Harvard
architecture".  It is supposed
PW> to be a linear addressing system (as opposed to segmented architectures).  
PW> I presume that most portable C code would still work on those machines?

Linear addressing is what you get when you write OS/2 32-bit programs, or
DOS 32-bit-extended programs, or Unix etc etc.  And of course portable C
code works on them.

PW> been a tad confused about that term.  BTW what non-portable functions and
PW> stuff exist in Turbo C++ v3.0 that I should be aware of?
PE> Billions and billions of them.  What you should do is FREQ ANSI_C.*

PW> I hope you're not the SysOp {at} 3:711/934...

I am at the moment, but there's a possibility that David Nugent will get me
kicked out of fidonet, although the chances are he won't.  Why do you ask?

PE> from 3:711/934 and then use THAT as your reference INSTEAD of the
PE> Turbo C++'s manuals.

PW> I don't use the manuals.  I use the online help -- much easier to copy and
PW> paste examples ;)

ANSI_C can be online too.  BFN.  Paul.
@EOT:

---