in reply to Re^3: Edifact anyone?
in thread Edifact anyone?

"You're not alone, but you don't say why?"

Skeeve's been here for 10 years and has made 799 posts. He probably knows "why". He certainly knows how to ask if he doesn't.

So why don't you say why? Not everybody knows (I don't)

Replies are listed 'Best First'.
Re^5: Edifact anyone?
by Athanasius (Archbishop) on Dec 18, 2013 at 09:03 UTC

    Release of a feature marked “experimental” is really a form of beta testing. Three issues come to mind (there may be others):

    1. The edge cases are not (fully) documented, as they haven’t all been found yet. So the current behaviour of the feature is not entirely dependable.

    2. As edge cases are found, the feature’s implementation will likely change in future releases. So the current behaviour may change, and code which uses the feature in its present implementation may need to be tweaked.

    3. Or the feature may be deprecated (see Smartmatch alternatives) and eventually removed, so that code which uses the feature may need to be re-written altogether in the future.

    In summary: code using an experimental feature requires more stringent testing now, and (potentially) greater maintenance in the future. For production code, it’s wise to avoid these pitfalls wherever possible.

    Hope that helps,

    Athanasius <°(((>< contra mundum Iustus alius egestas vitae, eros Piratica,

[reply]

      ... solid ...

      ok, thats great information

      next question, does any of this apply to how Business::Edifact::Interchange uses given/when without smart matching but as if/elsif/.../else chain?

      I think the odds of this portion of "switch" being deprecated/removed/semanticallychallenged is very low ...

      my impression of "the plans" of p5p is this part will definitely not integrate ...

[reply]

In Section Seekers of Perl Wisdom