pike.git
/
CHANGES
version
»
Context lines:
10
20
40
80
file
none
3
pike.git/CHANGES:38:
before resorting to Gmp.mpz objects for large numbers. o IPv6 Networking code in Pike has been updated to work with IPv6. This includes both low level fixes in the socket handling as well as high level changes such as IP parsing and protocol additions such as AAAA records in Protocol.DNS. o mysqls The Mysql glue can operate over SSL. Use the "mysqls://" protocol
-
in the Sql.Sql module to use this
secuity
feature.
+
in the Sql.Sql module to use this
security
feature.
o trace() can trace all threads The configure option --without-thread-trace has been removed, but instead the trace() function has been extended to make it possible to set the trace level in all threads simultaneously. o --help The Pike --help message has been improved and it is possible to retrieve further information about options and environment variables. In addition most of the tools and build scripts now
pike.git/CHANGES:77:
The built in functions upper_case and lower_case now also works on single characters, represented as integers. o hash The string hash functions is now byte-order independent. The old hash function is available as hash_7_4 or as hash when running in 7.4 compatibility mode or lower. o #warning A new The Pike preprocessor directive #warning has been added. It
-
simply
write
the rest of the line to stderr.
+
simply
writes
the rest of the line to stderr.
The Pike master: ---------------- o The new option --dumpversion prints out the Pike version in a more
-
easily
pared
way than --version.
+
easily
parsed
way than --version.
-
o The master now supplies argv to the started application, so it can
-
use
the create method
for execution. Some people find it a
more
-
elegant solution than having a main function.
+
o The master now supplies argv to the started application
's create()
+
callback
, so it can
be
used
for execution. Some people find it a
+
more elegant solution than having a main function.
o The -e Pike environment has been improved with a lot of convenience wrappings. When compiling code with pike -e the macro NOT(X) will expand to !(X) and CHAR(X) to 'X', making it easier to solve quote problems from a shell. If the return from a pike -e statement is a positive integer it will be used as pikes exit code. If the return
-
value is a string it will be
outputed
, with a "\n"
added
, if it
+
value is a string it will be
output
,
and
with a
trailing
"\n", if it
lacked one. Finally there is a predefined variable env that contains the environment variables as a string:string mapping. Building and installing pike: ----------------------------- o To simplify the process of building Pike source distributions it is now possible to bundle less common libraries such as Nettle with
-
Pike. The
bundle
, found in the bundle directory, will be compiled
+
Pike. The
bundles
, found in the bundle
/
directory, will be compiled
and statically linked if the no matching library is found on the system. o The Pike build process no longer builds a bootstrap pike, used to run various small programs to generate source files. This means that in order to build Pike from CVS you need the latest major version of
-
Pike installed on your system. Pike source distributions
contains
-
the generated files and
is
not affected (except
it
compiles
in less
-
time).
+
Pike installed on your system. Pike source distributions
will still
+
contain
the generated files and
are
not affected (except
they
compile
+
in less time).
o By default pike want you to build a documentation source file, i.e. "make && make doc && make install". This makes it possible for third party modules to integrate its documentation into the system Pike documentation. If you do not want to build a documentation source file, use "make install_nodoc" instead of "make install". Changes and additions to -x utilities: -------------------------------------- o rsif rsif can now work recursively in a file structure if given the flag -r or --recursive. Example: pike -x rsif -r 7.4 7.6 o benchmark A set of benchmarks is available in the benchmark tool. They are
-
based on the Great Computer Language Shootout, but
has
been
+
based on the Great Computer Language Shootout, but
have
been
modified to make more sense in the context of Pike and to test various aspects of Pike we suspect (or at least at one time
-
suspected)
performs
badly.
+
suspected)
perform
badly.
o cgrep
-
Context sensitive grep is very helpful when you are looking for
-
substrings that are common. The implemented search modes are:
+
Context sensitive grep
(grepping through tokenized code, at
+
present handling Pike and C source files)
is very helpful when
+
you are looking for substrings that are common. The implemented
+
search modes are:
o Complete token o Part of a token o Complete string literal o Part of a string literal o Part of a comment Example: $ cd Pike/7.6/src $ grep or * | wc -l 18907
pike.git/CHANGES:167:
src/dumpmodule.pike in the Pike source tree, but moved into the Pike builtin tools to facilitate dumping of external modules. o extract_locale Locale extractor utility used to extract localizable strings from an application into an xml format, to later be used by the Locale module. o monger A new utility to download, install and otherwise manage external
-
modules from the Fresh Pike project.
+
modules from the Fresh Pike project
(modules
.
gotpike.org).
New modules / classes / methods added: -------------------------------------- o Regexp.PCRE added to give libpcre support. Are you a closet-perlet? For those who missed the richer flora of regexp syntax that Perl supports, the Perl Compatible Regular Expression module is the answer. If you compile libpcre with UTF-8 support you will also get transparent wide string support. Several