4 references to BaseGetMembers
System.Management.Automation (4)
engine\MshMemberInfo.cs (3)
3373
PSObject.DotNetInstanceAdapter.
BaseGetMembers
<PSMemberInfo>(_psObject.ImmediateBaseObject))
3396
foreach (PSMemberInfo member in _psObject.InternalAdapter.
BaseGetMembers
<PSMemberInfo>(
3408
PSMemberInfoCollection<PSMemberInfo> members = PSObject.DotNetInstanceAdapter.
BaseGetMembers
<PSMemberInfo>(
engine\MshObject.cs (1)
2033
foreach (PSPropertyInfo member in particularAdapter.
BaseGetMembers
<PSPropertyInfo>(_immediateBaseObject))


Hello,
I am Genie, Business Development Manager.
I was surfing through your site and can see that you are offering Web
Development services to your clients.
We are an Indian Web Design and Development firm with over 7 years of
experience. In these tough times, where it is hard to maintain the top line,
we can help share the bottom-line for you.
We will be happy to help execute SEO & Web Design and Development projects
at a much lower cost than what you have in house - No compromise on quality!
We are at present partnering with over 30 firms from UK, US, Australia and
parts of Europe.
Our primary focus is:-
SEO
Web Design
Web Development
PPC
Flash Design
Graphic Designs
Web Copywriting
Database programming
Ecommerce Solutions
Do let me know if you are interested and I would be happy to share our
Methodologies, past work details and client Testimonials.
I look forward to your mail.
Kinds Regards,
Genie,
Business Development Manager
E-Mail<EMAIL_ADDRESS>Note: If you don’t want to receive any e-mails further, please mail us with
title unsubscribe.


Brother Hyrum
We arrived here safe and are all well I have been engaged in regulating the
Churches here as the disciples are numerous and the devil has made many
attempts to overthrow them it has been a serious Job but the Lord is with us
and we have overcome and have all things reular the work is breaking forth on
the right hand and on the left and there is a great Call for Elders in this
place we have received a letter from Oliver dated independence Jackson County
Missouri January the 29th 1831 these are the words which he has written saying
... thus reads most of the letter.
My Dearly Beloved Brother Hyrum
I have had much concern about you but I always remember you in my prayers
Calling upon god to keep you safe in spit of men or devils I think you had
better come into this country immediately for the Lord has commanded us that
we should call the elders of this church to gather unto this place as soon as
possible.
March forth this morning after being called out of my bed in the night to go a
small distance I went and had an awful struggle with satan but being armed
with the power of God he was cast out and the woman is clothed in her right
mind the Lord worth wonders in this land.
I want to see you all may the grace of God be and abide with you all even so
Amen
your Brother forever
PS. If you want to write Oliver direct your letter to independence Jackson
county Missouri
Harrison and Orson Pratt arrived here on Feb 27th they left our folks well
David Jackways has threatened to take father with a supreme writ in the spring
you had better come to Fayette and take father along with you come in a one
hourse wagon if you can do not come through Buffalo for they lie in wait for
you God protect you I am Joseph


- iodine
- This is a piece of software that lets you tunnel IPv4 data through a DNS server.  This tool is designed to create a command-and-control (C&C) channel over the DNS protocol, which is an effective tunnel out of almost every network.
- fraud-bridge
- fraud-bridge allows to tunnel TCP connections through ICMP, ICMPv6, DNS via UDP or DNS via UDP6. Project, not stable
- PyExfil
- Exfiltration tools inspired by Regin. Alpha Status.
- Exfil - Modular tool to test exfiltration techniques
- Exfil is a tool designed to exfiltrate data using various techniques, which allows a security team to test whether its monitoring system can effectively catch the exfiltration. The idea for Exfil came from a Twitter conversation between @averagesecguy, @ChrisJohnRiley, and @Ben0xA and was sparked by the TrustWave POS malware whitepaper available at https://gsr.trustwave.com/topics/placeholder-topic/point-of-sale-malware/.
- Multitun
- Efficiently and securely tunnel everything over a harmless looking WebSocket!
- Data Exfiltration Toolkit(DET)
- DET (is provided AS IS), is a proof of concept to perform Data Exfiltration using either single or multiple channel(s) at the same time. This is a Proof of Concept aimed at identifying possible DLP failures. This should never be used to exfiltrate sensitive/live data (say on an assessment) The idea was to create a generic toolkit to plug any kind of protocol/service to test implmented Network Monitoring and Data Leakage Prevention (DLP) solutions configuration, against different data exfiltration techniques.
- canisrufus
- A stealthy Python based Windows backdoor that uses Github as a command and control server
- Stunnel
-
- dnsftp
- Client/Server scripts to transfer files over DNS. Client scripts are small and only use native tools on the host OS.
- tcpovericmp
- TCP implementation over ICMP protocol to bypass firewalls
- icmptunnel
- Transparently tunnel your IP traffic through ICMP echo and reply packets.
- Outgoing port tester - http://letmeoutofyour.net/
-
- CloakifyFactory
- CloakifyFactory & the Cloakify Toolset - Data Exfiltration & Infiltration In Plain Sight; Evade DLP/MLS Devices; Social Engineering of Analysts; Defeat Data Whitelisting Controls; Evade AV Detection. Text-based steganography usings lists. Convert any file type (e.g. executables, Office, Zip, images) into a list of everyday strings. Very simple tools, powerful concept, limited only by your imagination.
- QRCode-Video-Data-Exfiltration
- Exfiltrate data with QR code videos generated from files by HTML5/JS.
- DNSExfiltrator
- DNSExfiltrator allows for transfering (exfiltrate) a file over a DNS request covert channel. This is basically a data leak testing tool allowing to exfiltrate data over a covert channel.
- system-bus-radio
- Transmits AM radio on computers without radio transmitting hardware.
- Data Exfiltration Toolkit(DET)
- DET (is provided AS IS), is a proof of concept to perform Data Exfiltration using either single or multiple channel(s) at the same time. The idea was to create a generic toolkit to plug any kind of protocol/service to test implmented Network Monitoring and Data Leakage Prevention (DLP) solutions configuration, against different data exfiltration techniques.
- EGRESSION
- EGRESSION is a tool that provides an instant view of how easy it is to upload sensitive data from any given network.
- Data Exfil Toolkit
- DET (is provided AS IS), is a proof of concept to perform Data Exfiltration using either single or multiple channel(s) at the same time. The idea was to create a generic toolkit to plug any kind of protocol/service.
- PyExfil
- This started as a PoC project but has later turned into something a bit more. Currently it's an Alpha-Alpha stage package, not yet tested (and will appriciate any feedbacks and commits) designed to show several techniques of data exfiltration is real world scenarios.
- pingfs - "True cloud storage" - Erin Ekman
- pingfs is a filesystem where the data is stored only in the Internet itself, as ICMP Echo packets (pings) travelling from you to remote servers and back again. It is implemented using raw sockets and FUSE, so superuser powers are required. Linux is the only intended target OS, portability is not a goal. Both IPv4 and IPv6 remote hosts are supported.
- Egress-Assess
-
- QRXfer
- Transfer files from Air gapped machines using QR codes
- icmptunnel
- 'icmptunnel' works by encapsulating your IP traffic in ICMP echo packets and sending them to your own proxy server. The proxy server decapsulates the packet and forwards the IP traffic. The incoming IP packets which are destined for the client are again encapsulated in ICMP reply packets and sent back to the client. The IP traffic is sent in the 'data' field of ICMP packets. RFC 792, which is IETF's rules governing ICMP packets, allows for an arbitrary data length for any type 0 (echo reply) or 8 (echo message) ICMP packets. So basically the client machine uses only the ICMP protocol to communicate with the proxy server. Applications running on the client machine are oblivious to this fact and work seamlessly.
- org.quietmodem.Quiet
- org.quietmodem.Quiet allows you to pass data through the speakers on your Android device. This library can operate either as a raw frame layer or as a UDP/TCP stack.
- Cachetak
Proof-of-concept program that is able to read and write arbitrary bits using HTTP server-side caching


Navigation state: Pose (rotation, translation) + velocity NOTE(frank): it does not make sense to make this a Lie group, but it is a 9D manifold.
|
|
| NavState () |
| | Default constructor.
|
| |
|
| NavState (const Rot3 &R, const Point3 &t, const Velocity3 &v) |
| | Construct from attitude, position, velocity.
|
| |
|
| NavState (const Pose3 &pose, const Velocity3 &v) |
| | Construct from pose and velocity.
|
| |
|
| NavState (const Matrix3 &R, const Vector9 tv) |
| | Construct from SO(3) and R^6.
|
| |
|
static NavState | Create (const Rot3 &R, const Point3 &t, const Velocity3 &v, OptionalJacobian< 9, 3 > H1, OptionalJacobian< 9, 3 > H2, OptionalJacobian< 9, 3 > H3) |
| | Named constructor with derivatives.
|
| |
|
static NavState | FromPoseVelocity (const Pose3 &pose, const Vector3 &vel, OptionalJacobian< 9, 6 > H1, OptionalJacobian< 9, 3 > H2) |
| | Named constructor with derivatives.
|
| |
|
|
NavState | retract (const Vector9 &v, OptionalJacobian< 9, 9 > H1=boost::none, OptionalJacobian< 9, 9 > H2=boost::none) const |
| | retract with optional derivatives
|
| |
|
Vector9 | localCoordinates (const NavState &g, OptionalJacobian< 9, 9 > H1=boost::none, OptionalJacobian< 9, 9 > H2=boost::none) const |
| | localCoordinates with optional derivatives
|
| |
|
static Eigen::Block< Vector9, 3, 1 > | dR (Vector9 &v) |
| |
|
static Eigen::Block< Vector9, 3, 1 > | dP (Vector9 &v) |
| |
|
static Eigen::Block< Vector9, 3, 1 > | dV (Vector9 &v) |
| |
|
static Eigen::Block< const Vector9, 3, 1 > | dR (const Vector9 &v) |
| |
|
static Eigen::Block< const Vector9, 3, 1 > | dP (const Vector9 &v) |
| |
|
static Eigen::Block< const Vector9, 3, 1 > | dV (const Vector9 &v) |
| |
| class | boost::serialization::access |
| |
|
|
|
const Rot3 & | attitude (OptionalJacobian< 3, 9 > H=boost::none) const |
| |
|
const Point3 & | position (OptionalJacobian< 3, 9 > H=boost::none) const |
| |
|
const Velocity3 & | velocity (OptionalJacobian< 3, 9 > H=boost::none) const |
| |
|
const Pose3 | pose () const |
| |
|
|
Matrix3 | R () const |
| | Return rotation matrix. Induces computation in quaternion mode.
|
| |
|
Quaternion | quaternion () const |
| | Return quaternion. Induces computation in matrix mode.
|
| |
|
Vector3 | t () const |
| | Return position as Vector3.
|
| |
|
const Vector3 & | v () const |
| | Return velocity as Vector3. Computation-free.
|
| |
|
Velocity3 | bodyVelocity (OptionalJacobian< 3, 9 > H=boost::none) const |
| |
|
Matrix7 | matrix () const |
| | Return matrix group representation, in MATLAB notation: nTb = [nRb 0 n_t; 0 nRb n_v; 0 0 1] With this embedding in GL(3), matrix product agrees with compose.
|
| |
|
| NavState | update (const Vector3 &b_acceleration, const Vector3 &b_omega, const double dt, OptionalJacobian< 9, 9 > F, OptionalJacobian< 9, 3 > G1, OptionalJacobian< 9, 3 > G2) const |
| | Integrate forward in time given angular velocity and acceleration in body frame Uses second order integration for position, returns derivatives except dt. More...
|
| |
|
Vector9 | coriolis (double dt, const Vector3 &omega, bool secondOrder=false, OptionalJacobian< 9, 9 > H=boost::none) const |
| | Compute tangent space contribution due to Coriolis forces.
|
| |
| Vector9 | correctPIM (const Vector9 &pim, double dt, const Vector3 &n_gravity, const boost::optional< Vector3 > &omegaCoriolis, bool use2ndOrderCoriolis=false, OptionalJacobian< 9, 9 > H1=boost::none, OptionalJacobian< 9, 9 > H2=boost::none) const |
| | Correct preintegrated tangent vector with our velocity and rotated gravity, taking into account Coriolis forces if omegaCoriolis is given. More...
|
| |


Ruby's Enumerable#CycleOct 31st
Photo credit: will_cyclist / Foter / CC BY-NC
Before we start talking about cycles, let's recall the Array. An array is something that can store data, like numbers or strings and looks like a bunch of items inside brackets, [], separated by commas:
array = ["duck", "duck", "goose"]
Here we have an Array of strings. What if we want to make it say, "duck duck goose"? Let's try puts:
puts array duck duck goose => nil
So it looks like we can get it to display each of the elements our array down a list! What if we want to go through this twice, so we can say "duck duck goose duck duck goose" ? Let's use print to make it appear on the same line. We can also use a little trick here by multiplying our array by 2:
print array*2 duckduckgooseduckduckgoose => nil
Yikes! That's not how we want it to look. Now, we can use a method called each to add spaces in between (actually, there are tons of ways to do this!), but let's look at how we can achieve this with cycle!
What exactly does cycle do? It will run through and do something to each element n number of times. Let's see what this looks like if we want to run through our array twice and print the result.
array.cycle(2) {|animal| print animal} duckduckgooseduckduckgoose => nil
You can see here we specify the number of times we want to cycle through, with (2). |animal| is where we decide what to call each element we are referring to, and print animal is our command we are telling it to do for every element
Now let's tell it to add a space after every time we print the element:
array.cycle(2) {|animal| print animal+" "} duck duck goose duck duck goose => nil
Looking good! But wait, we can do even more within cycle! What if we want it to print only "goose"? Here we just add an if statement. Let's keep cycling until we have 20 geese!! Remember, one cycle has 2 elements of "goose", so we run this 10 times:
array.cycle(10) {|animal| print animal+" " if animal=="goose"} goose goose goose goose goose goose goose goose goose goose => nil
Voila! I count 10 geese in total. Remember, cycle allows us to run through some n number of times while allowing us the flexibility of telling it exactly how and what to do for every element in our array. Oh, and cycle works with other things too!
question = "what?" question.cycle(10) {|x| print x} what?what?what?what?what?what?what?what?what?what? => nil


PERL590DELTA
Section: Perl Programmers Reference Guide (1)Updated: 2009-02-26
Index Return to Main Contents
NAME
perl590delta - what is new for perl v5.9.0DESCRIPTION
This document describes differences between the 5.8.0 release and the 5.9.0 release.Incompatible Changes
Hash Randomisation
Mainly due to security reasons, the ``random ordering'' of hashes has been made even more random. Previously while the order of hash elements from keys(), values(), and each() was essentially random, it was still repeatable. Now, however, the order varies between different runs of Perl.Perl has never guaranteed any ordering of the hash keys, and the ordering has already changed several times during the lifetime of Perl 5. Also, the ordering of hash keys has always been, and continues to be, affected by the insertion order.
The added randomness may affect applications.
One possible scenario is when output of an application has included hash data. For example, if you have used the Data::Dumper module to dump data into different files, and then compared the files to see whether the data has changed, now you will have false positives since the order in which hashes are dumped will vary. In general the cure is to sort the keys (or the values); in particular for Data::Dumper to use the "Sortkeys" option. If some particular order is really important, use tied hashes: for example the Tie::IxHash module which by default preserves the order in which the hash elements were added.
More subtle problem is reliance on the order of ``global destruction''. That is what happens at the end of execution: Perl destroys all data structures, including user data. If your destructors (the DESTROY subroutines) have assumed any particular ordering to the global destruction, there might be problems ahead. For example, in a destructor of one object you cannot assume that objects of any other class are still available, unless you hold a reference to them. If the environment variable PERL_DESTRUCT_LEVEL is set to a non-zero value, or if Perl is exiting a spawned thread, it will also destruct the ordinary references and the symbol tables that are no longer in use. You can't call a class method or an ordinary function on a class that has been collected that way.
The hash randomisation is certain to reveal hidden assumptions about some particular ordering of hash elements, and outright bugs: it revealed a few bugs in the Perl core and core modules.
To disable the hash randomisation in runtime, set the environment variable PERL_HASH_SEED to 0 (zero) before running Perl (for more information see ``PERL_HASH_SEED'' in perlrun), or to disable the feature completely in compile time, compile with "-DNO_HASH_SEED" (see INSTALL).
See ``Algorithmic Complexity Attacks'' in perlsec for the original rationale behind this change.
UTF-8 On Filehandles No Longer Activated By Locale
In Perl 5.8.0 all filehandles, including the standard filehandles, were implicitly set to be in Unicode UTF-8 if the locale settings indicated the use of UTF-8. This feature caused too many problems, so the feature was turned off and redesigned: see ``Core Enhancements''.Single-number v-strings are no longer v-strings before =>
The version strings or v-strings (see ``Version Strings'' in perldata) feature introduced in Perl 5.6.0 has been a source of some confusion--- especially when the user did not want to use it, but Perl thought it knew better. Especially troublesome has been the feature that before a ``=>'' a version string (a ``v'' followed by digits) has been interpreted as a v-string instead of a string literal. In other words:
%h = ( v65 => 42 );
has meant since Perl 5.6.0
%h = ( 'A' => 42 );
(at least in platforms of ASCII progeny) Perl 5.8.1 restored the more natural interpretation
%h = ( 'v65' => 42 );
The multi-number v-strings like v65.66 and 65.66.67 still continue to be v-strings in Perl 5.8.
(Win32) The -C Switch Has Been Repurposed
The -C switch has changed in an incompatible way. The old semantics of this switch only made sense in Win32 and only in the ``use utf8'' universe in 5.6.x releases, and do not make sense for the Unicode implementation in 5.8.0. Since this switch could not have been used by anyone, it has been repurposed. The behavior that this switch enabled in 5.6.x releases may be supported in a transparent, data-dependent fashion in a future release.For the new life of this switch, see ``UTF-8 no longer default under UTF-8 locales'', and ``-C'' in perlrun.
(Win32) The /d Switch Of cmd.exe
Since version 5.8.1, perl uses the /d switch when running the cmd.exe shell internally for system(), backticks, and when opening pipes to external programs. The extra switch disables the execution of AutoRun commands from the registry, which is generally considered undesirable when running external programs. If you wish to retain compatibility with the older behavior, set PERL5SHELL in your environment to "cmd /x/c".The $* variable has been removed
$*, which was deprecated in favor of the "/s" and "/m" regexp modifiers, has been removed.Core Enhancements
Assertions
Perl 5.9.0 has experimental support for assertions. Note that the user interface is not fully stabilized yet, and it may change until the 5.10.0 release. A new command-line switch, -A, is used to activate assertions, which are declared with the "assertions" pragma. See assertions.Defined-or operators
A new operator "//" (defined-or) has been implemented. The following statement:
$a // $b
is merely equivalent to
defined $a ? $a : $b
and
$c //= $d;
can be used instead of
$c = $d unless defined $c;
This operator has the same precedence and associativity as "||". It has a low-precedence counterpart, "err", which has the same precedence and associativity as "or". Special care has been taken to ensure that those operators Do What You Mean while not breaking old code, but some edge cases involving the empty regular expression may now parse differently. See perlop for details.
UTF-8 no longer default under UTF-8 locales
In Perl 5.8.0 many Unicode features were introduced. One of them was found to be of more nuisance than benefit: the automagic (and silent) ``UTF-8-ification'' of filehandles, including the standard filehandles, if the user's locale settings indicated use of UTF-8.For example, if you had "en_US.UTF-8" as your locale, your STDIN and STDOUT were automatically ``UTF-8'', in other words an implicit binmode(..., ``:utf8'') was made. This meant that trying to print, say, chr(0xff), ended up printing the bytes 0xc3 0xbf. Hardly what you had in mind unless you were aware of this feature of Perl 5.8.0. The problem is that the vast majority of people weren't: for example in RedHat releases 8 and 9 the default locale setting is UTF-8, so all RedHat users got UTF-8 filehandles, whether they wanted it or not. The pain was intensified by the Unicode implementation of Perl 5.8.0 (still) having nasty bugs, especially related to the use of s/// and tr///. (Bugs that have been fixed in 5.8.1)
Therefore a decision was made to backtrack the feature and change it from implicit silent default to explicit conscious option. The new Perl command line option "-C" and its counterpart environment variable PERL_UNICODE can now be used to control how Perl and Unicode interact at interfaces like I/O and for example the command line arguments. See ``-C'' in perlrun and ``PERL_UNICODE'' in perlrun for more information.
Unsafe signals again available
In Perl 5.8.0 the so-called ``safe signals'' were introduced. This means that Perl no longer handles signals immediately but instead ``between opcodes'', when it is safe to do so. The earlier immediate handling easily could corrupt the internal state of Perl, resulting in mysterious crashes.However, the new safer model has its problems too. Because now an opcode, a basic unit of Perl execution, is never interrupted but instead let to run to completion, certain operations that can take a long time now really do take a long time. For example, certain network operations have their own blocking and timeout mechanisms, and being able to interrupt them immediately would be nice.
Therefore perl 5.8.1 introduced a ``backdoor'' to restore the pre-5.8.0 (pre-5.7.3, really) signal behaviour. Just set the environment variable PERL_SIGNALS to "unsafe", and the old immediate (and unsafe) signal handling behaviour returns. See ``PERL_SIGNALS'' in perlrun and ``Deferred Signals (Safe Signals)'' in perlipc.
In completely unrelated news, you can now use safe signals with POSIX::SigAction. See ``POSIX::SigAction'' in POSIX.
Tied Arrays with Negative Array Indices
Formerly, the indices passed to "FETCH", "STORE", "EXISTS", and "DELETE" methods in tied array class were always non-negative. If the actual argument was negative, Perl would call FETCHSIZE implicitly and add the result to the index before passing the result to the tied array method. This behaviour is now optional. If the tied array class contains a package variable named $NEGATIVE_INDICES which is set to a true value, negative values will be passed to "FETCH", "STORE", "EXISTS", and "DELETE" unchanged.local ${$x}
The syntaxes
local ${$x} local @{$x} local %{$x}
now do localise variables, given that the $x is a valid variable name.
Unicode Character Database 4.0.0
The copy of the Unicode Character Database included in Perl 5.8 has been updated to 4.0.0 from 3.2.0. This means for example that the Unicode character properties are as in Unicode 4.0.0.Miscellaneous Enhancements
"unpack()" now defaults to unpacking the $_."map" in void context is no longer expensive. "map" is now context aware, and will not construct a list if called in void context.
If a socket gets closed by the server while printing to it, the client now gets a SIGPIPE. While this new feature was not planned, it fell naturally out of PerlIO changes, and is to be considered an accidental feature.
PerlIO::get_layers(FH) returns the names of the PerlIO layers active on a filehandle.
PerlIO::via layers can now have an optional UTF8 method to indicate whether the layer wants to ``auto-:utf8'' the stream.
utf8::is_utf8() has been added as a quick way to test whether a scalar is encoded internally in UTF-8 (Unicode).
Modules and Pragmata
Updated Modules And Pragmata
The following modules and pragmata have been updated since Perl 5.8.0:- base
- B::Bytecode
- In much better shape than it used to be. Still far from perfect, but maybe worth a try.
- B::Concise
- B::Deparse
- Benchmark
- An optional feature, ":hireswallclock", now allows for high resolution wall clock times (uses Time::HiRes).
- ByteLoader
- See B::Bytecode.
- bytes
- Now has bytes::substr.
- CGI
- charnames
- One can now have custom character name aliases.
- CPAN
- There is now a simple command line frontend to the CPAN.pm module called cpan.
- Data::Dumper
- A new option, Pair, allows choosing the separator between hash keys and values.
- DB_File
- Devel::PPPort
- Digest::MD5
- Encode
-
Significant updates on the encoding pragma functionality
(tr/// and the DATA filehandle, formats).
If a filehandle has been marked as to have an encoding, unmappable characters are detected already during input, not later (when the corrupted data is being used).
The ISO 8859-6 conversion table has been corrected (the 0x30..0x39 erroneously mapped to U+0660..U+0669, instead of U+0030..U+0039). The GSM 03.38 conversion did not handle escape sequences correctly. The UTF-7 encoding has been added (making Encode feature-complete with Unicode::String).
- fields
- libnet
- Math::BigInt
-
A lot of bugs have been fixed since v1.60, the version included in Perl
v5.8.0. Especially noteworthy are the bug in Calc that caused div and mod to
fail for some large values, and the fixes to the handling of bad inputs.
Some new features were added, e.g. the broot() method, you can now pass parameters to config() to change some settings at runtime, and it is now possible to trap the creation of NaN and infinity.
As usual, some optimizations took place and made the math overall a tad faster. In some cases, quite a lot faster, actually. Especially alternative libraries like Math::BigInt::GMP benefit from this. In addition, a lot of the quite clunky routines like fsqrt() and flog() are now much much faster.
- MIME::Base64
- NEXT
- Diamond inheritance now works.
- Net::Ping
- PerlIO::scalar
- Reading from non-string scalars (like the special variables, see perlvar) now works.
- podlators
- Pod::LaTeX
- PodParsers
- Pod::Perldoc
- Complete rewrite. As a side-effect, no longer refuses to startup when run by root.
- Scalar::Util
- New utilities: refaddr, isvstring, looks_like_number, set_prototype.
- Storable
- Can now store code references (via B::Deparse, so not foolproof).
- strict
-
Earlier versions of the strict pragma did not check the parameters
implicitly passed to its ``import'' (use) and ``unimport'' (no) routine.
This caused the false idiom such as:
use strict qw(@ISA); @ISA = qw(Foo);
This however (probably) raised the false expectation that the strict refs, vars and subs were being enforced (and that @ISA was somehow ``declared''). But the strict refs, vars, and subs are not enforced when using this false idiom.
Starting from Perl 5.8.1, the above will cause an error to be raised. This may cause programs which used to execute seemingly correctly without warnings and errors to fail when run under 5.8.1. This happens because
use strict qw(@ISA);
will now fail with the error:
Unknown 'strict' tag(s) '@ISA'
The remedy to this problem is to replace this code with the correct idiom:
use strict; use vars qw(@ISA); @ISA = qw(Foo);
- Term::ANSIcolor
- Test::Harness
- Now much more picky about extra or missing output from test scripts.
- Test::More
- Test::Simple
- Text::Balanced
- Time::HiRes
- Use of nanosleep(), if available, allows mixing subsecond sleeps with alarms.
- threads
- Several fixes, for example for join() problems and memory leaks. In some platforms (like Linux) that use glibc the minimum memory footprint of one ithread has been reduced by several hundred kilobytes.
- threads::shared
- Many memory leaks have been fixed.
- Unicode::Collate
- Unicode::Normalize
- Win32::GetFolderPath
- Win32::GetOSVersion
- Now returns extra information.
Utility Changes
The "h2xs" utility now produces a more modern layout: Foo-Bar/lib/Foo/Bar.pm instead of Foo/Bar/Bar.pm. Also, the boilerplate test is now called t/Foo-Bar.t instead of t/1.t.The Perl debugger (lib/perl5db.pl) has now been extensively documented and bugs found while documenting have been fixed.
"perldoc" has been rewritten from scratch to be more robust and feature rich.
"perlcc -B" works now at least somewhat better, while "perlcc -c" is rather more broken. (The Perl compiler suite as a whole continues to be experimental.)
New Documentation
perl573delta has been added to list the differences between the (now quite obsolete) development releases 5.7.2 and 5.7.3.perl58delta and perl581delta have been added: these are the perldeltas of 5.8.0 and 5.8.1, detailing the differences respectively between 5.6.0 and 5.8.0, and between 5.8.0 and 5.8.1.
perlartistic has been added: it is the Artistic License in pod format, making it easier for modules to refer to it.
perlcheat has been added: it is a Perl cheat sheet.
perlgpl has been added: it is the GNU General Public License in pod format, making it easier for modules to refer to it.
perlmacosx has been added to tell about the installation and use of Perl in Mac OS X.
perlos400 has been added to tell about the installation and use of Perl in OS/400 PASE.
perlreref has been added: it is a regular expressions quick reference.
Installation and Configuration Improvements
The UNIX standard Perl location, /usr/bin/perl, is no longer overwritten by default if it exists. This change was very prudent because so many UNIX vendors already provide a /usr/bin/perl, but simultaneously many system utilities may depend on that exact version of Perl, so better not to overwrite it.One can now specify installation directories for site and vendor man and HTML pages, and site and vendor scripts. See INSTALL.
One can now specify a destination directory for Perl installation by specifying the DESTDIR variable for "make install". (This feature is slightly different from the previous "Configure -Dinstallprefix=...".) See INSTALL.
gcc versions 3.x introduced a new warning that caused a lot of noise during Perl compilation: "gcc -Ialreadyknowndirectory (warning: changing search order)". This warning has now been avoided by Configure weeding out such directories before the compilation.
One can now build subsets of Perl core modules by using the Configure flags "-Dnoextensions=..." and "-Donlyextensions=...", see INSTALL.
Platform-specific enhancements
In Cygwin Perl can now be built with threads ("Configure -Duseithreads"). This works with both Cygwin 1.3.22 and Cygwin 1.5.3.In newer FreeBSD releases Perl 5.8.0 compilation failed because of trying to use malloc.h, which in FreeBSD is just a dummy file, and a fatal error to even try to use. Now malloc.h is not used.
Perl is now known to build also in Hitachi HI-UXMPP.
Perl is now known to build again in LynxOS.
Mac OS X now installs with Perl version number embedded in installation directory names for easier upgrading of user-compiled Perl, and the installation directories in general are more standard. In other words, the default installation no longer breaks the Apple-provided Perl. On the other hand, with "Configure -Dprefix=/usr" you can now really replace the Apple-supplied Perl (please be careful).
Mac OS X now builds Perl statically by default. This change was done mainly for faster startup times. The Apple-provided Perl is still dynamically linked and shared, and you can enable the sharedness for your own Perl builds by "Configure -Duseshrplib".
Perl has been ported to IBM's OS/400 PASE environment. The best way to build a Perl for PASE is to use an AIX host as a cross-compilation environment. See README.os400.
Yet another cross-compilation option has been added: now Perl builds on OpenZaurus, an Linux distribution based on Mandrake + Embedix for the Sharp Zaurus PDA. See the Cross/README file.
Tru64 when using gcc 3 drops the optimisation for toke.c to "-O2" because of gigantic memory use with the default "-O3".
Tru64 can now build Perl with the newer Berkeley DBs.
Building Perl on WinCE has been much enhanced, see README.ce and README.perlce.
Selected Bug Fixes
Closures, eval and lexicals
There have been many fixes in the area of anonymous subs, lexicals and closures. Although this means that Perl is now more ``correct'', it is possible that some existing code will break that happens to rely on the faulty behaviour. In practice this is unlikely unless your code contains a very complex nesting of anonymous subs, evals and lexicals.Generic fixes
If an input filehandle is marked ":utf8" and Perl sees illegal UTF-8 coming in when doing "<FH>", if warnings are enabled a warning is immediately given - instead of being silent about it and Perl being unhappy about the broken data later. (The ":encoding(utf8)" layer also works the same way.)binmode(SOCKET, ``:utf8'') only worked on the input side, not on the output side of the socket. Now it works both ways.
For threaded Perls certain system database functions like getpwent() and getgrent() now grow their result buffer dynamically, instead of failing. This means that at sites with lots of users and groups the functions no longer fail by returning only partial results.
Perl 5.8.0 had accidentally broken the capability for users to define their own uppercase<->lowercase Unicode mappings (as advertised by the Camel). This feature has been fixed and is also documented better.
In 5.8.0 this
$some_unicode .= <FH>;
didn't work correctly but instead corrupted the data. This has now been fixed.
Tied methods like FETCH etc. may now safely access tied values, i.e. resulting in a recursive call to FETCH etc. Remember to break the recursion, though.
At startup Perl blocks the SIGFPE signal away since there isn't much Perl can do about it. Previously this blocking was in effect also for programs executed from within Perl. Now Perl restores the original SIGFPE handling routine, whatever it was, before running external programs.
Linenumbers in Perl scripts may now be greater than 65536, or 2**16. (Perl scripts have always been able to be larger than that, it's just that the linenumber for reported errors and warnings have ``wrapped around''.) While scripts that large usually indicate a need to rethink your code a bit, such Perl scripts do exist, for example as results from generated code. Now linenumbers can go all the way to<PHONE_NUMBER>, or 2**32.
Platform-specific fixes
Linux- *
- Setting $0 works again (with certain limitations that Perl cannot do much about: see ``$0'' in perlvar)
HP-UX
- *
- Setting $0 now works.
VMS
- *
- Configuration now tests for the presence of "poll()", and IO::Poll now uses the vendor-supplied function if detected.
- *
- A rare access violation at Perl start-up could occur if the Perl image was installed with privileges or if there was an identifier with the subsystem attribute set in the process's rightslist. Either of these circumstances triggered tainting code that contained a pointer bug. The faulty pointer arithmetic has been fixed.
- *
- The length limit on values (not keys) in the %ENV hash has been raised from 255 bytes to 32640 bytes (except when the PERL_ENV_TABLES setting overrides the default use of logical names for %ENV). If it is necessary to access these long values from outside Perl, be aware that they are implemented using search list logical names that store the value in pieces, each 255-byte piece (up to 128 of them) being an element in the search list. When doing a lookup in %ENV from within Perl, the elements are combined into a single value. The existing VMS-specific ability to access individual elements of a search list logical name via the $ENV{'foo;N'} syntax (where N is the search list index) is unimpaired.
- *
- The piping implementation now uses local rather than global DCL symbols for inter-process communication.
- *
- File::Find could become confused when navigating to a relative directory whose name collided with a logical name. This problem has been corrected by adding directory syntax to relative path names, thus preventing logical name translation.
Win32
- *
- A memory leak in the fork() emulation has been fixed.
- *
- The return value of the ioctl() built-in function was accidentally broken in 5.8.0. This has been corrected.
- *
- The internal message loop executed by perl during blocking operations sometimes interfered with messages that were external to Perl. This often resulted in blocking operations terminating prematurely or returning incorrect results, when Perl was executing under environments that could generate Windows messages. This has been corrected.
- *
- Pipes and sockets are now automatically in binary mode.
- *
- The four-argument form of select() did not preserve $! (errno) properly when there were errors in the underlying call. This is now fixed.
- *
- The ``CR CR LF'' problem of has been fixed, binmode(FH, ``:crlf'') is now effectively a no-op.
New or Changed Diagnostics
All the warnings related to pack() and unpack() were made more informative and consistent.Changed A thread exited while %d threads were running
The old version
A thread exited while %d other threads were still running
was misleading because the ``other'' included also the thread giving the warning.
Removed Attempt to clear a restricted hash
It is not illegal to clear a restricted hash, so the warning was removed.New Illegal declaration of anonymous subroutine
You must specify the block of code for "sub".Changed Invalid range %s in transliteration operator
The old version
Invalid [] range "%s" in transliteration operator
was simply wrong because there are no ``[] ranges'' in tr///.
New Missing control char name in \c
Self-explanatory.New Newline in left-justified string for %s
The padding spaces would appear after the newline, which is probably not what you had in mind.New Possible precedence problem on bitwise %c operator
If you think this
$x & $y == 0
tests whether the bitwise AND of $x and $y is zero, you will like this warning.
New read() on %s filehandle %s
You cannot read() (or sysread()) from a closed or unopened filehandle.New Tied variable freed while still in use
Something pulled the plug on a live tied variable, Perl plays safe by bailing out.New To%s: illegal mapping '%s'
An illegal user-defined Unicode casemapping was specified.New Use of freed value in iteration
Something modified the values being iterated over. This is not good.Changed Internals
These news matter to you only if you either write XS code or like to know about or hack Perl internals (using Devel::Peek or any of the "B::" modules counts), or like to run Perl with the "-D" option.The embedding examples of perlembed have been reviewed to be up to date and consistent: for example, the correct use of PERL_SYS_INIT3() and PERL_SYS_TERM().
Extensive reworking of the pad code (the code responsible for lexical variables) has been conducted by Dave Mitchell.
Extensive work on the v-strings by John Peacock.
UTF-8 length and position cache: to speed up the handling of Unicode (UTF-8) scalars, a cache was introduced. Potential problems exist if an extension bypasses the official APIs and directly modifies the PV of an SV: the UTF-8 cache does not get cleared as it should.
APIs obsoleted in Perl 5.8.0, like sv_2pv, sv_catpvn, sv_catsv, sv_setsv, are again available.
Certain Perl core C APIs like cxinc and regatom are no longer available at all to code outside the Perl core of the Perl core extensions. This is intentional. They never should have been available with the shorter names, and if you application depends on them, you should (be ashamed and) contact perl5-porters to discuss what are the proper APIs.
Certain Perl core C APIs like "Perl_list" are no longer available without their "Perl_" prefix. If your XS module stops working because some functions cannot be found, in many cases a simple fix is to add the "Perl_" prefix to the function and the thread context "aTHX_" as the first argument of the function call. This is also how it should always have been done: letting the Perl_-less forms to leak from the core was an accident. For cleaner embedding you can also force this for all APIs by defining at compile time the cpp define PERL_NO_SHORT_NAMES.
Perl_save_bool() has been added.
Regexp objects (those created with "qr") now have S-magic rather than R-magic. This fixed regexps of the form /...(??{...;$x})/ to no longer ignore changes made to $x. The S-magic avoids dropping the caching optimization and making (??{...}) constructs obscenely slow (and consequently useless). See also ``Magic Variables'' in perlguts. Regexp::Copy was affected by this change.
The Perl internal debugging macros DEBUG() and DEB() have been renamed to PERL_DEBUG() and PERL_DEB() to avoid namespace conflicts.
"-DL" removed (the leaktest had been broken and unsupported for years, use alternative debugging mallocs or tools like valgrind and Purify).
Verbose modifier "v" added for "-DXv" and "-Dsv", see perlrun.
New Tests
In Perl 5.8.0 there were about 69000 separate tests in about 700 test files, in Perl 5.9.0 there are about 77000 separate tests in about 780 test files. The exact numbers depend on the Perl configuration and on the operating system platform.Known Problems
The hash randomisation mentioned in ``Incompatible Changes'' is definitely problematic: it will wake dormant bugs and shake out bad assumptions.Many of the rarer platforms that worked 100% or pretty close to it with perl 5.8.0 have been left a little bit untended since their maintainers have been otherwise busy lately, and therefore there will be more failures on those platforms. Such platforms include Mac OS Classic, IBM z/OS (and other EBCDIC platforms), and NetWare. The most common Perl platforms (Unix and Unix-like, Microsoft platforms, and VMS) have large enough testing and expert population that they are doing well.
Tied hashes in scalar context
Tied hashes do not currently return anything useful in scalar context, for example when used as boolean tests:
if (%tied_hash) { ... }
The current nonsensical behaviour is always to return false, regardless of whether the hash is empty or has elements.
The root cause is that there is no interface for the implementors of tied hashes to implement the behaviour of a hash in scalar context.
Net::Ping 450_service and 510_ping_udp failures
The subtests 9 and 18 of lib/Net/Ping/t/450_service.t, and the subtest 2 of lib/Net/Ping/t/510_ping_udp.t might fail if you have an unusual networking setup. For example in the latter case the test is trying to send a UDP ping to the IP address <IP_ADDRESS>.B::C
The C-generating compiler backend B::C (the frontend being "perlcc -c") is even more broken than it used to be because of the extensive lexical variable changes. (The good news is that B::Bytecode and ByteLoader are better than they used to be.)Platform Specific Problems
EBCDIC Platforms
IBM z/OS and other EBCDIC platforms continue to be problematic regarding Unicode support. Many Unicode tests are skipped when they really should be fixed.Cygwin 1.5 problems
In Cygwin 1.5 the io/tell and op/sysio tests have failures for some yet unknown reason. In 1.5.5 the threads tests stress_cv, stress_re, and stress_string are failing unless the environment variable PERLIO is set to ``perlio'' (which makes also the io/tell failure go away).Perl 5.8.1 does build and work well with Cygwin 1.3: with (uname -a) "CYGWIN_NT-5.0 ... 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 ..." a 100% ``make test'' was achieved with "Configure -des -Duseithreads".
HP-UX: HP cc warnings about sendfile and sendpath
With certain HP C compiler releases (e.g. B.11.11.02) you will get many warnings like this (lines wrapped for easier reading):
cc: "/usr/include/sys/socket.h", line 504: warning 562: Redeclaration of "sendfile" with a different storage class specifier: "sendfile" will have internal linkage. cc: "/usr/include/sys/socket.h", line 505: warning 562: Redeclaration of "sendpath" with a different storage class specifier: "sendpath" will have internal linkage.
The warnings show up both during the build of Perl and during certain lib/ExtUtils tests that invoke the C compiler. The warning, however, is not serious and can be ignored.
IRIX: t/uni/tr_7jis.t falsely failing
The test t/uni/tr_7jis.t is known to report failure under 'make test' or the test harness with certain releases of IRIX (at least IRIX 6.5 and MIPSpro Compilers Version <IP_ADDRESS>m), but if run manually the test fully passes.Mac OS X: no usemymalloc
The Perl malloc ("-Dusemymalloc") does not work at all in Mac OS X. This is not that serious, though, since the native malloc works just fine.Tru64: No threaded builds with GNU cc (gcc)
In the latest Tru64 releases (e.g. v5.1B or later) gcc cannot be used to compile a threaded Perl (-Duseithreads) because the system "<pthread.h>" file doesn't know about gcc.Win32: sysopen, sysread, syswrite
As of the 5.8.0 release, sysopen()/sysread()/syswrite() do not behave like they used to in 5.6.1 and earlier with respect to ``text'' mode. These built-ins now always operate in ``binary'' mode (even if sysopen() was passed the O_TEXT flag, or if binmode() was used on the file handle). Note that this issue should only make a difference for disk files, as sockets and pipes have always been in ``binary'' mode in the Windows port. As this behavior is currently considered a bug, compatible behavior may be re-introduced in a future release. Until then, the use of sysopen(), sysread() and syswrite() is not supported for ``text'' mode operations.TODO
Here are some things that are planned for perl 5.10.0 :- *
- Various Copy-On-Write techniques will be investigated in hopes of speeding up Perl.
- *
- CPANPLUS, Inline, and Module::Build will become core modules.
- *
- The ability to write true lexically scoped pragmas will be introduced, perhaps via a "pragma" pragma.
- *
- Work will continue on the bytecompiler and byteloader.
- *
- v-strings as they currently exist are scheduled to be deprecated. The v-less form (1.2.3) will become a ``version object'' when used with "use", "require", and $VERSION. $^V will also be a ``version object'' so the printf(``%vd'',...) construct will no longer be needed. The v-ful version (v1.2.3) will become obsolete. The equivalence of strings and v-strings (e.g. that currently 5.8.0 is equal to ``\5\8\0'') will go away. There may be no deprecation warning for v-strings, though: it is quite hard to detect when v-strings are being used safely, and when they are not.
Reporting Bugs
If you find what you think is a bug, you might check the articles recently posted to the comp.lang.perl.misc newsgroup and the perl bug database at http://bugs.perl.org/. There may also be information at http://www.perl.com/, the Perl Home Page.If you believe you have an unreported bug, please run the perlbug program included with your release. Be sure to trim your bug down to a tiny but sufficient test case. Your bug report, along with the output of "perl -V", will be sent off to<EMAIL_ADDRESS>to be analysed by the Perl porting team. You can browse and search the Perl 5 bugs at http://bugs.perl.org/.
SEE ALSO
The Changes file for exhaustive details on what changed.The INSTALL file for how to build Perl.
The README file for general stuff.
The Artistic and Copying files for copyright information.
Index
- NAME
- DESCRIPTION
- Incompatible Changes
- Core Enhancements
- Modules and Pragmata
- Utility Changes
- New Documentation
- Installation and Configuration Improvements
- Selected Bug Fixes
- New or Changed Diagnostics
-
- Changed A thread exited while %d threads were running
- Removed Attempt to clear a restricted hash
- New Illegal declaration of anonymous subroutine
- Changed Invalid range %s in transliteration operator
- New Missing control char name in \c
- New Newline in left-justified string for %s
- New Possible precedence problem on bitwise %c operator
- New read() on %s filehandle %s
- New Tied variable freed while still in use
- New To%s: illegal mapping '%s'
- New Use of freed value in iteration
- Changed Internals
- New Tests
- Known Problems
- Platform Specific Problems
- TODO
- Reporting Bugs
- SEE ALSO
This document was created by man2html, using the manual pages.
Time: 05:29:07 GMT, December 24, 2015


--- layout: post status: publish published: true title: Xml Serializable & Serializable author: display_name: Tomas Restrepo login: tomasr email<EMAIL_ADDRESS>url: http://winterdom.com/ author_login: tomasr author_email<EMAIL_ADDRESS>author_url: http://winterdom.com/ wordpress_id: 401 wordpress_url: http://winterdom.com/2003/06/xmlserializableserializable date: '2003-06-23 19:57:35 +0000' date_gmt: '2003-06-23 19:57:35 +0000' categories: - ".NET" tags: [] comments: - id: 294 author: Philip Canarsky author_email<EMAIL_ADDRESS>author_url: '' date: '2003-06-26 11:44:55 +0000' date_gmt: '2003-06-26 11:44:55 +0000' content: |
This 'feature' (the dataset not being marked as serializable) has caused me pain as well.
What was your work around?
- id: 295 author: Tomas Restrepo author_email<EMAIL_ADDRESS>author_url: http://www.winterdom.com/weblog date: '2003-06-27 03:54:13 +0000' date_gmt: '2003-06-27 03:54:13 +0000' content: |So far, none... Perhaps I'll just write a small script to add them, I don't know...
- id: 296 author: James author_email<EMAIL_ADDRESS>author_url: '' date: '2003-07-28 02:45:03 +0000' date_gmt: '2003-07-28 02:45:03 +0000' content: |any suggestion?
i have the same problem.
I need to make the creattion automatically so that it can be done in baseline build.
Any guru can give me some hints.
Thanks.
<EMAIL_ADDRESS>One thing that has been bugging me about XSD.EXE lately is the fact
that when using it to generate typed classes from an XSD (with the /c switch), the
generated classes won't also be marked as [Serializable]. I've been trying to come
up with a case where an XmlSerializable class generated by XSD.EXE wouldn't also be
potentially Remoting-Serializable, but have come emptu handed. Any examples?
Granted, this is not the focus of the tool, but I think it would be
fairly useful and not too troublesome. Anyone cares to agree/disagree?


We use wusa.exe to extract a CAB file (cabinet archive file) to our secure location
wusa c:\users\user1\desktop\poc.tmp /extract:c:\windows\system32\sysprep
Here in the example our cab file is called poc.tmp but we can call it whatever we like. Windows comes with the makecab.exe tool so we can even create our cab file
makecab c:\users\user1\desktop\CRYPTBASE.dll c:\users\user1\desktop\poc.tmp


In Cernunnos, tasks and phrases use Request Attributes as a common
means of collaborating with one another. Request attributes are a collection of
contextual information organized as a Map
: attribute values may be
any type of Object
, but keys are always String
s.
You can create request attributes in several ways; perhaps the most common
(and most broadly applicable) method is the
<with-attribute>
task. This task registers any Object
(specified by the
VALUE
reagent) under any name (specified by the KEY
).
The resulting name/value pair will be visible to all subtasks: this is the role
and the entire purpose of the <with-attribute>
task.
Conversely, some tasks that set request attributes have other duties. The
<sql-connection>
task is a great example. <sql-connection>
is responsible
for opening a JDBC connection to an SQL data source. This connection is then
made available to subtasks of <sql-connection>
, which use it
to execute SQL statements. Once all subtasks have completed,
<sql-connection>
closes the SQL connection in accordance with
JDBC best practices.
You can optionally designate the name of the request attribute that will
contain the SQL connection through the ATTRIBUTE_NAME
reagent. If
you don't specify a name, a default name will be used (more on this topic
below). Tasks that open or establish resources for the benefit of subtasks
commonly support the ATTRIBUTE_NAME
reagent. These include
<invoke-method>
,
<node-iterator>
, and
<print-stream>
.
The usual way to access the value of a request attribute is through the
${req()}
phrase. Just put the name
of the desired request attribute between the parentheses, like so:
${req(Attributes.LOCATION)}
Just like tasks, phrases use reagents to accept inputs; the expression
'Attributes.LOCATION
' above is associated with the KEY
reagent of ${req()}
. Unlike tasks, phrases typically have only
one reagent.
Accessing request attributes is very common in Cernunnos. The
${req()}
phrase, therefore, is the default phrase
implementation. Since it's the default, you don't have to specify it
explicitly to use it.
The expression:
${req(Attributes.LOCATION)}
is usually abbreviated as:
${Attributes.LOCATION}
Request attributes exhibit some characteristics that may catch unwary programmers off guard; don't worry, they will make complete sense one you get used to them (we hope). Be aware of the following considerations when dealing with request attributes.
Request attributes have a lifecycle: they exist only within the scope of the task that creates them. In other words, they are visible to descendants, but not to ancestors or siblings.
Request attributes may also cover other request attributes. This process occurs whenever a task registers an attribute with the same name as an existing attribute. In this case, the new attribute will be visible within the scope of the task that (re)registered it; the covered attribute will be inaccessible.
Many tasks and phrases provide default values for some or all of their reagents through standard, well-known request attributes. Consider this example:
Who told <sql-connection>
how to connect to the database?
Who told <sql-statement>
or ${sql()}
what JDBC
connection to use?
No one did -- at least, not explicitly. This information is communicated
through a system of conventional request attributes. Since
<sql-connection>
, <sql-statement>
, and
${sql()}
each agree on the convention, you can leave these mundane
details out of your scripts in 99% of cases. For the remaining 1% of cases, you
have the opportunity to specify a DataSource
or
Connection
object explicitly.
Request attributes that serve as default values for reagents are given names according to a convention: first a name like "Attributes" or "SqlAttributes" (roughly corresponding to Java package names), followed by a period '.' character, followed by a noun in uppercase (multi-word nouns are separated by underscore '_' characters). For example:
Attributes.CONTEXT
Attributes.LOCATION
SqlAttributes.DATA_SOURCE
XmlAttributes.ENTITY_RESOLVER
Ad-hoc request attributes need not -- and should not -- adhere
to this convention. User-defined request attributes that contain special
characters may not play well with some Task
or Phrase
implementations. Use camel-case names for request attributes, like Java
variables (e.g. 'myFile' or 'theXslTemplateLocation').
Depending on how you use Cernunnos, one or more request attributes may be present in the collection even before the first task is invoked.
Attributes.ORIGIN
The value of this attribute is a URL (in String
form)
representing the absolute location of the current script. It set by the
Cernunnos runtime whenever a Task
object is created from a file --
whether read over HTTP, over FTP, from the classpath, from the local file
system, etc.
Attributes.ORIGIN
is tremendously useful because it allows you
to reference additional resources -- XSLT stylesheets, properties files, other
Cernunnos scripts, etc. -- using relative path expressions. Thanks to
this attribute, you don't have to know where resources will be when they are
ultimately deployed; you only have to know where they are relative to the
script that uses them. Pass Attributes.ORIGIN
to the
CONTEXT
reagent of a task that uses an external resource; it will
then evaluate the LOCATION
of that resource relative to the current
script.
There are, moreover, several tasks that use Attributes.ORIGIN
as
the default value for their CONTEXT
reagent. Some examples are
<properties>
and
<crn>
. These tasks will
evaluate LOCATION
relative to the current script if
CONTEXT
is omitted.
When you invoke Cernunnos from the command line, you may optionally specify request attributes as command line parameters. Take a look at this example:
> crn good-advice.crn many hands make light work
INFO [main] runtime.ScriptRunner.[] Nov/28 21:00:14 -
**************************************************
** Invoking ScriptRunner.run(Task, TaskRequest)
** TaskRequest contains 6 elements
** - $3=make
** - $1=many
** - Attributes.ORIGIN=file:/C:/HOME/danann/cernunnos/good-advice.crn
** - $5=work
** - $2=hands
** - $4=light
**************************************************
The first parameter is always the location of the script (can be relative,
absolute, or a URL). Subsequent parameters are added to the collection of
request attributes as $1
, $2
, and so on.
Cernunnos has been used to develop several Java Portlets. For detailed instructions on how to create portlets with Cernunnos, refer to this article.
The Cernunnos portlet class
(org.danann.cernunnos.runtime.web.CernunnosPortlet
) can pre-load
the request with useful attributes whenever it invokes a script. For starters,
it creates request attributes for the two objects provided by the portlet
container in each action or render cycle:
WebAttributes.REQUEST
WebAttributes.RESPONSE
These will be set to instances of
ActionRequest
/ActionResponse
or
RenderRequest
/RenderResponse
in the
processAction
and render
methods, respectively.
In addition, you may optionally define a collection of request attributes for
your portlet using spring
dependency injection. These attributes my be of any type, and will be
accessible to all scripts in both processAction
and
render
.


{% extends 'userena/base_userena.html' %} {% load i18n %} {% block title %}{% trans "Email verification" %}{% endblock %} {% block content_title %}
{% blocktrans with viewed_user.userena_signup.email_unconfirmed as email %}You have received an email at {{ email }}.{% endblocktrans %}
{% blocktrans with viewed_user.username as username %}To associate this email address with your account ( {{ username }}) click on the link provided in this email.{% endblocktrans %}
{% endblock %}


{@boolean renderSection1=true} {#include Common/insightsEmailBody} {#content-title} Compliance - Red Hat Enterprise Linux {/content-title} {#content-title-section1} Compliance below threshold {/content-title-section1} {#content-body-section1}
Your system, {action.events[0].payload.host_name}, assigned to policy {action.events[0].payload.policy_name}, has been marked as non-compliant because its compliance score {action.events[0].payload.compliance_score}% dropped below the configured compliance threshold of {action.events[0].payload.policy_threshold}% for this policy.
Please review the detailed policy report for this system and take the appropriate steps to bring this system into compliance. For additional details on how to remediate compliance issues, learn more here.
{/content-body-section1} {/include}


| About Dailyrotten |
|
Feedback
If you like this page, hate it, or would like to suggest changes,
<EMAIL_ADDRESS>is listening. This page
is experimental and somewhat different from what we usually offer, so please
do send your feedback.
Adding Stories
If you are a rotten newshound and you would like to suggest a story,
visit our submit page to
send us the URL. Stories that are accepted will have your name credited.
Posting Comments
In order to post comments to stories, you will have to
create an account.
Accounts will generally be validated within 24 hours, and of
course will be disabled if there is abuse.
Viewership
On the first full day this page went live, 100,000 people visited this Rotten
News page. Of course that was the day after the WTC attacks, so that number is
somewhat distorted. Right now this page gets between 50,000 and 75,000 people
every day.
Linking
We encourage everyone to link to this page; if you like it, others probably
will as well.
Other Rotten
Rotten
Gaping Maw
Celebrity Morgue
Mugshots
Rotten Store
Rate My Poo
Rate My Kitten
Penny Postcards
Phallic
Boners
Home
Make Dailyrotten your start page
|
|
|
October 16, 2001
Morgue Photo Caper
Associated Press | Submitted by: LadyC
Deliberations began yesterday in the trial of two Cincinnati men
accused of 12 counts of "gross abuse of a corpse". The two men took
suggestive and silly pictures in the morgue, but the access was
granted with permission.
"Bender cited examples of the photographs in which the hands of a 2-year-old
were wrapped with plastic, a man's body was posed with an apple with a bite
taken out of it, and a body bag was unzipped to expose a woman's breasts."
|
|
Read article...
|
|
Nasty Western Food Drops
Times | Submitted by: Soylent
Are Afghanis really appreciating our food drops? --
"Not good taste", said one teenager, who sat on a pile of food packages,
ripping open each tinfoil packet and testing the ready-to-eat meals. As he
opened each one, he stared at it as though it were an object from Mars,
tasted it, then tossed it aside.
|
|
Read article...
|
|
Coworkers Spraypainted My Genitals!
Houston Chronicle | Submitted by: Soylent
Hazing has apparently been a problem at the George M. Construction Company
for years. An employee filed state and civil suits after "co-workers allegedly
lashed him to a utility pole and spray-painted his genitals." And when the
company thought he might sue, they warned him that he might be blacklisted.
|
|
Read article...
|
|
Hawking Urges Space Colonization
London Telegraph | Submitted by: Soylent
Stephen Hawking, the best crippled cosmologist the world has ever
produced, urges that colonization of space is the only way to guarantee
survival of humanity. Biotechnology, genetic engineering, atomics, and
nanotechnology all pose potential threats as well as unimaginable rewards.
He is quite correct in stating the imperative that parts of humanity
must leave this planet if we want a bright future.
|
|
Read article...
|
|
How We Got Fooled
Asia Times | Submitted by: Soylent
American isolationism and navel gazing is largely responsible for Americans
being unaware that people out there hate us. Even our top networks would hardly
report on international events, instead focusing on mundane trivia such as
Gary Condit, O.J. Simpson or Tonya Harding. This is a great article by the
former CEO of United Press International.
|
|
Read article...
|
|
|
|
|