Documentation error: abapp.wsp not mentioned in phAb documen

Under “Generating, Compiling, and Running Code” for phAb,
there is a list of the files which should be placed under
CVS control. It does not include “abapp.wsp”, but deleting
“abapp.wsp” seems to lead to problems.

What is in “abapp.wsp”, anyway? There’s no reference to it
in the phAb documentation, but phAb generates and uses it.

John Nagle
Team Overbot

John Nagle <nagle@downside.com> wrote:

Under “Generating, Compiling, and Running Code” for phAb,
there is a list of the files which should be placed under
CVS control. It does not include “abapp.wsp”, but deleting
“abapp.wsp” seems to lead to problems.

What kind of problems?

Here at QSSL, we don’t put it in CVS for most apps, and as far as I
know, it’s not causing any problems. PhAB was specifically designed to
deal with a stale abapp.wsp after you check out changes to the rest of
the files.

What is in “abapp.wsp”, anyway? There’s no reference to it
in the phAb documentation, but phAb generates and uses it.

It preserves the layout of your modules in PhAB’s window (the
“WorkSPace”). Not putting it in CVS allows you to preserve your layout
without inflicting it on everybody else who works on the same
application.

I had a recompile fail with error messages when
“abapp.wsp” wasn’t present, but I’d have to go to some
trouble to replicate the problem.

If “abapp.wsp” had been documented, this wouldn’t have
been a problem.

John Nagle

Wojtek Lerch wrote:

John Nagle <> nagle@downside.com> > wrote:

Under “Generating, Compiling, and Running Code” for phAb,
there is a list of the files which should be placed under
CVS control. It does not include “abapp.wsp”, but deleting
“abapp.wsp” seems to lead to problems.


What kind of problems?

Here at QSSL, we don’t put it in CVS for most apps, and as far as I
know, it’s not causing any problems. PhAB was specifically designed to
deal with a stale abapp.wsp after you check out changes to the rest of
the files.


What is in “abapp.wsp”, anyway? There’s no reference to it
in the phAb documentation, but phAb generates and uses it.


It preserves the layout of your modules in PhAB’s window (the
“WorkSPace”). Not putting it in CVS allows you to preserve your layout
without inflicting it on everybody else who works on the same
application.

John Nagle <nagle@downside.com> wrote:

I had a recompile fail with error messages when
“abapp.wsp” wasn’t present, but I’d have to go to some
trouble to replicate the problem.

That’s very surprising. The compiler knows nothing about that file.
It’s never mentioned in the Makefile, and .wsp is not one of the
extensions that make understand by default. It’s only ever looked at by
PhAB.

If it happens again, I would be very interested in seeing the compile
command and its output.

If “abapp.wsp” had been documented, this wouldn’t have
been a problem.

With abapp.wsp undocumented, it shouldn’t have been a problem, either… :wink:

Still, it probably wouldn’t be a bad idea to mention the file in the
docs.