sass 3.4.9 → 3.7.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 586156255d3623fed22e16cc8ddf44c6f50931af
-  data.tar.gz: 4660667253de7af141d348bb68e400801a8c167a
+  metadata.gz: 6442c161b5fc7709753d4bdc2a134f340af6d908
+  data.tar.gz: '0946cacd17612b438ce689b86cce9fa6a90bc208'
 SHA512:
-  metadata.gz: b23a97f2c8142ddd09e624e8363fb69901a92e092ca1c645768b407c0be27e6fa74ed4d47a1b175fedcda42fed3e7ea0f15c54161b9e737f2bb39b1d4e71cc77
-  data.tar.gz: c2b58e2b9be2c58d95310a960d4d27d4834fe2d18f33eebbdafae9e348c35e6550dce359f4d608b571861b0ef0bba827b0017406fb79935e224b5be6d0c03b88
+  metadata.gz: 87b7eb8440a85957deaf8b83549d60fdb86f8c5f865aab9db67bee7ba8cd5c0985f05018c9a7ff18e1ea514aa2beb8dbca238257f76e6db14b9f6b1793bf4388
+  data.tar.gz: 5c786b64db488ba61d018257943aeb1ab9365c2e7069201ae0a5759fdbe6576f36d57a885ea690824d15d398d2c8c656fb21be0460ca5f6b088f2e10cfd1edee

data/.yardopts

@@ -1,6 +1,6 @@
 --readme          README.md
 --markup          markdown
---markup-provider maruku
+--markup-provider redcarpet
 --default-return  ""
 --title           "Sass Documentation"
 --query           'object.type != :classvariable'
@@ -9,3 +9,5 @@
 --protected
 --no-private
 --no-highlight
+--tag             comment
+--hide-tag        comment

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,10 @@
+Sass is more than a technology; Sass is driven by the community of individuals
+that power its development and use every day. As a community, we want to embrace
+the very differences that have made our collaboration so powerful, and work
+together to provide the best environment for learning, growing, and sharing of
+ideas. It is imperative that we keep Sass a fun, welcoming, challenging, and
+fair place to play.
+
+[The full community guidelines can be found on the Sass website.][link]
+
+[link]: https://sass-lang.com/community-guidelines

data/CONTRIBUTING.md

@@ -0,0 +1,148 @@
+Contributions are welcomed. Please see the following site for guidelines:
+
+[https://sass-lang.com/community#Contribute](https://sass-lang.com/community#Contribute)
+
+* [Branches](#main-development-branches)
+  * [Feature Branches](#feature-branches)
+  * [Experimental Branches](#experimental-branches)
+  * [Old Stable Branches](#old-stable-branches)
+* [Versioning](#versioning)
+  * [Making Breaking Changes](#making-breaking-changes)
+  * [Exceptional Breakages](#exceptional-breakages)
+
+## Branches
+
+The Sass repository has three primary development branches, each of which tracks
+a different line of releases (see [versioning](#versioning) below). Each branch
+is regularly merged into the one below: `stable` into `next`, `next` into
+`master`.
+
+* The `stable` branch is the default—it's what GitHub shows if you go to
+  [sass/ruby-sass](https://github.com/sass/ruby-sass), and it's the default place for pull
+  requests to go. This branch is where we work on the next patch release. Bug
+  fixes and documentation improvements belong here, but not new features.
+
+* The `next` branch is where we work on the next minor release. It's where most
+  new features go, as long as they're not breaking changes. Very occasionally
+  breaking changes will go here as well—see
+  [exceptional breakages](#exceptional-breakages) below for details.
+
+* The `master` branch is where we work on the next major release. It's where
+  breaking changes go. We also occasionally decide that a non-breaking feature
+  is big enough to warrant saving until the next major release, in which case it
+  will also be developed here.
+
+Ideally, pull requests would be made against the appropriate
+branch, but don't worry about it too much; if you make a request against the
+wrong branch, the maintainer will take responsibility for rebasing it before
+merging.
+
+### Testing
+
+Tests for changes to the Sass language go in
+[sass-spec](https://github.com/sass/sass-spec) so that other
+implementations (E.g. libSass) can be tested against the same test
+suite. The sass-spec repo follows a "trunk development" model in that
+the tests there test against different version of the Sass language (as
+opposed to having branches that track different Sass versions). When
+contributing changes to Sass, update the Gemfile to use sass-spec from a
+branch or fork that has the new tests. When the feature lands in Sass,
+the committer will also merge the corresponding sass-spec changes.
+
+The [documentation of
+sass-spec](https://github.com/sass/sass-spec/blob/master/README.md)
+explains how to run sass-spec and contribute changes. In development,
+Change the Gemfile(s) to use the `:path` option against the sass-spec gem
+to link your local checkout of sass and sass-spec together in one or
+both directions.
+
+Changes to Sass internals or Ruby Sass specific features (E.g.
+the `sass-convert` tool) should always have tests in the Sass `test`
+directory following the conventions you see there.
+
+### Feature Branches
+
+Sometimes it won't be possible to merge a new feature into `next` or `master`
+immediately. It may require longer-term work before it's complete, or we may not
+want to release it as part of any alpha releases of the branch in question.
+Branches like this are labeled `feature.#{name}` and stay on GitHub until
+they're ready to be merged.
+
+### Experimental Branches
+
+Not all features pan out, and not all code is a good fit for merging into the
+main codebase. Usually when this happens the code is just discarded, but every
+so often it's interesting or promising enough that it's worth keeping around.
+This is what experimental branches (labeled `experimental.#{name}`) are for.
+While they're not currently in use, they contain code that might be useful in
+the future.
+
+### Old Stable Branches
+
+Usually Sass doesn't have the development time to do long-term maintenance of
+old release. But occasionally, very rarely, it becomes necessary. In cases like
+that, a branch named `stable_#{version}` will be created, starting from the last
+tag in that version series.
+
+## Versioning
+
+Starting with version 3.5.0, Sass uses [semantic versioning](http://semver.org/)
+to indicate the evolution of its language semantics as much as possible. This
+means that patch releases (such as 3.5.3) contain only bug fixes, minor releases
+(such as 3.6.0) contain backwards-compatible features, and only major releases
+(such as 4.0.0) are allowed to have backwards-incompatible behavior. There are
+[exceptions](#exceptional-breakages), but we try to follow this rule as closely
+as possible.
+
+Note, however, that the semantic versioning applies only to the language's
+semantics, not to the Ruby APIs. Although we try hard to keep widely-used APIs
+like [`Sass::Engine`][Sass::Engine] stable, we don't have a strong distinction
+between public and private APIs and we need to be able to freely refactor our
+code.
+
+[Sass::Engine]: https://sass-lang.com/documentation/Sass/Engine.html
+
+### Making Breaking Changes
+
+Sometimes the old way of doing something just isn't going to work anymore, and
+the new way just can't be made backwards-compatible. In that case, a breaking
+change is necessary. These changes are rarely pleasant, but they contribute to
+making the language better in the long term.
+
+Our breaking change process tries to make such changes as clear to users and as
+easy to adapt to as possible. We want to ensure that there's a clear path
+forward for users using functionality that will no longer exist, and that they
+are able to understand what's changing and what they need to do. We've developed
+the following process for this:
+
+1. Deprecate the old behavior [in `stable`](#branches). At minimum, deprecating
+   some behavior involves printing a warning when that behavior is used
+   explaining that it's going to go away in the future. Ideally, this message
+   will also include code that will do the same thing in a non-deprecated way.
+   If there's a thorough prose explanation of the change available online, the
+   message should link to that as well.
+
+2. If possible, make `sass-convert` (also in `stable`) convert the deprecated
+   behavior into a non-deprecated form. This allows users to run `sass-convert
+   -R -i` to automatically update their stylesheets.
+
+3. Implement the new behavior in `master`. The sooner this happens, the better:
+   it may be unclear exactly what needs to be deprecated until the new
+   implementation exists.
+
+4. Release an alpha version of `master` that includes the new behavior. This
+   allows users who are dissatisfied with the workaround to use the new
+   behavior early. Normally a maintainer will take care of this.
+
+### Exceptional Breakages
+
+Because Sass's syntax and semantics are closely tied to those of CSS, there are
+occasionally times when CSS syntax is introduced that overlaps with
+previously-valid Sass. In this case in particular, we may introduce a breaking
+change in a minor version to get back to CSS compatibility as soon as possible.
+
+Exceptional breakages still require the full deprecation process; the only
+change is that the new behavior is implemented in `next` rather than `master`.
+Because there are no minor releases between the deprecation and the removal of
+the old behavior, the deprecation warning should be introduced soon as it
+becomes clear that an exceptional breakage is necessary.

data/MIT-LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2006-2014 Hampton Catlin, Natalie Weizenbaum, and Chris Eppstein
+Copyright (c) 2006-2016 Hampton Catlin, Natalie Weizenbaum, and Chris Eppstein
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

data/README.md

@@ -1,14 +1,22 @@
-# Sass [![Gem Version](https://badge.fury.io/rb/sass.png)](http://badge.fury.io/rb/sass) [![Inline docs](http://inch-ci.org/github/sass/sass.svg)](http://inch-ci.org/github/sass/sass)
+## Ruby Sass Has Reached End-of-Life
 
-**Sass makes CSS fun again**. Sass is an extension of CSS3,
+Ruby Sass should no longer be used, and will no longer be receiving any updates.
+See [the Sass blog][], and consider switching to the [`sassc` gem].
+
+[the Sass blog]: https://sass-lang.com/blog/posts/7828841
+[`sassc` gem]: https://rubygems.org/gems/sassc
+
+# Sass [![Travis Build Status](https://travis-ci.org/sass/ruby-sass.svg?branch=next)](https://travis-ci.org/sass/ruby-sass) [![Gem Version](https://badge.fury.io/rb/sass.svg)](http://badge.fury.io/rb/sass) [![Inline docs](http://inch-ci.org/github/sass/sass.svg)](http://inch-ci.org/github/sass/sass)
+
+**Sass makes CSS fun again**. Sass is an extension of CSS,
 adding nested rules, variables, mixins, selector inheritance, and more.
 It's translated to well-formatted, standard CSS
 using the command line tool or a web-framework plugin.
 
 Sass has two syntaxes. The new main syntax (as of Sass 3)
 is known as "SCSS" (for "Sassy CSS"),
-and is a superset of CSS3's syntax.
-This means that every valid CSS3 stylesheet is valid SCSS as well.
+and is a superset of CSS's syntax.
+This means that every valid CSS stylesheet is valid SCSS as well.
 SCSS files use the extension `.scss`.
 
 The second, older syntax is known as the indented syntax (or just "Sass").
@@ -44,7 +52,7 @@ In Rails 3, add `gem "sass"` to your Gemfile instead.
 where they'll be automatically compiled
 to corresponding CSS files in `public/stylesheets` when needed
 (the Sass template directory is customizable...
-see [the Sass reference](http://sass-lang.com/docs/yardoc/file.SASS_REFERENCE.html#template_location-option) for details).
+see [the Sass reference](https://sass-lang.com/docs/yardoc/file.SASS_REFERENCE.html#template_location-option) for details).
 
 Sass can also be used with any Rack-enabled web framework.
 To do so, just add
@@ -59,7 +67,7 @@ Then any Sass files in `public/stylesheets/sass`
 will be compiled into CSS files in `public/stylesheets` on every request.
 
 To use Sass programmatically,
-check out the [YARD documentation](http://sass-lang.com/documentation/file.SASS_REFERENCE.html#using_sass).
+check out the [YARD documentation](https://sass-lang.com/documentation/file.SASS_REFERENCE.html#using_sass).
 
 ## Formatting
 
@@ -73,10 +81,10 @@ and get small stylesheets up and running quickly,
 particularly with the help of
 [the Compass style library](http://compass-style.org).
 
-[vars]:    http://sass-lang.com/documentation/file.SASS_REFERENCE.html#variables_
-[nested]:  http://sass-lang.com/documentation/file.SASS_REFERENCE.html#nested_rules
-[mixins]:  http://sass-lang.com/documentation/file.SASS_REFERENCE.html#mixins
-[imports]: http://sass-lang.com/documentation/file.SASS_REFERENCE.html#import
+[vars]:    https://sass-lang.com/documentation/file.SASS_REFERENCE.html#variables_
+[nested]:  https://sass-lang.com/documentation/file.SASS_REFERENCE.html#nested_rules
+[mixins]:  https://sass-lang.com/documentation/file.SASS_REFERENCE.html#mixins
+[imports]: https://sass-lang.com/documentation/file.SASS_REFERENCE.html#import
 
 Sass has two syntaxes.
 The one presented here, known as "SCSS" (for "Sassy CSS"),
@@ -85,7 +93,7 @@ The other (older) syntax, known as the indented syntax or just "Sass",
 is whitespace-sensitive and indentation-based.
 For more information, see the [reference documentation][syntax].
 
-[syntax]: http://sass-lang.com/documentation/file.SASS_REFERENCE.html#syntax
+[syntax]: https://sass-lang.com/documentation/file.SASS_REFERENCE.html#syntax
 
 To run the following examples and see the CSS they produce,
 put them in a file called `test.scss` and run `sass test.scss`.
@@ -160,7 +168,7 @@ You can even give them arguments.
 ```
 
 A comprehensive list of features is available
-in the [Sass reference](http://sass-lang.com/documentation/file.SASS_REFERENCE.html).
+in the [Sass reference](https://sass-lang.com/documentation/file.SASS_REFERENCE.html).
 
 ## Executables
 
@@ -184,7 +192,7 @@ See `sass-convert --help` for further information and options.
 To run the Sass executables from a source checkout instead of from rubygems:
 
 ```
-$ cd <SASS_CHECKOUT_DIRECTORY>
+$ cd sass
 $ bundle
 $ bundle exec sass ...
 $ bundle exec scss ...
@@ -199,23 +207,29 @@ and now occasionally consults on the language issues. Hampton lives in San
 Francisco, California and works as VP of Technology
 at [Moovweb](http://www.moovweb.com/).
 
-[Natalie Weizenbaum](http://nex-3.com) is the primary developer and architect of
-Sass. Her hard work has kept the project alive by endlessly answering forum
-posts, fixing bugs, refactoring, finding speed improvements, writing
-documentation, implementing new features, and getting Hampton coffee (a fitting
-task for a girl genius). Natalie lives in Seattle, Washington and works on
-[Dart](http://dartlang.org) application libraries at Google.
+[Natalie Weizenbaum](https://twitter.com/nex3) is the primary developer and
+architect of Sass. Her hard work has kept the project alive by endlessly
+answering forum posts, fixing bugs, refactoring, finding speed improvements,
+writing documentation, implementing new features, and designing the language.
+Natalie lives in Seattle, Washington and works on [Dart](http://dartlang.org)
+application libraries at Google.
 
-[Chris Eppstein](http://acts-as-architect.blogspot.com) is a core contributor to
-Sass and the creator of Compass, the first Sass-based framework. Chris focuses
+[Chris Eppstein](http://twitter.com/chriseppstein) is a core contributor to
+Sass and the creator of [Compass](http://compass-style.org/), the first Sass-based framework, and
+[Eyeglass](http://github.com/sass-eyeglass/eyeglass), a node-sass plugin ecosystem for NPM. Chris focuses
 on making Sass more powerful, easy to use, and on ways to speed its adoption
 through the web development community. Chris lives in San Jose, California with
-his wife and daughter. He is an Engineer for
-[LinkedIn.com](http://linkedin.com), where one of his responsibilities is to
-maintain Sass & Compass.
+his wife and two children. He is an Engineer for
+[LinkedIn.com](http://linkedin.com), where his primary responsibility is to
+maintain Sass and many other Sass-related open source projects.
+
+If you use this software, we'd be truly honored if you'd make a
+tax-deductible donation to a non-profit organization and then
+[let us know on twitter](http://twitter.com/SassCSS), so that we can
+thank you. Here's a few that we endorse:
 
-If you use this software, you must pay Hampton a compliment. And buy Natalie
-some candy. Maybe pet a kitten. Yeah. Pet that kitty.
+* [Trans Justice Funding Project](http://www.transjusticefundingproject.org/)
+* [United Mitochondrial Disease Foundation](http://umdf.org/compass)
+* [Girl Develop It](https://www.girldevelopit.com/donate)
 
-Beyond that, the implementation is licensed under the MIT License.
-Okay, fine, I guess that means compliments aren't __required__.
+Sass is licensed under the MIT License.

data/VERSION

@@ -1 +1 @@
-3.4.9
+3.7.4

data/VERSION_DATE

@@ -1 +1 @@
-25 November 2014 01:40:45 UTC
+04 April 2019 00:49:58 UTC

data/VERSION_NAME

@@ -1 +1 @@
-Selective Steve
+Bleeding Edge

data/extra/sass-spec-ref.sh

@@ -0,0 +1,40 @@
+#!/bin/bash -e
+# Copyright 2016 Google Inc. Use of this source code is governed by an MIT-style
+# license that can be found in the LICENSE file or at
+# https://opensource.org/licenses/MIT.
+
+# Echoes the sass-spec Git ref that should be checked out for the current Travis
+# run. If we're running specs for a pull request which refers to a sass-spec
+# pull request, we'll run against the latter rather than sass-spec master.
+
+default=master
+
+if [ "$TRAVIS_PULL_REQUEST" == "false" ]; then
+  >&2 echo "TRAVIS_PULL_REQUEST: $TRAVIS_PULL_REQUEST."
+  >&2 echo "Ref: $default."
+  echo "$default"
+  exit 0
+fi
+
+>&2 echo "Fetching pull request $TRAVIS_PULL_REQUEST..."
+
+url=https://api.github.com/repos/sass/ruby-sass/pulls/$TRAVIS_PULL_REQUEST
+if [ -z "$GITHUB_AUTH" ]; then
+    >&2 echo "Fetching pull request info without authentication"
+    JSON=$(curl -L -sS $url)
+else
+    >&2 echo "Fetching pull request info as sassbot"
+    JSON=$(curl -u "sassbot:$GITHUB_AUTH" -L -sS $url)
+fi
+>&2 echo "$JSON"
+
+RE_SPEC_PR="sass\/sass-spec(#|\/pull\/)([0-9]+)"
+
+if [[ $JSON =~ $RE_SPEC_PR ]]; then
+  ref="pull/${BASH_REMATCH[2]}/head"
+  >&2 echo "Ref: $ref."
+  echo "$ref"
+else
+  >&2 echo "Ref: $default."
+  echo "$default"
+fi

data/extra/update_watch.rb

@@ -7,7 +7,7 @@ enable :lock
 Dir.chdir(File.dirname(__FILE__) + "/..")
 
 post "/" do
-  puts "Recieved payload!"
+  puts "Received payload!"
   puts "Rev: #{`git name-rev HEAD`.strip}"
   system %{rake handle_update --trace REF=#{JSON.parse(params["payload"])["ref"].inspect}}
 end

data/lib/sass/cache_stores/filesystem.rb

@@ -17,12 +17,12 @@ module Sass
       # @see Base#\_retrieve
       def _retrieve(key, version, sha)
         return unless File.readable?(path_to(key))
-        File.open(path_to(key), "rb") do |f|
-          if f.readline("\n").strip == version && f.readline("\n").strip == sha
-            return f.read
-          end
-        end
         begin
+          File.open(path_to(key), "rb") do |f|
+            if f.readline("\n").strip == version && f.readline("\n").strip == sha
+              return f.read
+            end
+          end
           File.unlink path_to(key)
         rescue Errno::ENOENT
           # Already deleted. Race condition?
@@ -36,7 +36,7 @@ module Sass
       def _store(key, version, sha, contents)
         compiled_filename = path_to(key)
         FileUtils.mkdir_p(File.dirname(compiled_filename))
-        Sass::Util.atomic_create_and_write_file(compiled_filename, 0600) do |f|
+        Sass::Util.atomic_create_and_write_file(compiled_filename) do |f|
           f.puts(version)
           f.puts(sha)
           f.write(contents)
@@ -52,7 +52,7 @@ module Sass
       # @param key [String]
       # @return [String] The path to the cache file.
       def path_to(key)
-        key = key.gsub(/[<>:\\|?*%]/) {|c| "%%%03d" % Sass::Util.ord(c)}
+        key = key.gsub(/[<>:\\|?*%]/) {|c| "%%%03d" % c.ord}
         File.join(cache_location, key)
       end
     end

data/lib/sass/cache_stores/memory.rb

@@ -26,11 +26,10 @@ module Sass
 
       # @see Base#retrieve
       def retrieve(key, sha)
-        if @contents.has_key?(key)
-          return unless @contents[key][:sha] == sha
-          obj = @contents[key][:obj]
-          obj.respond_to?(:deep_copy) ? obj.deep_copy : obj.dup
-        end
+        return unless @contents.has_key?(key)
+        return unless @contents[key][:sha] == sha
+        obj = @contents[key][:obj]
+        obj.respond_to?(:deep_copy) ? obj.deep_copy : obj.dup
       end
 
       # @see Base#store

data/lib/sass/callbacks.rb

@@ -51,12 +51,12 @@ module Sass
     def define_callback(name)
       class_eval <<RUBY, __FILE__, __LINE__ + 1
 def on_#{name}(&block)
-  @_sass_callbacks ||= {}
+  @_sass_callbacks = {} unless defined? @_sass_callbacks
   (@_sass_callbacks[#{name.inspect}] ||= []) << block
 end
 
 def run_#{name}(*args)
-  return unless @_sass_callbacks
+  return unless defined? @_sass_callbacks
   return unless @_sass_callbacks[#{name.inspect}]
   @_sass_callbacks[#{name.inspect}].each {|c| c[*args]}
 end

data/lib/sass/css.rb

@@ -18,7 +18,7 @@ module Sass
     #   that can be converted to Unicode.
     #   If the stylesheet contains an `@charset` declaration,
     #   that overrides the Ruby encoding
-    #   (see {file:SASS_REFERENCE.md#encodings the encoding documentation})
+    #   (see {file:SASS_REFERENCE.md#Encodings the encoding documentation})
     # @option options :old [Boolean] (false)
     #     Whether or not to output old property syntax
     #     (`:color blue` as opposed to `color: blue`).
@@ -31,10 +31,11 @@ module Sass
         template = template.read
       end
 
-      @options = options.dup
+      @options = options.merge(:_convert => true)
       # Backwards compatibility
       @options[:old] = true if @options[:alternate] == false
       @template = template
+      @checked_encoding = false
     end
 
     # Converts the CSS template into Sass or SCSS code.
@@ -50,8 +51,7 @@ module Sass
       raise err
     end
 
-    # Returns the original encoding of the document,
-    # or `nil` under Ruby 1.8.
+    # Returns the original encoding of the document.
     #
     # @return [Encoding, nil]
     # @raise [Encoding::UndefinedConversionError] if the source encoding
@@ -75,14 +75,14 @@ module Sass
     # @return [Tree::Node] The root node of the parsed tree
     def build_tree
       root = Sass::SCSS::CssParser.new(@template, @options[:filename], nil).parse
-      parse_selectors    root
-      expand_commas      root
-      nest_seqs          root
-      parent_ref_rules   root
-      flatten_rules      root
-      bubble_subject     root
-      fold_commas        root
-      dump_selectors     root
+      parse_selectors(root)
+      expand_commas(root)
+      nest_seqs(root)
+      parent_ref_rules(root)
+      flatten_rules(root)
+      bubble_subject(root)
+      fold_commas(root)
+      dump_selectors(root)
       root
     end
 

data/lib/sass/deprecation.rb

@@ -0,0 +1,55 @@
+module Sass
+  # A deprecation warning that should only be printed once for a given line in a
+  # given file.
+  #
+  # A global Deprecation instance should be created for each type of deprecation
+  # warning, and `warn` should be called each time a warning is needed.
+  class Deprecation
+    @@allow_double_warnings = false
+
+    # Runs a block in which double deprecation warnings for the same location
+    # are allowed.
+    def self.allow_double_warnings
+      old_allow_double_warnings = @@allow_double_warnings
+      @@allow_double_warnings = true
+      yield
+    ensure
+      @@allow_double_warnings = old_allow_double_warnings
+    end
+
+    def initialize
+      # A set of filename, line pairs for which warnings have been emitted.
+      @seen = Set.new
+    end
+
+    # Prints `message` as a deprecation warning associated with `filename`,
+    # `line`, and optionally `column`.
+    #
+    # This ensures that only one message will be printed for each line of a
+    # given file.
+    #
+    # @overload warn(filename, line, message)
+    #   @param filename [String, nil]
+    #   @param line [Number]
+    #   @param message [String]
+    # @overload warn(filename, line, column, message)
+    #   @param filename [String, nil]
+    #   @param line [Number]
+    #   @param column [Number]
+    #   @param message [String]
+    def warn(filename, line, column_or_message, message = nil)
+      return if !@@allow_double_warnings && @seen.add?([filename, line]).nil?
+      if message
+        column = column_or_message
+      else
+        message = column_or_message
+      end
+
+      location = "line #{line}"
+      location << ", column #{column}" if column
+      location << " of #{filename}" if filename
+
+      Sass::Util.sass_warn("DEPRECATION WARNING on #{location}:\n#{message}")
+    end
+  end
+end