Login or Register to Ask a Question and Join Our Community


UNIX and Linux RSS News

Novell Files Motion for Judgment and Motion to Strike

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Novell Files Motion for Judgment and Motion to Strike
# 1  
Old 03-25-2010
Novell Files Motion for Judgment and Motion to Strike
Novell has filed two motions today, one for a judgment on SCO's slander of title claim -- the promised Rule 50(a) motion -- and one to strike testimony inconsistent with the unambiguous contract language.
Novell points out that the only evidence SCO presented regarding malice is testimony by Maureen O'Gara of a conversation with Chris Stone, and no one corroborates her story, first of all, and second, O'Gara admitted she can't recall exactly what was said in the conversation with Chris Stone. She merely surmised things. And that's not clear and convincing evidence. No reasonable jury could find personal malice in the picture, so Novell says as a matter of law, judgment should be granted as a matter of law on SCO's claim for punitive damages.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT MOJAVE

file::find::rule::extending

File::Find::Rule::Extending(3)				User Contributed Perl Documentation			    File::Find::Rule::Extending(3)

NAME

       File::Find::Rule::Extending - the mini-guide to extending File::Find::Rule

SYNOPSIS

	package File::Find::Rule::Random;
	use strict;

	# take useful things from File::Find::Rule
	use base 'File::Find::Rule';

	# and force our crack into the main namespace
	sub File::Find::Rule::random () {
	    my $self = shift()->_force_object;
	    $self->exec( sub { rand > 0.5 } );
	}

	1;

DESCRIPTION

       File::Find::Rule went down so well with the buying public that everyone wanted to add extra features.  With the 0.07 release this became a
       possibility, using the following conventions.

   Declare your package
	package File::Find::Rule::Random;
	use strict;

   Inherit methods from File::Find::Rule
	# take useful things from File::Find::Rule
	use base 'File::Find::Rule';

       Force your madness into the main package

	# and force our crack into the main namespace
	sub File::Find::Rule::random () {
	    my $self = shift()->_force_object;
	    $self->exec( sub { rand > 0.5 } );
	}

       Yes, we're being very cavalier here and defining things into the main File::Find::Rule namespace.  This is due to lack of imaginiation on
       my part - I simply can't find a way for the functional and oo interface to work without doing this or some kind of inheritance, and
       inheritance stops you using two File::Find::Rule::Foo modules together.

       For this reason try and pick distinct names for your extensions.  If this becomes a problem then I may institute a semi-official registry
       of taken names.

   Taking no arguments.
       Note the null prototype on random.  This is a cheat for the procedural interface to know that your sub takes no arguments, and so allows
       this to happen:

	find( random => in => '.' );

       If you hadn't declared "random" with a null prototype it would have consumed "in" as a parameter to it, then got all confused as it doesn't
       know about a '.' rule.

AUTHOR

       Richard Clamp <richardc@unixbeard.net>

COPYRIGHT

       Copyright (C) 2002 Richard Clamp.  All Rights Reserved.

       This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

SEE ALSO

       File::Find::Rule

       File::Find::Rule::MMagic was the first extension module, so maybe check that out.

perl v5.18.2							    2011-09-19					    File::Find::Rule::Extending(3)