[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Order of include file parameters influence DEFINED() value

  • Thread starter Thread starter frank.meulblok
  • Start date Start date
Status
Not open for further replies.
F

frank.meulblok

Guest
And apart from the notes that are nowadays irrelevant (Sequent platform has not been supported for how long exactly?) or bad practice, the one that really identifies current behavior as a bug is of course the first one: "You can pass a series of positional arguments or a series of named arguments to an include file, but you cannot pass a combination of positional and named arguments to an include file." So in the example, case 2,3 and 7 should raise a compile-time error. And in cases 1,5 and 6, I'd say what you *should* see is that myParam is not defined as a preprocessor name, and the positional arguments resolve to the literal string "&myParam" -> without the "=" those don't follow the syntax for named arguments so they should not be parsed as such.

Continue reading...
 
Status
Not open for further replies.
Back
Top