Project

General

Profile

Unimplemented Quirks Protocol

By default, it is assumed that all 4GL behavior is to be implemented with 100% compatibility/fidelity. In almost any scenario, this can be relied upon as a rule. This rule even extends to some really weird/bizarre behavior which has little rational explanation, whenever a 4GL application can rely upon such crazy behavior in order to process correctly. This means that a huge amount of really weird stuff has been implemented in FWD, solely because real applications rely upon that behavior to properly function.

However, there are some crazy behaviors that (at the present time):

  • We don't know of an application which relies upon it. AND
  • We can't see a useful reason to otherwise implement it.

Such "features" are either very strange corner cases that are accidental implementation choices or they are simply long standing bugs in OpenEdge which have not been fixed (and may never be fixed). We call this category a "quirk". The implementation of quirks is deferred (and we hope to defer that implement forever). Here is the process to determine if there is a quirk and how to handle it:

  1. Discuss with the team to confirm if both conditions above are true.
  2. If so, then this is considered a "quirk". Once this determination is made, we can defer the implementation.
  3. To defer the implemention:
    1. Create a new task in the appropriate project. For example, user interface quirks should be created in User Interface.
    2. In that task, describe the quirk in detail and how to recreate it. Make sure to include the 4GL sample code that allows the reproduction.
    3. Link that task as a "Related Task" in the master task for related quirks. See below for the master task list.

#2596 unimplemented BROWSE quirks


© 2021 Golden Code Development Corporation. ALL RIGHTS RESERVED.