(Continued from previous message)

do anything you want, but you better know what you are doing coz if
you stuff up, it can fang you severely because it makes very little
attempt to protect you from your own stupidity. It does warn you now
more than it used to, but some of its techniques like pointers are
extremely dangerous if you dont know what you are doing. Particularly
when used with an OS which doesnt try very hard to protect itself
from an app which is running barefoot thru the system.

BL> The restrictions in VB are actually protections.

Yeah, often.

RS> PKT2QWK is plenty complex enough to see the problem.
RS> Even a PKT joiner can be, tho usually isnt.

BL> I wrote a joiner first, and then the twitter, and the converter
BL> is not much different. All it adds is a struct to create the QWK
BL> header. It's no big deal, Rod. It has to be, if I can make it work.

Dont agree with that either |-)

Thats another area where software is just about unique, it really is
possible to just focus on the detail and work it out, there is almost
never anything which is at all hard to understand. The only real problem
is with people who just cant handle the mass of detail and drown in it.

--- PQWK202