RE: RPG naming

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

That's because we call it "encapsulation" or, for the ancient among us,
"modularization".  The idea was the same: write a procedure or program
with a fixed parameter list, and whatever was inside that program was
nobody's business.  The fact that the compiler enforces the contract is
simply the strict typing paradigm (which as I noted in another email is
actually a bone of contention between OO types: you can find heated
debate about strict typing like in Java vs. loose typing as done in
Python).

Joe

P.S. Yeah, I like "persists".  Not only is it a new word for an old
function, it's also the transformation of an adjective to a verb.  I do
so love technical jargon <g>.


> From: Cate, Tony (Alliance)
> 
> I rarely (as in I can't remember an instance) hear a RPG professional
> discuss refactoring. At a previous place of employment I was derided
> vigorously for suggesting it as a method of code improvement. It's an
> uphill battle.
> 
> By the way, my favorite 'renaming' of things is Microsoft's use of
> 'Persists' instead of save.  Ex: Biztalk persists each record in the
> SQLServer database.