* highlight hash-bang line as comment
* make lua-mode-hook editable via customize
* fix several indentation bugs & quirks
* fix lua-send-proc not to send previous function when point is at the beginning of a function
* derive lua-mode from prog-mode for Emacs24
* add font-locking for builtins and numeric constants
* fix a bug causing exponential complexity in a keyword matching regexp
* add more unindentation cases for block-closing tokens
* improve multiline highlighting via font-lock-syntactic-keywords
This should make font-locking of multiline literals more fluent & stable. And
it becomes customizable via standard font-lock configuration
* properly fontify variable definitions in 'local ...' & 'for ...'
Also, perform some basic syntax verification in those lines. Multi-line
constructs not supported yet.
* fix indentation for blocks starting on continued lines
local foo =
{
bar,
baz
} ^
1. these lines should be indented properly now
^
2. the following lines should be unindented properly now
* extend imenu-generic-expression
Now it matches 'foo = function(...)' function definitions
distribution.
php-opcache is the Zend OPcache module which provides faster PHP execution
through opcode caching and optimization. It improves PHP performance by
storing precompiled script bytecode in the shared memory. This eliminates the
stages of reading code from the disk and compiling it on future access. In
addition, it applies a few bytecode optimization patterns that make code
execution faster.
Released on 2013-07-28.
* Sources migrated to a GitHub project from the previous copy in
the pkgsrc repository. shtk is now a first-class package and includes
a traditional build system based on automake and autoconf and also
provides a pkg-config file and autoconf macros to ease the integration
with other packages.
- 2.37 | 2013-07-28
- dropped
- example program wwwcat
This trivial program is not so interesting.
- module ‘(www main)’
- proc ‘(www server-utils parse-request) read-first-line’
- proc ‘(www server-utils parse-request) read-headers’
- proc ‘(www server-utils parse-request) skip-headers’
- proc ‘(www server-utils parse-request) read-body’
- proc ‘(www http) http:head’
- proc ‘(www http) http:get’
These were announced in Guile-WWW 2.34 (2012-03-29) NEWS.
- support for values in ‘receive-response’ spec
This was announced in Guile-WWW 2.36 (2012-11-22) NEWS.
- ‘(www url) url:address’ more strict
- ‘(www url) url:unknown’ more strict
Contrary to the Guile-WWW 2.34 (2012-03-29) NEWS blurb, these
two procs are not being deleted. Instead, they persist and now
check their arg for the proper scheme (‘mailto’ and ‘unknown’,
respectively) to better support the (thin) abstraction they
provide over the underlying data structure.
- bootstrap tools upgraded
- GNU Automake 1.13.4
- Guile-BAUX 20130705.0751.4969fb4
1.10 (2013-07-23)
~~~~~~~~~~~~~~~~~
* **BACKWARDS INCOMPATIBLE** Dropped support for Python 2.5. The minimum
supported Python version is now Python 2.6.
* **BACKWARDS INCOMPATIBLE** Using ``virtualenv.py`` as an isolated script
(i.e. without an associated ``virtualenv_support`` directory) is no longer
supported for security reasons and will fail with an error.
Along with this, ``--never-download`` is now always pinned to ``True``, and
is only being maintained in the short term for backward compatibility
(Pull #412).
* **IMPORTANT** Switched to the new setuptools (v0.9.7) which has been merged
with Distribute_ again and works for Python 2 and 3 with one codebase.
The ``--distribute`` and ``--setuptools`` options are now no-op.
* Updated to pip 1.4.
* Added support for PyPy3k
* Added the option to use a version number with the ``-p`` option to get the
system copy of that Python version (Windows only)
* Removed embedded ``ez_setup.py``, ``distribute_setup.py`` and
``distribute_from_egg.py`` files as part of switching to merged setuptools.
* Fixed ``--relocatable`` to work better on Windows.
* Fixed issue with readline on Windows.
.. _Distribute: https://pypi.python.org/pypi/distribute
-----
0.9.8
-----
* Issue #53: Fix NameErrors in `_vcs_split_rev_from_url`.
-----
0.9.7
-----
* Issue #49: Correct AttributeError on PyPy where a hashlib.HASH object does
not have a `.name` attribute.
* Issue #34: Documentation now refers to bootstrap script in code repository
referenced by bookmark.
* Add underscore-separated keys to environment markers (markerlib).
* Noteworthy changes in release 3.0 (2013-07-25) [stable]
** WARNING: Future backward-incompatibilities!
Like other GNU packages, Bison will start using some of the C99 features
for its own code, especially the definition of variables after statements.
The generated C parsers still aim at C90.
** Backward incompatible changes
*** Obsolete features
Support for YYFAIL is removed (deprecated in Bison 2.4.2): use YYERROR.
Support for yystype and yyltype is removed (deprecated in Bison 1.875):
use YYSTYPE and YYLTYPE.
Support for YYLEX_PARAM and YYPARSE_PARAM is removed (deprecated in Bison
1.875): use %lex-param, %parse-param, or %param.
Missing semicolons at the end of actions are no longer added (as announced
in the release 2.5).
*** Use of YACC='bison -y'
TL;DR: With Autoconf <= 2.69, pass -Wno-yacc to (AM_)YFLAGS if you use
Bison extensions.
Traditional Yacc generates 'y.tab.c' whatever the name of the input file.
Therefore Makefiles written for Yacc expect 'y.tab.c' (and possibly
'y.tab.h' and 'y.outout') to be generated from 'foo.y'.
To this end, for ages, AC_PROG_YACC, Autoconf's macro to look for an
implementation of Yacc, was using Bison as 'bison -y'. While it does
ensure compatible output file names, it also enables warnings for
incompatibilities with POSIX Yacc. In other words, 'bison -y' triggers
warnings for Bison extensions.
Autoconf 2.70+ fixes this incompatibility by using YACC='bison -o y.tab.c'
(which also generates 'y.tab.h' and 'y.output' when needed).
Alternatively, disable Yacc warnings by passing '-Wno-yacc' to your Yacc
flags (YFLAGS, or AM_YFLAGS with Automake).
** Bug fixes
*** The epilogue is no longer affected by internal #defines (glr.c)
The glr.c skeleton uses defines such as #define yylval (yystackp->yyval) in
generated code. These weren't properly undefined before the inclusion of
the user epilogue, so functions such as the following were butchered by the
preprocessor expansion:
int yylex (YYSTYPE *yylval);
This is fixed: yylval, yynerrs, yychar, and yylloc are now valid
identifiers for user-provided variables.
*** stdio.h is no longer needed when locations are enabled (yacc.c)
Changes in Bison 2.7 introduced a dependency on FILE and fprintf when
locations are enabled. This is fixed.
*** Warnings about useless %pure-parser/%define api.pure are restored
** Diagnostics reported by Bison
Most of these features were contributed by Théophile Ranquet and Victor
Santet.
*** Carets
Version 2.7 introduced caret errors, for a prettier output. These are now
activated by default. The old format can still be used by invoking Bison
with -fno-caret (or -fnone).
Some error messages that reproduced excerpts of the grammar are now using
the caret information only. For instance on:
%%
exp: 'a' | 'a';
Bison 2.7 reports:
in.y: warning: 1 reduce/reduce conflict [-Wconflicts-rr]
in.y:2.12-14: warning: rule useless in parser due to conflicts: exp: 'a' [-Wother]
Now bison reports:
in.y: warning: 1 reduce/reduce conflict [-Wconflicts-rr]
in.y:2.12-14: warning: rule useless in parser due to conflicts [-Wother]
exp: 'a' | 'a';
^^^
and "bison -fno-caret" reports:
in.y: warning: 1 reduce/reduce conflict [-Wconflicts-rr]
in.y:2.12-14: warning: rule useless in parser due to conflicts [-Wother]
*** Enhancements of the -Werror option
The -Werror=CATEGORY option is now recognized, and will treat specified
warnings as errors. The warnings need not have been explicitly activated
using the -W option, this is similar to what GCC 4.7 does.
For example, given the following command line, Bison will treat both
warnings related to POSIX Yacc incompatibilities and S/R conflicts as
errors (and only those):
$ bison -Werror=yacc,error=conflicts-sr input.y
If no categories are specified, -Werror will make all active warnings into
errors. For example, the following line does the same the previous example:
$ bison -Werror -Wnone -Wyacc -Wconflicts-sr input.y
(By default -Wconflicts-sr,conflicts-rr,deprecated,other is enabled.)
Note that the categories in this -Werror option may not be prefixed with
"no-". However, -Wno-error[=CATEGORY] is valid.
Note that -y enables -Werror=yacc. Therefore it is now possible to require
Yacc-like behavior (e.g., always generate y.tab.c), but to report
incompatibilities as warnings: "-y -Wno-error=yacc".
*** The display of warnings is now richer
The option that controls a given warning is now displayed:
foo.y:4.6: warning: type clash on default action: <foo> != <bar> [-Wother]
In the case of warnings treated as errors, the prefix is changed from
"warning: " to "error: ", and the suffix is displayed, in a manner similar
to GCC, as [-Werror=CATEGORY].
For instance, where the previous version of Bison would report (and exit
with failure):
bison: warnings being treated as errors
input.y:1.1: warning: stray ',' treated as white space
it now reports:
input.y:1.1: error: stray ',' treated as white space [-Werror=other]
*** Deprecated constructs
The new 'deprecated' warning category flags obsolete constructs whose
support will be discontinued. It is enabled by default. These warnings
used to be reported as 'other' warnings.
*** Useless semantic types
Bison now warns about useless (uninhabited) semantic types. Since
semantic types are not declared to Bison (they are defined in the opaque
%union structure), it is %printer/%destructor directives about useless
types that trigger the warning:
%token <type1> term
%type <type2> nterm
%printer {} <type1> <type3>
%destructor {} <type2> <type4>
%%
nterm: term { $$ = $1; };
3.28-34: warning: type <type3> is used, but is not associated to any symbol
4.28-34: warning: type <type4> is used, but is not associated to any symbol
*** Undefined but unused symbols
Bison used to raise an error for undefined symbols that are not used in
the grammar. This is now only a warning.
%printer {} symbol1
%destructor {} symbol2
%type <type> symbol3
%%
exp: "a";
*** Useless destructors or printers
Bison now warns about useless destructors or printers. In the following
example, the printer for <type1>, and the destructor for <type2> are
useless: all symbols of <type1> (token1) already have a printer, and all
symbols of type <type2> (token2) already have a destructor.
%token <type1> token1
<type2> token2
<type3> token3
<type4> token4
%printer {} token1 <type1> <type3>
%destructor {} token2 <type2> <type4>
*** Conflicts
The warnings and error messages about shift/reduce and reduce/reduce
conflicts have been normalized. For instance on the following foo.y file:
%glr-parser
%%
exp: exp '+' exp | '0' | '0';
compare the previous version of bison:
$ bison foo.y
foo.y: conflicts: 1 shift/reduce, 2 reduce/reduce
$ bison -Werror foo.y
bison: warnings being treated as errors
foo.y: conflicts: 1 shift/reduce, 2 reduce/reduce
with the new behavior:
$ bison foo.y
foo.y: warning: 1 shift/reduce conflict [-Wconflicts-sr]
foo.y: warning: 2 reduce/reduce conflicts [-Wconflicts-rr]
$ bison -Werror foo.y
foo.y: error: 1 shift/reduce conflict [-Werror=conflicts-sr]
foo.y: error: 2 reduce/reduce conflicts [-Werror=conflicts-rr]
When %expect or %expect-rr is used, such as with bar.y:
%expect 0
%glr-parser
%%
exp: exp '+' exp | '0' | '0';
Former behavior:
$ bison bar.y
bar.y: conflicts: 1 shift/reduce, 2 reduce/reduce
bar.y: expected 0 shift/reduce conflicts
bar.y: expected 0 reduce/reduce conflicts
New one:
$ bison bar.y
bar.y: error: shift/reduce conflicts: 1 found, 0 expected
bar.y: error: reduce/reduce conflicts: 2 found, 0 expected
** Incompatibilities with POSIX Yacc
The 'yacc' category is no longer part of '-Wall', enable it explicitly
with '-Wyacc'.
** Additional yylex/yyparse arguments
The new directive %param declares additional arguments to both yylex and
yyparse. The %lex-param, %parse-param, and %param directives support one
or more arguments. Instead of
%lex-param {arg1_type *arg1}
%lex-param {arg2_type *arg2}
%parse-param {arg1_type *arg1}
%parse-param {arg2_type *arg2}
one may now declare
%param {arg1_type *arg1} {arg2_type *arg2}
** Types of values for %define variables
Bison used to make no difference between '%define foo bar' and '%define
foo "bar"'. The former is now called a 'keyword value', and the latter a
'string value'. A third kind was added: 'code values', such as '%define
foo {bar}'.
Keyword variables are used for fixed value sets, e.g.,
%define lr.type lalr
Code variables are used for value in the target language, e.g.,
%define api.value.type {struct semantic_type}
String variables are used remaining cases, e.g. file names.
** Variable api.token.prefix
The variable api.token.prefix changes the way tokens are identified in
the generated files. This is especially useful to avoid collisions
with identifiers in the target language. For instance
%token FILE for ERROR
%define api.token.prefix {TOK_}
%%
start: FILE for ERROR;
will generate the definition of the symbols TOK_FILE, TOK_for, and
TOK_ERROR in the generated sources. In particular, the scanner must
use these prefixed token names, although the grammar itself still
uses the short names (as in the sample rule given above).
** Variable api.value.type
This new %define variable supersedes the #define macro YYSTYPE. The use
of YYSTYPE is discouraged. In particular, #defining YYSTYPE *and* either
using %union or %defining api.value.type results in undefined behavior.
Either define api.value.type, or use "%union":
%union
{
int ival;
char *sval;
}
%token <ival> INT "integer"
%token <sval> STRING "string"
%printer { fprintf (yyo, "%d", $$); } <ival>
%destructor { free ($$); } <sval>
/* In yylex(). */
yylval.ival = 42; return INT;
yylval.sval = "42"; return STRING;
The %define variable api.value.type supports both keyword and code values.
The keyword value 'union' means that the user provides genuine types, not
union member names such as "ival" and "sval" above (WARNING: will fail if
-y/--yacc/%yacc is enabled).
%define api.value.type union
%token <int> INT "integer"
%token <char *> STRING "string"
%printer { fprintf (yyo, "%d", $$); } <int>
%destructor { free ($$); } <char *>
/* In yylex(). */
yylval.INT = 42; return INT;
yylval.STRING = "42"; return STRING;
The keyword value variant is somewhat equivalent, but for C++ special
provision is made to allow classes to be used (more about this below).
%define api.value.type variant
%token <int> INT "integer"
%token <std::string> STRING "string"
Code values (in braces) denote user defined types. This is where YYSTYPE
used to be used.
%code requires
{
struct my_value
{
enum
{
is_int, is_string
} kind;
union
{
int ival;
char *sval;
} u;
};
}
%define api.value.type {struct my_value}
%token <u.ival> INT "integer"
%token <u.sval> STRING "string"
%printer { fprintf (yyo, "%d", $$); } <u.ival>
%destructor { free ($$); } <u.sval>
/* In yylex(). */
yylval.u.ival = 42; return INT;
yylval.u.sval = "42"; return STRING;
** Variable parse.error
This variable controls the verbosity of error messages. The use of the
%error-verbose directive is deprecated in favor of "%define parse.error
verbose".
** Renamed %define variables
The following variables have been renamed for consistency. Backward
compatibility is ensured, but upgrading is recommended.
lr.default-reductions -> lr.default-reduction
lr.keep-unreachable-states -> lr.keep-unreachable-state
namespace -> api.namespace
stype -> api.value.type
** Semantic predicates
Contributed by Paul Hilfinger.
The new, experimental, semantic-predicate feature allows actions of the
form "%?{ BOOLEAN-EXPRESSION }", which cause syntax errors (as for
YYERROR) if the expression evaluates to 0, and are evaluated immediately
in GLR parsers, rather than being deferred. The result is that they allow
the programmer to prune possible parses based on the values of run-time
expressions.
** The directive %expect-rr is now an error in non GLR mode
It used to be an error only if used in non GLR mode, _and_ if there are
reduce/reduce conflicts.
** Tokens are numbered in their order of appearance
Contributed by Valentin Tolmer.
With '%token A B', A had a number less than the one of B. However,
precedence declarations used to generate a reversed order. This is now
fixed, and introducing tokens with any of %token, %left, %right,
%precedence, or %nonassoc yields the same result.
When mixing declarations of tokens with a litteral character (e.g., 'a')
or with an identifier (e.g., B) in a precedence declaration, Bison
numbered the litteral characters first. For example
%right A B 'c' 'd'
would lead to the tokens declared in this order: 'c' 'd' A B. Again, the
input order is now preserved.
These changes were made so that one can remove useless precedence and
associativity declarations (i.e., map %nonassoc, %left or %right to
%precedence, or to %token) and get exactly the same output.
** Useless precedence and associativity
Contributed by Valentin Tolmer.
When developing and maintaining a grammar, useless associativity and
precedence directives are common. They can be a nuisance: new ambiguities
arising are sometimes masked because their conflicts are resolved due to
the extra precedence or associativity information. Furthermore, it can
hinder the comprehension of a new grammar: one will wonder about the role
of a precedence, where in fact it is useless. The following changes aim
at detecting and reporting these extra directives.
*** Precedence warning category
A new category of warning, -Wprecedence, was introduced. It flags the
useless precedence and associativity directives.
*** Useless associativity
Bison now warns about symbols with a declared associativity that is never
used to resolve conflicts. In that case, using %precedence is sufficient;
the parsing tables will remain unchanged. Solving these warnings may raise
useless precedence warnings, as the symbols no longer have associativity.
For example:
%left '+'
%left '*'
%%
exp:
"number"
| exp '+' "number"
| exp '*' exp
;
will produce a
warning: useless associativity for '+', use %precedence [-Wprecedence]
%left '+'
^^^
*** Useless precedence
Bison now warns about symbols with a declared precedence and no declared
associativity (i.e., declared with %precedence), and whose precedence is
never used. In that case, the symbol can be safely declared with %token
instead, without modifying the parsing tables. For example:
%precedence '='
%%
exp: "var" '=' "number";
will produce a
warning: useless precedence for '=' [-Wprecedence]
%precedence '='
^^^
*** Useless precedence and associativity
In case of both useless precedence and associativity, the issue is flagged
as follows:
%nonassoc '='
%%
exp: "var" '=' "number";
The warning is:
warning: useless precedence and associativity for '=' [-Wprecedence]
%nonassoc '='
^^^
** Empty rules
With help from Joel E. Denny and Gabriel Rassoul.
Empty rules (i.e., with an empty right-hand side) can now be explicitly
marked by the new %empty directive. Using %empty on a non-empty rule is
an error. The new -Wempty-rule warning reports empty rules without
%empty. On the following grammar:
%%
s: a b c;
a: ;
b: %empty;
c: 'a' %empty;
bison reports:
3.4-5: warning: empty rule without %empty [-Wempty-rule]
a: {}
^^
5.8-13: error: %empty on non-empty rule
c: 'a' %empty {};
^^^^^^
** Java skeleton improvements
The constants for token names were moved to the Lexer interface. Also, it
is possible to add code to the parser's constructors using "%code init"
and "%define init_throws".
Contributed by Paolo Bonzini.
The Java skeleton now supports push parsing.
Contributed by Dennis Heimbigner.
** C++ skeletons improvements
*** The parser header is no longer mandatory (lalr1.cc, glr.cc)
Using %defines is now optional. Without it, the needed support classes
are defined in the generated parser, instead of additional files (such as
location.hh, position.hh and stack.hh).
*** Locations are no longer mandatory (lalr1.cc, glr.cc)
Both lalr1.cc and glr.cc no longer require %location.
*** syntax_error exception (lalr1.cc)
The C++ parser features a syntax_error exception, which can be
thrown from the scanner or from user rules to raise syntax errors.
This facilitates reporting errors caught in sub-functions (e.g.,
rejecting too large integral literals from a conversion function
used by the scanner, or rejecting invalid combinations from a
factory invoked by the user actions).
*** %define api.value.type variant
This is based on a submission from Michiel De Wilde. With help
from Théophile Ranquet.
In this mode, complex C++ objects can be used as semantic values. For
instance:
%token <::std::string> TEXT;
%token <int> NUMBER;
%token SEMICOLON ";"
%type <::std::string> item;
%type <::std::list<std::string>> list;
%%
result:
list { std::cout << $1 << std::endl; }
;
list:
%empty { /* Generates an empty string list. */ }
| list item ";" { std::swap ($$, $1); $$.push_back ($2); }
;
item:
TEXT { std::swap ($$, $1); }
| NUMBER { $$ = string_cast ($1); }
;
*** %define api.token.constructor
When variants are enabled, Bison can generate functions to build the
tokens. This guarantees that the token type (e.g., NUMBER) is consistent
with the semantic value (e.g., int):
parser::symbol_type yylex ()
{
parser::location_type loc = ...;
...
return parser::make_TEXT ("Hello, world!", loc);
...
return parser::make_NUMBER (42, loc);
...
return parser::make_SEMICOLON (loc);
...
}
*** C++ locations
There are operator- and operator-= for 'location'. Negative line/column
increments can no longer underflow the resulting value.
2013-7-28 meld 1.7.4
====================
Features:
* Commit dialog can now automatically wrap commit messages (Kai Willadsen)
* Add Bazaar support for pushing changes, and improve sensitivity setting
(Louis des Landes)
* Support Subversion 1.8 (Yuri)
* Type-ahead-find search now works in folder comparisons (Kai Willadsen)
* Preference to swap pane order left = local (Kai Willadsen)
* Arch, Codeville and RCS are no longer supported (Kai Willadsen)
Fixes:
* When opening new tabs from the command line, bring new tab to the front
(Richard Simmons)
* Current chunk highlight is now customisable using gtkrc (Louis des
Landes)
* Syncpoints now prevent chunks from being re-merged, syncpoints move with
insertions, and disable automatic updating (Kai Willadsen)
* Various version control updates and fixes (Louis des Landes, Kai
Willadsen)
* Sensitivity fixes (Kai Willadsen)
* Translation string fixes (Marek Černocký)
Translations:
* Daniel Mustieles (es)
* Dimitris Spingos (el)
* Fran Diéguez (gl)
* Marek Černocký (cs)
* Matej Urbančič (sl)
* Piotr Drąg (pl)
Update DEPENDS
Upstream changes:
0.44 2012-11-24 13:17:02 PST-0800 (Karen Etheridge)
* Fix broken test in 5.17.6, where hash ordering is now randomized
(RT#81388, Karen Etheridge)
0.43 2012-05-20 17:34:04 PDT-0700
* Bump dependency on MooseX::Types to 0.35 to resolve issues with recent
MooseX::Types releases.
0.42 2012-04-23 11:08:19 PDT-0700
* Mark failing test due to Eval::Closure/Devel::Declare issues as TODO until
things are fixed, to at least allow recent versions to install without
errors.
0.41 Sun Mar 11 10:05:27 PDT 2012
* Add explicit dependency on Eval::Closure, in an effort to get more
diagnostics from failing cpantesters reports. No functionality changes.
0.40 Sat Mar 10 09:03:51 PST 2012
* Loosen a regexp in a test, to handle the new format emitted by Carp 1.25.
0.39 Sat Mar 10 00:54:18 GMT 2012
* The test suite now uses Test::Fatal instead of Test::Exception (Karen
Etheridge).
* Bump dependency on MooseX::Types::Structured to 0.24, which contains
more detailed error messages as well as some performance enhancements.
0.38 Fri Mar 9 23:43:07 GMT 2012
* Require B::Hooks::EndOfScope 0.10 and Module::Runtime 0.012, fixing various
perl 5.8 breakages.
Update DEPENDS
Upstream changes:
0.10 2013-03-15 13:09:48 PDT-0700 (Karen Etheridge)
* use quotes around attribute name in error messages (David Precious)
0.09 2012-12-01 14:16:14 PST-0800 (Karen Etheridge)
* Invalid tests that failed on perl 5.17.6 have been fixed (they were always
invalid, but the changes to hash key ordering only now made the tests
start failing in an obvious way) (RT#81419)
* unnecessary dependency on MooseX::Types removed
Upstream changes:
0.18 2013-05-13 12:34:52 PDT-0700
- make tests a bit more tolerant of slow systems, by waiting longer for
processes to die (RT#85229, Chisel Wright)
0.17 2013-04-20
- Makefile.PL now prevents installation on MSWin32
0.16 2013-04-14
- fix incompatibilities with Test::Builder 1.005+ (schwern, RT#76523)
- add missing dependency on the version of File::Path which added
make_path (RT#79169, Jonathan Sailor)
- add missing test dependency on Test::Exception (RT#70382)
- document the 'basedir' attribute and its behaviour (RT#83055)
- add 'documentation' keys for public attributes, to be used when
displaying --help (RT#54295)
Update BUILD_DEPENDS
Upstream changes:
0.56 2013-02-15 13:13:18 PST-0800
- depend on newest Path::Tiny, to regain 5.8.x compatibility (gone since
v0.52)
0.55 2013-02-12 10:02:55 PST-0800
- fix broken tests on win32 with file comparisons
0.54 2013-02-09 16:25:32 PST-0800
- fix broken tests on win32 with file comparisons
- allow configfiles called "0"
- support more mechanisms for overriding default configfile
- when using in conjunction with MooseX::ConfigFromFile, configfile value now
properly passed to new()
0.53 2013-02-05 09:59:00 PST-0800
- properly indicate optional dependency in tests using
MooseX::ConfigFromFile
0.52 2013-02-02 19:01:25 PST-0800
- tests converted from using Path::Class to Path::Tiny
0.51 2013-01-27 09:38:11 PST-0800
- missing test prereqs now declared (thanks for the automated reports, David
Cantrell!)
0.50 2012-12-27 00:20:56 PST-0800
- unbreak Catalyst::Runtime tests (etc) by keeping _getopt_full_usage in the
callstack. (RT#82249)
0.49 2012-12-26 10:13:41 PST-0800
- silence a warning in tests if the user does not have YAML::XS installed
(thanks for the report, Getty!)
- fix off-by-one issues in test plans if optional requirements are not met
0.48 2012-12-23 18:08:04 PST-0800
- documentation and tests amended to prefer usage of 'trait' over 'metaclass'
as much as possible
- print_usage_text() exposed as a public method, to make it easier for
consuming classes to modify the behaviour when usage text is printed
Upstream changes:
0.27 2013-03-28
- The latest Moose release (2.08) broke this module. This release fixes
MooseX::ClassAttribute to work with both new and old Mooses. Reported by
Jonathan Stowe. RT #84263.
Update DEPENDS
Upstream changes:
1.003000 - 2013-07-15
- fix composing roles that require methods provided by the other (RT#82711)
- document optional use of Class::XSAccessor with caveats
- fix constructor generated when creating a class with
create_class_with_roles when the superclass constructor hasn't been
generated yet
- fix extending the constructor generator using Moo classes/roles
- non-lazy attribute defaults are used when applying a role to an object
- updated META files to list prerequisites in proper phases
- $Method::Generate::Accessor::CurrentAttribute hashref contains
information about attribute currently being processed (available
to exception objects thrown by "isa" and "coerce")
- properly die when composing a module that isn't a Role
- fix passing attribute parameters for traits when inflating to Moose
- fix inflating method modifiers applied to multiple methods
- fix documentation for Sub::Quote::capture_unroll
- add documentation noting Sub::Quote's use of strictures
- fix FOREIGNBUILDARGS not being called if no attributes created
Upstream changes:
1.003001 - 2013-07-14
- fix test accidentally requiring Class::Method::Modifiers
1.003000 - 2013-07-14
- allow composing roles simultaneously that mutually require each other
(RT#82711)
- Fix _concrete_methods_of returning non-CODE entries
- fix broken implementation of method conflict resolution
(Perlmonks#1041015)
- add is_role method for checking if a given package is a role
- drop minimum perl version - code tests just fine on 5.6.1 and 5.6.2
1.002005 - 2013-02-01
- complain loudly if Class::Method::Modifiers is too old (and skip tests)
- don't use $_ as loop variable when calling arbitrary code
Upstream changes:
0.23 2013-01-26
- The new_events() watcher method blocked when using IO::Kqueue as the watcher
backend. Reported and patched by Jun Kuriyama.
0.22 2012-04-13
- Remove unnecessary Perl 5.10 requirement.
0.21 2012-02-03
- The implementation of the exclude feature did not work properly in several
cases. First, for the Inotify and KQueue watchers, when a new directory was
created that should have been excluded, it was not. Second, it didn't work
for files at all for these watchers. Reported by Jon Swartz. RT #73089.
Remove some unneeded comments.
Upstream changes;
2.1004 Fri, Jul 26, 2013
[BUG FIXES]
* 2.1003 was released with some bad metadata, which caused the prereq test
to fail.
2.1003 Fri, Jul 26, 2013
[OTHER]
* Releasing 2.0901 as stable.
2.0901-TRIAL Fri, Jun 21, 2013
[ENHANCEMENTS]
* The with_immutable() sub from Test::Moose now passes a boolean value to
the code block containing tests indicating whether or not the classes have
been made immutable. This can make for nicer test descriptions. (Dave
Rolsky)
* You can now use Specio types instead of Moose builtins or
MooseX::Types. As a bonus, Specio types inline coercion. However, this
support is still experimental (as is Specio), so use it with care. (Dave
Rolsky)
2.0900-TRIAL Sun, May 26, 2013
[API CHANGES]
* Fixed the Num builtin type to reject NaN, Inf, numbers with whitespace,
and other questionable strings. The MooseX::Types::LaxNum distro
implements the old behavior. RT#70539 (Upasana Shukla)
Upstream changes:
0.30 2013-06-24
- doy/data-visitor should probably be the canonical repository at this
point
0.29 2013-06-24
- The class callbacks to be run for an object are now chosen once, at the
start of visiting that object. Previously, it always looked through the
entire list of callbacks every time, in a loop in which the object in
question could be changed by the callback. Since the class callbacks are
only partially ordered, this lead to differences in whether a callback
would be called or not based on hash order. reported by Robin Smidsrd.
Upstream changes:
1.4 (2013-07-23)
BACKWARD INCOMPATIBLE pip now only installs stable versions by default, and offers a new --pre option to also find pre-release and development versions. (Pull #834)
BACKWARD INCOMPATIBLE Dropped support for Python 2.5. The minimum supported Python version for pip 1.4 is Python 2.6.
Added support for installing and building wheel archives. Thanks Daniel Holth, Marcus Smith, Paul Moore, and Michele Lacchia (Pull #845)
Applied security patch to pip's ssl support related to certificate DNS wildcard matching (http://bugs.python.org/issue17980).
To satisfy pip's setuptools requirement, pip now recommends setuptools>=0.8, not distribute. setuptools and distribute are now merged into one project called 'setuptools'. (Pull #1003)
pip will now warn when installing a file that is either hosted externally to the index or cannot be verified with a hash. In the future pip will default to not installing them and will require the flags -allow-external NAME, and -allow-insecure NAME respectively. (Pull #985)
If an already-downloaded or cached file has a bad hash, re-download it rather than erroring out. (Issue #963).
pip bundle and support for installing from pybundle files is now considered deprecated and will be removed in pip v1.5.
Fixed a number of issues (#413, #709, #634, #602, and #939) related to cleaning up and not reusing build directories. (Pull #865, #948)
Added a User Agent so that pip is identifiable in logs. (Pull #901)
Added ssl and -user support to get-pip.py. Thanks Gabriel de Perthuis. (Pull #895)
Fixed the proxy support, which was broken in pip 1.3.x (Pull #840)
Fixed issue #32 - pip fails when server does not send content-type header. Thanks Hugo Lopes Tavares and Kelsey Hightower (Pull #872).
"Vendorized" distlib as pip.vendor.distlib (https://distlib.readthedocs.org/).
Fixed git VCS backend with git 1.8.3. (Pull #967)
Upstream changes:
1.6932 2013-07-24 15:28:05 PDT
[Bug Fixes]
- Stop scanning .pm files for root installdeps target (e.g. carton apps)
1.6931 2013-07-24 14:50:59 PDT
[Bug Fixes]
- Use (patched) Parse::PMFile to parse packages and versions from current directory
rather than Module::Metadata from blib.
- Fixes a bug where install.json has bogus file path in provides
- Honor no_index metadata when scanning provides from .pm files
- no_index fatscript.pm since fatpacks bunch of external modules
1.6930 2013-07-24 13:46:10 PDT
[Bug Fixes]
- Fixed fatscript.pm being stripped, causing issues with Metadata inspection
- Bumped Module::CPANfile
1.6929 2013-07-24 11:45:48 PDT
[New Features]
- Include App/cpanminus/fatscript.pm which is exactly the same content as cpanm.
This allows both calling .pm as a script or reading the content to call with Scriptlet,
which would also make fatpacking cpanm (in another program!) easier.
- Removed the Share dir feature added in 1.6928 in favor of fatscript
1.6928 2013-07-23 14:10:20 PDT
[New Features]
- Installs cpanm executable to share dir for App-cpanminus, so that other applications
can run the specific version of cpanm without relying on user's $PATH or shebang
1.6927 2013-07-23 00:44:53 PDT
[New Features]
- Add experimental --cpanfile option to specify alternate cpanfile location
1.6926 2013-07-20 09:02:39 PDT
[Incompatible Changes]
- Log messages are printed to STDOUT rather than STDERR, except errors.
- --scandeps are now deprecated. Only in the documentation for now.
[Bug Fixes]
- Fixes a bug in printing "Expiring directories"
1.6925 2013-07-19 22:07:21 PDT
[Bug Fixes]
- Ignore leading/trailing spaces in PERL_CPANM_OPT #288 (ribasushi)
- Stop checking dependencies with --scandeps mode #286 (tazle)
[Improvements]
- Mask passwords in URI when printing them in terminal and log files #281 (xdg, thaljef)
- Added link to App::cpanminus::reporter #284 (garu)
[New Features]
- Added experimental --cpanmetadb option #279 (xdg)
1.6924 2013-07-16 11:36:56 PDT
[Bug Fixes]
- Sort MetaCPAN API results based on date (older one wins) to work around the issue
with Crixa-0.01 (https://github.com/CPAN-API/cpan-api/issues/274)
[Improvements]
- Document --with-develop
- Document fixes (oalders, garu)
- Added Perl::Strip for develop deps if you'd like to build fatpacked binary
This bug fix releases includes fixes for a couple crashing or memory
corrupting bugs, along with general code cleanups and build configuration
improvements, including fixing compatibility with automake 1.13 & 1.14.
Adam Jackson (1):
configure: Drop AM_MAINTAINER_MODE
Alan Coopersmith (14):
unifdef -U__UNIXOS2__
Update configure.ac initialization to X.Org standard form
config: Remove unnecessary calls from configure.ac
Move i_listlen in struct inclist for better packing in 64-bit builds
Remove fallbacks for Imake configuration, assume autoconf
Remove unnecessary casts from malloc/realloc calls
Convert more sprintf calls to snprintf
Fix a comment typo
Replace deprecated Automake INCLUDES variable with AM_CPPFLAGS
Mark fatalerr & catch as _X_NORETURN
Store len in a size_t instead of an int in redirect()
Bug 56091 - Unsafe use of strcpy() in makedepend
Assume signal handlers return void, as C89 requires
makedepend 1.0.5
Colin Walters (1):
autogen.sh: Implement GNOME Build API
Glenn Burkhardt (1):
Bd shares
Julien Cristau (2):
configure.ac: use AM_MAINTAINER_MODE
Don't crash if an option's argument is missing
Marko Lindqvist (1):
Bug 59005 - makedepend: Build with automake-1.13 broken
This release provides some fixes for static analysis warnings and other code
maintenance cleanups.
Alan Coopersmith (6):
Avoid closing inFile twice in CheckImakefileC if LogFatal returns
Ensure inFile is always closed on error in cppit()
Let configure pick cpp path on Solaris, instead of hardcoding in imakemdep.h
unifdef -U__UNIXOS2__
config: replace deprecated AM_CONFIG_HEADER with AC_CONFIG_HEADERS
imake 1.0.6
Eric S. Raymond (1):
Avoid use of low-level troff markup that can't be lifted structurally.
simple grammars, vs. the traditional lex/yacc approach, or the use of regular
expressions. The pyparsing module provides a library of classes that client
code uses to construct the grammar directly in Python code.
-----
0.9.6
-----
* Issue #44: Test failure on Python 2.4 when MD5 hash doesn't have a `.name`
attribute.
-----
0.9.5
-----
* Python #17980: Fix security vulnerability in SSL certificate validation.
-----
0.9.4
-----
* Issue #43: Fix issue (introduced in 0.9.1) with version resolution when
upgrading over other releases of Setuptools.
-----
0.9.3
-----
* Issue #42: Fix new ``AttributeError`` introduced in last fix.
-----
0.9.2
-----
* Issue #42: Fix regression where blank checksums would trigger an
``AttributeError``.
-----
0.9.1
-----
* Distribute #386: Allow other positional and keyword arguments to os.open.
* Corrected dependency on certifi mis-referenced in 0.9.
Version 0.18.3 - July 2013
* Runtime behaviour:
On Mac OS X systems, the setlocale() function now properly
invalidates loaded message catalogs when a locale has been set.
* Programming languages support:
- C++:
The gnu::autosprintf class now provides an assignment operator.
- Glade:
xgettext now supports GtkBuider file format used by Glade 3.
xgettext now also extracts contexts (msgctxt) from Glade 2 and
GtkBuider files.
- JavaScript:
xgettext now partially supports JavaScript. Since the current
JavaScript specification (ECMA-262) does not define the standard
set of formatting methods nor translation functions, the
implementation supports only a limited set of formatting methods
and translation functions commonly used in Gjs and other popular
JavaScript implemenations and libraries.
- Lua:
xgettext now supports Lua, using Ľubomír Remák's lua-gettext.
- Python:
xgettext and msgfmt's format string checking now recognize Python
format string in braced syntax (PEP 3101). xgettext now also
supports explicit string concatenation with '+' and handles
platform dependent line terminators (LF/CR/CRLF) transparently.
- Tcl:
Bug fix in xgettext Unicode escape handling.
- Vala:
xgettext now supports Vala.
* msgattrib now has --previous option to keep previous msgid when
making messages fuzzy, similar to msgmerge --previous.
* msgfmt now checks PO file headers more strictly with less
false-positives.
* 'gettextize' now checks macro directories specified with
AC_CONFIGURE_MACRO_DIRS in configure.ac.
* Portability:
- msginit now does not require GNU sed.
- The Makefile rule for generating en@quot and en@boldquot now uses
@SED@ variable instead of hard-coded 'sed' command to allow users
to supply GNU sed.
* Future backward-incompatibilities:
- In future Gettext versions, the files installed by 'gettextize'
will require Automake 1.10 or later. This will improve the
compatibility of user projects with newer Automake versions.
* Fixed thick line swap bug and added accuracy test for thick line
* Improved interface to SDL_framerateDelay
* Fixed 32bpp blending function for BGRA
* Fix for pixel blend routine
Upstream changes:
1.37 2013-02-24
- I now recommend you use Throwable instead of this module. It has a nicer,
more modern interface.
- Fixed various bugs and confusion in the docs.
1.36 2012-11-17
- Fixed some stupidity in the tests that appears to have been highlighted by
recent changes to Devel::StackTrace. Reported by Dan Horne. RT #81245.
1.35 2012-09-17
- Require Class::Data::Inheritable 0.02+.
1.34 2012-09-16
- 1.33 did not declare any prereqs. Oops. Reported by Roham McGovern. RT
#79677.
1.33 2012-09-16
- Fixed warning from basic.t on 5.17.x. RT #79121.
Update DEPENDS
Upstream changes:
0.24 - 2013-07-10
- Upgrade Num test, keep in sync w/ Moose (autarch)
- Improve documentation
0.23 - 2013-03-07
- Fix regression in subtypes defined with a string (for the parent test)
0.22 - 2013-03-04
- Allow subtyping of parameterized types (haarg)
- Extract SetObject and Numeric types into their own distributions
Various fixes.
* Added misc/ruby-additional.el for emacs24 support.
* misc/ruby-electric.el (ruby-electric-curlies): Automatically
indent closing curly brackets when
ruby-electric-newline-before-closing-bracket is true.
* misc/ruby-electric.el (ruby-electric-curlies): Fix the bug where
an open curly inserted in a string is always replaced with a
hash sign.
