Fixes for ; not supported in mixin parameter lists #319 #320
Fixed @import to follow LESS 1.4.0 specification
Merge pull request #326 from munissor/master

Fixed @import to follow LESS 1.4.0 specification
Adds a "DisableColorCompression" flag to the configuration to fix issue #332
Added a unit test for the "DisableColorCompression" config flag for issue #332
changed parse of CSS selector attribute names to allow mixed case

see issue 334, https://github.com/dotless/dotless/issues/334 ,

if following CSS specified, 

    img[imgType="sort"]
    { ...

then compiler was give error...

   Expected ']' but found 'y' on line XXXX in file '....':

Changing to 

    img[imgtype="sort"]

would get around issue.
Merge pull request #333 from david-poirier/master

Adds a "DisableColorCompression" flag to the configuration to fix issue ...
Update SelectorFixture test for issue #334

Unit test for below, fixed in issue #334 where previously a mixed case attribute selector would result in a compile error.
    img[imgType="sort"]
    {
        margin-left:5px;
        padding-left:5px;
    }
Fix major bug with watcher and file being watched having other imports

If a file has other imports such as ...

#import "file1.less";
#import "file2.less"

and the watch is run on this file (e.g. --watch), then the file will compile the first time the compiler is run as --watch, but any changes to the file after that will result in the imports failing.  No imports of the files will be done, they will simply be skipped.

The problem is that a shared "engine" was used for all following compilation delegates instead of a new engine being created for each compile.  

The engine used to not be shared, but was changed in the following checkin...
   https://github.com/dotless/dotless/commit/80b483c7d0ae30e79bad03c624614c5e23850edc#diff-4d66a4cc28d0a6911703f1b28ba48125

At this time, this was probably fine, but when the import was changed to be a default of "import once", then the shared/re-used engine results in this problem.  The engine keeps track of what imports have been done.  On the 2nd and future compiles of the file, the engine detects that the imports have already been done (due to first run of --watch and compile), and therefore skips any other imports.

Creating a new engine for every compile delegate call fixes this issue by having a new fresh uninitialized engine for every compile.
Merge pull request #335 from ronl/patch-1

changed parse of CSS selector attribute names to allow mixed case
Merge pull request #336 from ronl/patch-2

Update SelectorFixture test for issue #335 checkin
Merge pull request #337 from ronl/patch-3

Fix major bug with watcher and file being watched having other imports
Allow class to import a mixin with the same selector (Issue #136)

A class could already import a mxin with the same name but if another
selector within the same scope as that class and the identically-named
mixin tried to import the mixin, a stack overflow would occur. See Issue
#136 for more details and a reproduce case (or see the new unit test in
this changeset).
Merge pull request #339 from ProductiveRage/master

Allow class to import a mixin with the same selector (Issue #136)
Allow IE "\9" hack on rules with evaluated values

Bootstrap includes rules such as "background-color: #000 \9; // IE8"
which dotLess would not parse. It was ok with rules such as
"background-color: red \9; // IE8", where it doesn't have to evaluate
the value (it just pulls out the string "red" rather than trying to
parse "#000"). I've added a unit test for the now-fixed evaulated value
version and added one for the already-working non-evaluated value (for
regression testing). All of the existing unit tests still pass. This
relates to Issue 340.
Enable multi-Element Mixin Selectors

Previously, dotLess would require that mixins be selectors with single
elements (eg. ".dropdown-menu") since the matching algorithm would try
to match only a single element and then drill down into the selector's
rules for any additional elements. Bootstrap uses multi-element mixin
selectors (eg. ".pull-right > .dropdown"), the drilling down should only
be done if the selector does not already fully match the specified
selector. I've added a unit test to illustrate the fix, the existing
unit tests all still pass. The comments on pull request #323 refer to
this issue.
Merge pull request #341 from ProductiveRage/master

Allow IE "\9" hack on rules with evaluated values
Merge pull request #342 from ProductiveRage/MultipleElementMixinSelectorFix

Enable multi-Element Mixin Selectors
Handling of empty declarations to avoid throwing an exception when declaration block contains successive semicolons
Merge pull request #1 from VSoftTechnologies/master

Fixes for ; not supported in mixin parameter lists #319 #320