willett wrote:
Frank Heckenbach:
Apologies for duplication, but you replied to subsequent messages and a copied part of this one, so I'm guessing you didn't see the questions below. I'm responding to your complex (to me) message about ncurses types and automatic configuration for multiple hosts. Any verification or correction of my approach would be appreciated.
Earlier Message from willett@udel.edu:
Frank, thanks very much for all your advice. I'm trying to get up to speed here.
Ok, based on your message, I'm now using: MedCard for chtype in ncurses.h (assuming typedef unsigned long chtype) CBoolean for "bool" in ncurses.h (assuming typedef unsigned int bool) CBoolean for an "int" which contains only TRUE or FALSE CInteger for an "int" used as an integer (on older gpc I use "integer") tacs now uses index of char128 = #0 .. #127
The c translation types are very useful! Thanks.
I hope not to bore you with my yakitty yak.
First, is MacOSX a POSIX compliant operating system ?? On linux, you type the command " printenv | more " and you will learn a lot about your system.
Second, I believe the CString type is important. Your interface (like FPC) uses the PChar type. PChar works but is ambiguous, CString is not ambiguous. NCurses will use a lot of CStrings.
The rest, I don't know. Just plain ncurses.pas works for me. The only programming snag is GPC demands that a function is treated as a function. FPC lets a function pass as a procedure.
Good work. Important, too.
Thanks, Rick.