#79
  • Created on
    2010-04-27 16:29
  • Reported by
    stuartsierra
  • Status
    Fixed
  • Priority
    Normal (3)
  • Assigned to
    stuartsierra
  • Milestone
    Backlog
  • Plan Level
    -
  • Permission type
    None
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

Forward-port deprecated 1.1 namespaces

Too many people are doing crazy stuff with conditional loading just to support both 1.1 and 1.2 simultaneously. This way lies madness.

To avoid this, lets forward-port all the 1.1 namespaces that were removed or renamed in master, e.g. duck-streams, seq-utils, str-utils, etc. Just copy the old files from the 1.1 branch, so that no behavior changes.

Add a printed deprecation warning at the top-level of each of the old namespaces, like
(println "The foo namespace is deprecated, please use bar instead.")

Post 1.2 release we can remove the deprecated namespaces.
User picture
  on 2010-04-28 19:03 *
By stuartsierra
Assigned to set to stuartsierra
(In revision:a1c66df5287776b4397cf3929a5f498fbb34ea32) Copy deleted/renamed namespaces from 1.1 release; refs #79

  • For backward compatibility with 1.1 release.
  • Namespaces copied: duck-streams, java-utils, seq-utils,
shell-out, str-utils, str-utils2.
  • These namespaces can be marked as deprecated.
  • They are copied rather than simply aliased because
some behavior has changed.

Branch: master
User picture
  on 2010-04-28 20:21 *
By Chas Emerick
FWIW, the various signature and fn name changes between 1.1 and 1.2 still need to be unraveled by any codebase that wants to target both, and choosing which impl to use is still easiest by eagerly loading whereever the new impls are in a try/catch. I'm not arguing against restoring the old namespaces (at the moment! :-), just pointing out that doing so doesn't impact 1.1/1.2 compat.
User picture
  on 2010-09-17 16:51 *
By stuartsierra
Status changed from New to Fixed
Work remaining changed from 5.0 to 0.0