Robert
JK> My question -- how big is the PB programmer base that an
JK> advanced book will get any sales?
RP>I would imagine quite large by now. Check with Carmel and get
RP>their advice and what help they can give you. It is to their
RP>advantage. The help hawk third party installers, libraries and
RP>packages of all kinds and types. No reason they shouldn't help
RP>you but _don't_ expect a marketing survey and study as you
RP>probably won't get it.
  I'll ask them, but I don't think they'll tell me much at all.
RP>Then don't write his book - write your own book that covers the
RP>features and benefits of PowerBasic. Best Idea: Now that PB has
RP>pointers, get a good book on 'C++' and translate it to
RP>PowerBasic. Go into great detail about writing TSRs in PB. So
RP>many have problems with this feature. Include lotsa functions and
RP>procedures with multiple working examples.
  The TSR thing would be good -- include a lot of TSR support SUBs that
save screens, save the system state, stuff like that -- but I consider
that kind of thing to be programming to the metal.  I prefer high level
code that demonstrates advanced principles like hashing, sorting,
indexing, that sort of thing.  That thing tends to live longer across
platforms.  A long TSR chapter would be outdated as soon as PB went
Windows, don't you think?  A pattern matching language would last a long
time, across PBDOS/PBWIN/PBDLL/PBOS2, I would think, since it, being HL
code, would compile without many alterations in the future.
I wouldn't want to write myself into the DOS platform, in other words.
___
 X POW 1.2  On Trial X Powerline Offline reader for Windows - QWK mail reader
--- Maximus/2 2.01wb
---------------