🚀 go-pugleaf

In article <28ps6t$9um@access.digex.net>,
kbennett@access.digex.net (Keith R. Bennett) writes:
>
>I appreciate your response.  It is true that a couple of my questions
>were general to OS/2 and not specific to C/Set++.
>
>You excluded a large area of questions.  Tell me, then,
>what *is* included in the scope of their expertise?  I hope it's
>more than how to install it, open a project, etc.

Certainly.   I realize that there's a grey area between a compiler
question, and an operating system question.   Hopefully, our support
people can answer all the compiler questions, and at least halfway
into the grey of OS questions.  As I said before, if you have specific
examples of questions you feel were answered poorly, send them to me
off-line and I'll see if I can help.

I think a simple test you can answer yourself is whether or not you'd
have the same question if you were using another compiler.   For
example, creating a semaphore, using shared memory, creating a
PM container, registering a WPS class -- none of these are really
compiler related.  As long as the compiler generates correct code(!),
all we do is call the relevant OS function, and return the result to
you.

Please don't assume that our support line will reject OS questions
out of hand.  If they can, they'll answer it.   If they can't, they'll
route the question down to the OS/2 support area.   In either case,
you probably won't get an answer as quickly as you would for a
question about the compiler.

>I may not be typical, but when I see that tech support is offered
>for a compiler and toolkit, I assume that that support extends to
>technical issues and not just compiler operation.  I'm not asking
>to be taught, but answering a few questions would be helpful.

Again, without knowing the details of your questions, it's difficult
to comment.  Of course our support team answer technical questions.
The problem is how far do we (or should we) go?   Would you expect
Borland to be able to help you if a DOS interrupt you call (with
their compiler) doesn't work?  If a runtime call fails, that's one
thing -- but if it's the OS, there's not much the compiler vendor
can do.

> ....
>Well, I should acknowledge that C/Set++ may be among the first
>(maybe the first?) IBM product I know of to offer Internet support
>at all, and that is commendable.  But, as I mentioned in the letter,
>C/Set++ support is lacking, and that is the primary tool I use to
>develop OS/2 applications.

I don't disagree.   Our business is hinged on the success of OS/2 even
more than yours is, so I want to see all the help developers need
available via internet.   Your letter has not been ignored, and I'm
sending a copy of it to several people internally who may be able to
do something about it.  In the meantime, all I ask is for you to be
aware of the difference between compiler support and OS support.

Thanks for your feedback.   -tim