Frequently asked questions

-Q: My program works correctly in the interpreter, but once compiled, it doesn't work anymore.

-A:

  1. You probably are using the PWoutln command when your program runs in the interperter. Are you using this still when compiled? You shouldn't.
  2. If the error seems to stem from the PW command - which is often the case if the other PWxxxx keywords come back with "bad parameter" or such errors- then there is a large chance that you have compiled the program with the NAMES option deselected, but are using somewhere a direct name in the PW command. You should put the paramters to the PW function between quotes.

-Q: I can run any program correctly (or so it seems...) under the interpreter, but I always get a "not enough stack" message from a compiled program.

-A: First try to increase the stack of your application. Include the following line as the very first line of your program: REMark $$stak=20000. If it is only a "normal" Qliberator problem, then this will cure it.

The problem may, however, still persist. The reason for this is rather technical, BUT it is due to the fact that you did not follow the manual correctly: Somewhere, ProWesS is coming back to SBasic (QLiberator) in a manner that was not as it should have been. Typical candidates are Fileselect objects where you indicated an Action routine (even though you shouldn't) or Edlines that are activated through a PWchange, and also include an action_after routine (which they shouldn't).