pike.git / CHANGES

version» Context lines:

pike.git/CHANGES:172:      o Added a shorthand syntax for integer rages: xbit, where x is a    number between 1 and 31. This can be used as an example to indicate    that a string is 8 bits wide only: string(8bit)       This is equivalent to the range (0..255) but can be easier to parse.       Similarily int(1bit) is an alias for 'bool', and int(12bit) is    the same as int(0..4095).    - o The random(), random_string() and random_seed() might be more random -  -  On computers with a hardware pseudo random generator random() can -  return significantly more random numbers, however, this means that -  random_seed is a no-op on those machines. -  -  A side-effect of this is that random_string is now actually -  significantly faster on at least x86 cpu:s with rdrnd. -  -  Note: If you want cryptographically random data please use -  Crypto.Random.random_string unless you know for sure the random data -  returned by the RDRND instruction is random enough. -  -  +    New preprocessor features   -------------------------      o Support for the ", ##__VA_ARGS__" cpp feature.       This makes the ‘##’ token paste operator have a special meaning    when placed between a comma and a variable argument. If you write       | #define err(format, ...) f(debug)werror("ERROR: "+format, ##__VA_ARGS__)   
pike.git/CHANGES:952:       This can be useful while optimizing to identify reference cycles in    Pike data structures, so that the need for garbage collection can be    reduced.      o Most math functions (log, pow, exp sin, cos etc) can now take    integers as arguments in addition to a floating point number.       The result will still be a float, the argument will be converted.    + o The random(), random_string() and random_seed() might be more random +  +  On computers with a hardware pseudo random generator random() can +  return significantly more random numbers, however, this means that +  random_seed is a no-op on those machines. +  +  A side-effect of this is that random_string is now actually +  significantly faster on at least x86 cpu:s with rdrnd. +  +  Note: If you want cryptographically random data please use +  Crypto.Random.random_string unless you know for sure the random data +  returned by the RDRND instruction is random enough. +    Crypto and SSL   --------------      o Several identifiers have changed name    SSL.sslfile -> SSL.File    SSL.sslport -> SSL.Port    ... <add more, nilsson. :))>      o SSL.File: Changed client/server selection API.