Hi Ferdinand ;

    Well that statement would be pre-PB v4.0. In the early years of PB 1.0, 2, 3 ... PowerScript was based more on the "Basic" language because most new PB developers were used to Basic and/or COBOL. So most commands were XXXXXX ( Object ) in syntax nature. For example:

SetActioncode (THIS, -1 )  // EditChanged Event in PB 1.x

     In PB 2.0, PowerSoft decided that they would move from "C" to C++ in the background for the IDE. That is because their goal now was to make PB more like "SmallTalk" (considered fully object oriented at that time). SmallTalk at that time (late 1980's) was THE OO tool to use. So with the OO model in mind, the SetActionCode() command became:

THIS.SetActioncode (-1 )  // EditChanged Event in PB 2/3.x

   In PB 4.0, PowerSoft changed their approach on the SetActionCode() command and replaced it with

RETURN  -1

   So if your App was built under a very old version of PB or your an old PB Developer (like me - LOL), you can still use the older versions of the PowerScript Syntax. The IDE compiler will accept the old syntax. It might give you a warning but, it should allow you to compile & save if you ignore it.

  So if your in a refactoring mode, just change the command to <DS>.Update() to be "hip".  ;-)

PS: Trivia ... The 1st OO language was Simlua and it was released in 1963.

      https://en.wikipedia.org/wiki/Simula

Regards ... Chris