sass 3.7.4 → 4.0.0.alpha.1

checksums.yaml

@@ -1,7 +1,15 @@
 ---
-SHA1:
-  metadata.gz: 6442c161b5fc7709753d4bdc2a134f340af6d908
-  data.tar.gz: '0946cacd17612b438ce689b86cce9fa6a90bc208'
+!binary "U0hBMQ==":
+  metadata.gz: !binary |-
+    NzMwNWUzNzdjNWY1ODExMjYyZTM1NWQ5YTM1MWVmNjQ4MjljZWI2NA==
+  data.tar.gz: !binary |-
+    MGM5MWVlZDJjMzFlYjY2NTQxZjZiYTcwMzM2YThhODRkOTk0OGQyYg==
 SHA512:
-  metadata.gz: 87b7eb8440a85957deaf8b83549d60fdb86f8c5f865aab9db67bee7ba8cd5c0985f05018c9a7ff18e1ea514aa2beb8dbca238257f76e6db14b9f6b1793bf4388
-  data.tar.gz: 5c786b64db488ba61d018257943aeb1ab9365c2e7069201ae0a5759fdbe6576f36d57a885ea690824d15d398d2c8c656fb21be0460ca5f6b088f2e10cfd1edee
+  metadata.gz: !binary |-
+    M2U5ODMzYjQ4OTQxOTNmZDFhOGM2YmNhODRkZjhhMjAxOWQ1Yjg4ZjZiMzM2
+    YjcyZWNmMTNmMmJlZTY4NDBkYmI0NDUzZDM3NzI0ZGNhM2NlNTZkMDU2MWI5
+    ZGIyYWE0MGEyZmExYWU2YTQ1ZGRmZDFlZjRmNThlNDliNmI3Y2M=
+  data.tar.gz: !binary |-
+    Yjk3MjlkNjU3YWM0ZmUxMDIxMTk1MWFjODZhM2QyOGMyODQzZjFiZDczZDRj
+    YjUzNDRlYTU4MjRkZmYwM2VhYTBiMjk0NTE4ODdhMzYzZTMzYjRmYTdmOTlm
+    N2I3NmQxYTE5YTdmNmNjMzRlY2Q4ZWMzYzA5NzRjZWMzNjcxYWY=

data/.yardopts

@@ -1,6 +1,6 @@
 --readme          README.md
 --markup          markdown
---markup-provider redcarpet
+--markup-provider maruku
 --default-return  ""
 --title           "Sass Documentation"
 --query           'object.type != :classvariable'

data/CODE_OF_CONDUCT.md

@@ -7,4 +7,4 @@ fair place to play.
 
 [The full community guidelines can be found on the Sass website.][link]
 
-[link]: https://sass-lang.com/community-guidelines
+[link]: http://sass-lang.com/community-guidelines

data/CONTRIBUTING.md

@@ -1,148 +1,3 @@
 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.
+[http://sass-lang.com/community#Contribute](http://sass-lang.com/community#Contribute)

data/MIT-LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2006-2016 Hampton Catlin, Natalie Weizenbaum, and Chris Eppstein
+Copyright (c) 2006-2015 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,12 +1,4 @@
-## Ruby Sass Has Reached End-of-Life
-
-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 [![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)
 
 **Sass makes CSS fun again**. Sass is an extension of CSS,
 adding nested rules, variables, mixins, selector inheritance, and more.
@@ -52,7 +44,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](https://sass-lang.com/docs/yardoc/file.SASS_REFERENCE.html#template_location-option) for details).
+see [the Sass reference](http://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
@@ -67,7 +59,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](https://sass-lang.com/documentation/file.SASS_REFERENCE.html#using_sass).
+check out the [YARD documentation](http://sass-lang.com/documentation/file.SASS_REFERENCE.html#using_sass).
 
 ## Formatting
 
@@ -81,10 +73,10 @@ and get small stylesheets up and running quickly,
 particularly with the help of
 [the Compass style library](http://compass-style.org).
 
-[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
+[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
 
 Sass has two syntaxes.
 The one presented here, known as "SCSS" (for "Sassy CSS"),
@@ -93,7 +85,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]: https://sass-lang.com/documentation/file.SASS_REFERENCE.html#syntax
+[syntax]: http://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`.
@@ -168,7 +160,7 @@ You can even give them arguments.
 ```
 
 A comprehensive list of features is available
-in the [Sass reference](https://sass-lang.com/documentation/file.SASS_REFERENCE.html).
+in the [Sass reference](http://sass-lang.com/documentation/file.SASS_REFERENCE.html).
 
 ## Executables
 
@@ -192,7 +184,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
+$ cd <SASS_CHECKOUT_DIRECTORY>
 $ bundle
 $ bundle exec sass ...
 $ bundle exec scss ...
@@ -207,29 +199,23 @@ 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](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.
+[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 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.
 
-[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
+[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
 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 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:
+his wife and daughter. He is an Engineer for
+[LinkedIn.com](http://linkedin.com), where one of his responsibilities is to
+maintain Sass & Compass.
 
-* [Trans Justice Funding Project](http://www.transjusticefundingproject.org/)
-* [United Mitochondrial Disease Foundation](http://umdf.org/compass)
-* [Girl Develop It](https://www.girldevelopit.com/donate)
+If you use this software, you must pay Hampton a compliment. And buy Natalie
+some candy. Maybe pet a kitten. Yeah. Pet that kitty.
 
-Sass is licensed under the MIT License.
+Beyond that, the implementation is licensed under the MIT License.
+Okay, fine, I guess that means compliments aren't __required__.

data/Rakefile

@@ -0,0 +1,274 @@
+require 'rubygems/package'
+
+# ----- Utility Functions -----
+
+def scope(path)
+  File.join(File.dirname(__FILE__), path)
+end
+
+# ----- Default: Testing ------
+
+task :default => :test
+
+require 'rake/testtask'
+
+Rake::TestTask.new do |t|
+  t.libs << 'test'
+  test_files = FileList[scope('test/**/*_test.rb')]
+  test_files.exclude(scope('test/rails/*'))
+  test_files.exclude(scope('test/plugins/*'))
+  t.test_files = test_files
+  t.verbose = true
+end
+
+# ----- Code Style Enforcement -----
+
+version = RUBY_VERSION.split(".").map {|n| n.to_i}
+
+# TODO: Run Rubocop on Ruby 2.2+ when it's supported. See
+# https://github.com/sass/sass/pull/1805.
+if (version[0] > 1 || (version[0] == 1 && version[1] > 8)) &&
+    (version[0] < 2 || (version[0] == 2 && version[1] < 2)) &&
+    (ENV.has_key?("RUBOCOP") && ENV["RUBOCOP"] == "true" ||
+      !(ENV.has_key?("RUBOCOP") || ENV.has_key?("TEST")))
+  require 'rubocop/rake_task'
+  Rubocop::RakeTask.new do |t|
+    t.patterns = FileList["lib/**/*"]
+  end
+else
+  task :rubocop do
+    puts "Skipping rubocop style check."
+    if !ENV.has_key?("RUBOCOP")
+      puts "Passing this check is required in order for your patch to be accepted."
+      puts "Use ruby 1.9 or greater and then run the style check with: rake rubocop"
+    end
+  end
+end
+
+task :test => :rubocop
+
+# ----- Packaging -----
+
+# Don't use Rake::GemPackageTast because we want prerequisites to run
+# before we load the gemspec.
+desc "Build all the packages."
+task :package => [:revision_file, :date_file, :submodules, :permissions] do
+  version = get_version
+  File.open(scope('VERSION'), 'w') {|f| f.puts(version)}
+  load scope('sass.gemspec')
+  Gem::Package.build(SASS_GEMSPEC)
+  sh %{git checkout VERSION}
+
+  pkg = "#{SASS_GEMSPEC.name}-#{SASS_GEMSPEC.version}"
+  mkdir_p "pkg"
+  verbose(true) {mv "#{pkg}.gem", "pkg/#{pkg}.gem"}
+
+  sh %{rm -f pkg/#{pkg}.tar.gz}
+  verbose(false) {SASS_GEMSPEC.files.each {|f| sh %{tar rf pkg/#{pkg}.tar #{f}}}}
+  sh %{gzip pkg/#{pkg}.tar}
+end
+
+task :permissions do
+  sh %{chmod -R a+rx bin}
+  sh %{chmod -R a+r .}
+  require 'shellwords'
+  Dir.glob('test/**/*_test.rb') do |file|
+    next if file =~ %r{^test/haml/spec/}
+    sh %{chmod a+rx #{file}}
+  end
+end
+
+task :revision_file do
+  require scope('lib/sass')
+
+  release = Rake.application.top_level_tasks.include?('release') || File.exist?(scope('EDGE_GEM_VERSION'))
+  if Sass.version[:rev] && !release
+    File.open(scope('REVISION'), 'w') { |f| f.puts Sass.version[:rev] }
+  elsif release
+    File.open(scope('REVISION'), 'w') { |f| f.puts "(release)" }
+  else
+    File.open(scope('REVISION'), 'w') { |f| f.puts "(unknown)" }
+  end
+end
+
+task :date_file do
+  File.open(scope('VERSION_DATE'), 'w') do |f|
+    f.puts Time.now.utc.strftime('%d %B %Y %T %Z')
+  end
+end
+
+# We also need to get rid of this file after packaging.
+at_exit do
+  File.delete(scope('REVISION')) rescue nil
+  File.delete(scope('VERSION_DATE')) rescue nil
+end
+
+desc "Install Sass as a gem. Use SUDO=1 to install with sudo."
+task :install => [:package] do
+  gem  = RUBY_PLATFORM =~ /java/  ? 'jgem' : 'gem'
+  sh %{#{'sudo ' if ENV["SUDO"]}#{gem} install --no-ri pkg/sass-#{get_version}}
+end
+
+desc "Release a new Sass package to RubyGems.org."
+task :release => [:check_release, :package] do
+  name = File.read(scope("VERSION_NAME")).strip
+  version = File.read(scope("VERSION")).strip
+  sh %{gem push pkg/sass-#{version}.gem}
+end
+
+# Ensures that the VERSION file has been updated for a new release.
+task :check_release do
+  version = File.read(scope("VERSION")).strip
+  raise "There have been changes since current version (#{version})" if changed_since?(version)
+  raise "VERSION_NAME must not be 'Bleeding Edge'" if File.read(scope("VERSION_NAME")) == "Bleeding Edge"
+end
+
+# Reads a password from the command line.
+#
+# @param name [String] The prompt to use to read the password
+def read_password(prompt)
+  require 'readline'
+  system "stty -echo"
+  Readline.readline("#{prompt}: ").strip
+ensure
+  system "stty echo"
+  puts
+end
+
+# Returns whether or not the repository, or specific files,
+# has/have changed since a given revision.
+#
+# @param rev [String] The revision to check against
+# @param files [Array<String>] The files to check.
+#   If this is empty, checks the entire repository
+def changed_since?(rev, *files)
+  IO.popen("git diff --exit-code #{rev} #{files.join(' ')}") {}
+  return !$?.success?
+end
+
+task :submodules do
+  if File.exist?(File.dirname(__FILE__) + "/.git")
+    sh %{git submodule sync}
+    sh %{git submodule update --init}
+  elsif !File.exist?(File.dirname(__FILE__) + "/vendor/listen/lib")
+    warn <<WARN
+WARNING: vendor/listen doesn't exist, and this isn't a git repository so
+I can't get it automatically!
+WARN
+  end
+end
+
+# Get the version string. If this is being installed from Git,
+# this includes the proper prerelease version.
+def get_version
+  File.read(scope('VERSION').strip)
+end
+
+task :watch_for_update do
+  sh %{ruby extra/update_watch.rb}
+end
+
+# ----- Documentation -----
+
+task :rdoc do
+  puts '=' * 100, <<END, '=' * 100
+Sass uses the YARD documentation system (http://github.com/lsegal/yard).
+Install the yard gem and then run "rake doc".
+END
+end
+
+begin
+  require 'yard'
+
+  namespace :doc do
+    task :sass do
+      require scope('lib/sass')
+      Dir[scope("yard/default/**/*.sass")].each do |sass|
+        File.open(sass.gsub(/sass$/, 'css'), 'w') do |f|
+          f.write(Sass::Engine.new(File.read(sass)).render)
+        end
+      end
+    end
+
+    desc "List all undocumented methods and classes."
+    task :undocumented do
+      opts = ENV["YARD_OPTS"] || ""
+      ENV["YARD_OPTS"] = opts.dup + <<OPTS
+ --list --tag comment --hide-tag comment --query "
+  object.docstring.blank? &&
+  !(object.type == :method && object.is_alias?)"
+OPTS
+      Rake::Task['yard'].execute
+    end
+  end
+
+  YARD::Rake::YardocTask.new do |t|
+    t.files = FileList.new(scope('lib/**/*.rb')) do |list|
+      list.exclude('lib/sass/plugin/merb.rb')
+      list.exclude('lib/sass/plugin/rails.rb')
+    end.to_a
+    t.options << '--incremental' if Rake.application.top_level_tasks.include?('redoc')
+    t.options += FileList.new(scope('yard/*.rb')).to_a.map {|f| ['-e', f]}.flatten
+    files = FileList.new(scope('doc-src/*')).to_a.sort_by {|s| s.size} + %w[MIT-LICENSE VERSION]
+    t.options << '--files' << files.join(',')
+    t.options << '--template-path' << scope('yard')
+    t.options << '--title' << ENV["YARD_TITLE"] if ENV["YARD_TITLE"]
+
+    t.before = lambda do
+      if ENV["YARD_OPTS"]
+        require 'shellwords'
+        t.options.concat(Shellwords.shellwords(ENV["YARD_OPTS"]))
+      end
+    end
+  end
+  Rake::Task['yard'].prerequisites.insert(0, 'doc:sass')
+  Rake::Task['yard'].instance_variable_set('@comment', nil)
+
+  desc "Generate Documentation"
+  task :doc => :yard
+  task :redoc => :yard
+rescue LoadError
+  desc "Generate Documentation"
+  task :doc => :rdoc
+  task :yard => :rdoc
+end
+
+# ----- Coverage -----
+
+begin
+  require 'rcov/rcovtask'
+
+  Rcov::RcovTask.new do |t|
+    t.test_files = FileList[scope('test/**/*_test.rb')]
+    t.rcov_opts << '-x' << '"^\/"'
+    if ENV['NON_NATIVE']
+      t.rcov_opts << "--no-rcovrt"
+    end
+    t.verbose = true
+  end
+rescue LoadError; end
+
+# ----- Profiling -----
+
+begin
+  require 'ruby-prof'
+
+  desc <<END
+Run a profile of sass.
+  TIMES=n sets the number of runs. Defaults to 1000.
+  FILE=str sets the file to profile. Defaults to 'complex'.
+  OUTPUT=str sets the ruby-prof output format.
+    Can be Flat, CallInfo, or Graph. Defaults to Flat. Defaults to Flat.
+END
+  task :profile do
+    times  = (ENV['TIMES'] || '1000').to_i
+    file   = ENV['FILE']
+
+    require 'lib/sass'
+
+    file = File.read(scope("test/sass/templates/#{file || 'complex'}.sass"))
+    result = RubyProf.profile { times.times { Sass::Engine.new(file).render } }
+
+    RubyProf.const_get("#{(ENV['OUTPUT'] || 'Flat').capitalize}Printer").new(result).print
+  end
+rescue LoadError; end