We sell users!
- transform proactive supply-chains
- incentivize robust systems
- mesh efficient interfaces
- reintermediate transparent platforms
- morph turn-key action-items
- grow value-added schemas
- whiteboard wireless bandwidth
- implement frictionless paradigms
- whiteboard dynamic models


The route {{ route.url }} was not found. Click here to go back to the information page
{{ route.url }}


Home >
Microsoft XML Notepad is now an open source project. You can find more information at https://github.com/Microsoft/XmlNotepad.
Home >
Microsoft XML Notepad is now an open source project. You can find more information at https://github.com/Microsoft/XmlNotepad.


Developed application as a final project for Information Organization Lab in a team of three with Nico Soldi and Ganesh Viswanathan. Full report
If you experience an uncertainty about the food you are about to order at a restaurant, specifically if it could contain a serious food allergen, then you are one among approximately 15 million Americans affected by food allergy. KoÁlacarte is a Service that allows user to identify dishes that are safe to eat in a restaurant keeping in mind dietary restrictions and preferences.
The first step in the process was collecting a database of menus. Next step was to match dietary preference of users at ingredient level to menu item. This was done by collecting recipes for all the items in the menu. Multiple recipes were collected for single dish as different recipes differed slightly in the ingredients they use. This approach was used to be give user a probability score of an ingredient occurring in a menu item.
My role in this project was limited to application development. We decided that the use case of the app is mostly in a restaurant setting so the app must be available on the go. Therefore we decided to implement the app as a mobile app rather than a desktop app.
We build the app using Ionic framework. We made the choice as Ionic can be used to make hybrid mobile apps easily. Code for Iocnic is written in HTML5, CSS and AnglarJS, Ionic creates native code for Android and iOS using the underlying Cordova API. It Works like a single page application with one index.html and different templates plugin as needed. JS part divided into route, controller, services, directives and app, like a typical application in angular.
We built a database model to include two main entities, the user and the restaurant. The user could store the ingredient that they have to restrict in their diet in the database through the onboarding process. The restaurant has a menu, each menu has a list of dishes and dishes had a list of ingredients in them.
The application uses hybrid database to manage information and an API layer to delegate information retrieval and storage in the database. The primary ingredient database was created as a Mongo Database and was connected to the application via mLab API. We also decided to use Firebase to store user authentication information. Firebase is optimized for maintaining user information such as user id, user name, email and password.


{% extends 'cotton.html' %} {% block header_css %} {{ super() }} {% endblock %} {% block hero %}
A basic platform for your simple canvas ideas.
Duck components are a library of tools to help drawing on the canvas.
To get started, we need to use a bit of cotton to wait for a ready canvas
var line = function(){};
var ready = function(){
var canvas = new cotton.duck.objects.Surface('main');
canvas.load(['NullPoint'], function(o){
NullPoint = o.NullPoint;
canvas.load(['Line'], line);
});
cotton.ready(ready)
In this example, we wait for a ready event and call the 'line' function.
If your using the live loader, you call the Duck element's you'd like to use prior to usage.
Pass an array and handler to the load() method
var line = function(){};
canvas.load(['NullPoint','Line'], function(){});
The API is super simple All components follow the following structure
data = {};
points = [
new NullPoint(10, 10),
new NullPoint(10, 100)
];
new Line(points, data);
{% endblock %}
{% block footer_js %}
{{ super() }}
{% endblock %}


Audio File Management
Existing Audio Files
Upload Audio Files
Delete
Refresh
AUDIO FILE
Upload Audio File


Archive for posts tagged with 'Google'
-
My WordPress hacked by c99madshell script
After all the excitement of last Friday’s attempted hack on my travelblog, and the subsequent upgrade to WordPress 2.6 – I thought everything was under control. Boy was I wrong! A few hours ago I received a blog comment (from a Mr Andrew Wong) on the travelblog: http://www.lee-and-lucy.com/travelblog/index.php?p=5817 check this out!! I clicked the link, my jaw dropped! It wasn’t an attempted hack, it was a very successful hack… I felt violated -in a digital…
-
How to follow conversations on Twitter
After reading Dave’s post about Twitter being the new Facebook yesterday, I decided to give Digsby a go. (I’d heard of it previously, but I was semi-scared off by all the twittermania – it’s a bit like marmite). Since I was only following a few tweeters there wasn’t of a flow – so I added a couple more higher profile tweeters, like Jeff Atwood’s Coding Horror.
-
“Powered by Category Cloud”
I’ve just installed Operator – a Firefox extension that highlights microformatted data on web pages. So far I haven’t noticed any performance issues, and it’s been playing nicely with all my other Firefox extensions. As a web developer, Operator makes me want to add more semantic mark-up to my websites, (which I already try to do). This extension will make it easier for testing purposes. I decided to read more about the extension on the…
-
All hail “The Bookninja Messiah”!
Earlier this week I’d heard that Bookninja had been hijacked, they needed some help to get their WordPress back in working order. Mark suggested that I offered my services, so I did. George explained what the problems since the hijack: Unable to publish blog posts and pages; (a blank page appeared when he tried to publish) All the pages had been delete, or disappeared. Akismet was turned off… opening the floodgates to lots of unwanted…
-
WordPress: “post.php” is blank after publishing
Whilst I was helping out Bookninja earlier this week, I came across a strange problem in WordPress. Every time we tried to publish a new blog post (or page), there would be a pause, then the page would go blank. (This was on the “post.php” page) I spent a long time trying to figure out what the issue was… even longer googling it! Several pages into the Google results, I found the answer! Thank you…
-
Mozilla Prism – Bringing Web Apps to the Desktop
I feel like I’ve been living under a rock for the last couple of months. I’ve only just heard about Mozilla’s Prism – and it’s already changing the way I use web-apps. Prism, (previously called WebRunner), is essentially a Site Specific Browser (SSB) – meaning that it’s a desktop application designed to host a single web-application. This is good for many reasons, foremost it causes less distractions. So far, I have prisms set-up for most…
-
Google Maps Street View
Google have added a new feature on their maps… Panoramic street views! Check this one from the Golden Gate Bridge – could it be a tourist asking for directions? or maybe it’s a secret spy meeting? [via Dave]
-
Google TiSP: Free wireless broadband
Want free in-home wireless broadband from Google? Check out TiSP!
-
Yahoo and MSN will use Google’s Sitemap Protocol
Yahoo and MSN are uniting with Google to provide support for the Sitemap Protocol! (more info here – sitemaps.org)
-
Google Reader
It has taken me a long time to actually get around to using RSS feeds properly – I’ve known about them (and developed them for other sites) for several years – but I never could get into the habit of opening a feed-reader everyday… well, the other day I thought I’d give Google’s Reader another go (I wasn’t impressed previously) – it’s only been 3 days and I’m hooked! When I eventually get around to…
-
Another Me?
Will the real Lee Kelleher please stand up? I was doing some ego-surfing on Google…. and found another me! I wish he’d learn how to spell! :roll:


Dan Chambers sent me this snap of a sampler, taken in the Bethnal Green Museum of Childhood. The provenance card states that it was made by a girl named Enid, aged fourteen, so, as Dan says, “maybe not so tiny”. But it may well be that the Museum has not done its research thoroughly, and that the sampler was made by an anonymous needleworker for Tiny Enid. What with the privations of the times (1933) there may have been a dearth of thread, not enough, at any rate, to sew both TINY and ENID.


spikedev.tank¶
-
class
spikedev.tank.
MoveTank
(left_motor_port, right_motor_port, motor_class=<class 'spikedev.motor.SpikeMediumMotor'>, left_motor_polarity=1, right_motor_polarity=0, desc=None)¶ Bases:
object
A class for supporting tank style robots that are driven by two motors
- Parameters
left_motor_port (str) – port letter of the left motor
right_motor_port (str) – port letter of the right motor
motor_class (Motor) – the type of motor that is used, defaults to
SpikeMediumMotor
left_motor_polarity (MotorPolarity) – the polarity for the left motor, defaults to
MotorPolarity.REVERSED
right_motor_polarity (MotorPolarity) – the polarity for the right motor, defaults to
MotorPolarity.NORMAL
desc (str) – defaults to None
Example:
import hub from spikedev.motor import MotorSpeedDPS from spikedev.tank import MoveTank tank = MoveTank(hub.port.E, hub.port.F) tank.run_for_time(3000, MotorSpeedDPS(180), MotorSpeedDPS(360))
-
stop
()¶ Stop both motors
-
run_at_speed
(left_speed, right_speed, **kwargs)¶ Run the motors at the specified speeds. The motors will run until you call
stop()
- Parameters
left_speed (MotorSpeed) – the speed of the left motor
right_speed (MotorSpeed) – the speed of the right motor
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
-
run_for_degrees
(degrees, left_speed, right_speed, stop=1, block=True, **kwargs)¶ Run the motors at the specified speeds, the two motors combined will move an average of
degrees
- Parameters
degrees (int) – the average number of degrees for the two motors to move
left_speed (MotorSpeed) – the speed of the left motor
right_speed (MotorSpeed) – the speed of the right motor
stop (MotorStop) – how to stop the motors, defaults to
MotorStop.BRAKE
block (bool) – if True this function will not return until the motors have finished moving
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
-
run_to_position
(left_position, right_position, speed, stop=1, block=True, **kwargs)¶ Run both motors at
speed
to the desired positions- Parameters
left_position (int) – the target position for the left motor
right_position (int) – the target position for the right motor
speed (MotorSpeed) – the speed of both motors
stop (MotorStop) – how to stop the motors, defaults to
MotorStop.BRAKE
block (bool) – if True this function will not return until the motors have finished moving
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
-
run_for_time
(msec, left_speed, right_speed, stop=1, block=True, **kwargs)¶ Run the motors at the specified speeds for
msec
- Parameters
msec (int) – the number of milliseconds to run the motors
left_speed (MotorSpeed) – the speed of the left motor
right_speed (MotorSpeed) – the speed of the right motor
stop (MotorStop) – how to stop the motors, defaults to
MotorStop.BRAKE
block (bool) – if True this function will not return until the motors have finished moving
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
-
class
spikedev.tank.
MoveSteering
(left_motor_port, right_motor_port, motor_class=<class 'spikedev.motor.SpikeMediumMotor'>, left_motor_polarity=1, right_motor_polarity=0, desc=None)¶ Bases:
spikedev.tank.MoveTank
MoveSteering is a child of
MoveTank
that adds the ability to control the tank via asteering
value and aspeed
value.Example:
import hub from spikedev.motor import MotorSpeedDPS from spikedev.tank import MoveSteering ms = MoveSteering(hub.port.E, hub.port.F) # Move forward and to the right for 500 degrees ms.run_for_degrees(500, 60, MotorSpeedDPS(180))
-
run_at_speed
(steering, speed, **kwargs)¶ Run the motors according to the provided
steering
atspeed
The motors will run until you callstop()
steering
details:-100 means turn left on the spot (right motor at 100% forward, left motor at 100% backward),
0 means drive in a straight line, and
100 means turn right on the spot (left motor at 100% forward, right motor at 100% backward).
- Parameters
steering (int) – a number from -100 to 100
speed (SpeedValue) – The speed that should be applied to the outmost motor (the one rotating faster). The speed of the other motor will be computed automatically.
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
-
run_for_degrees
(steering, speed, degrees, stop=1, block=True, **kwargs)¶ Rotate the motors according to the provided
steering
atspeed
where the outmost motor (the one rotating faster) will move fordegrees
.steering
details:-100 means turn left on the spot (right motor at 100% forward, left motor at 100% backward),
0 means drive in a straight line, and
100 means turn right on the spot (left motor at 100% forward, right motor at 100% backward).
- Parameters
steering (int) – a number from -100 to 100
speed (SpeedValue) – The speed that should be applied to the outmost motor (the one rotating faster). The speed of the other motor will be computed automatically.
degrees (int) – the number of degrees for the outmost motor (the one rotating faster) to move
stop (MotorStop) – how to stop the motors, defaults to
MotorStop.BRAKE
block (bool) – if True this function will not return until the motors have finished moving
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
-
run_for_time
(msec, steering, speed, stop=1, block=True, **kwargs)¶ Rotate the motors according to the provided
steering
forseconds
.steering
details:-100 means turn left on the spot (right motor at 100% forward, left motor at 100% backward),
0 means drive in a straight line, and
100 means turn right on the spot (left motor at 100% forward, right motor at 100% backward).
- Parameters
msec (int) – the number of milliseconds to run the motors
steering (int) – a number from -100 to 100
speed (SpeedValue) – The speed that should be applied to the outmost motor (the one rotating faster). The speed of the other motor will be computed automatically.
stop (MotorStop) – how to stop the motors, defaults to
MotorStop.BRAKE
block (bool) – if True this function will not return until the motors have finished moving
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
-
-
class
spikedev.tank.
MoveDifferential
(left_motor_port, right_motor_port, wheel_class, wheel_distance, motor_class=<class 'spikedev.motor.SpikeMediumMotor'>, left_motor_polarity=1, right_motor_polarity=0)¶ Bases:
spikedev.tank.MoveTank
- MoveDifferential is a child of
MoveTank
that adds the following capabilities: drive in a straight line for a specified distance
rotate in place in a circle (clockwise or counter clockwise) for a specified number of degrees
drive in an arc (clockwise or counter clockwise) of a specified radius for a specified distance
All of the args from MoveTank apply plus two additional args:
- Parameters
wheel_class (Wheel) – used to get the circumference of the wheels of the robot. The circumference is needed for several calculations in this class.
wheel_distance_mm (DistanceValue) – The distance between the mid point of the two wheels of the robot. You may need to do some test drives to find the correct value for your robot. It is not as simple as measuring the distance between the midpoints of the two wheels. The weight of the robot, center of gravity, etc come into play.
Example:
import hub from spikedev.motor import MotorSpeedDPS from spikedev.tank import MoveDifferential from spikedev.unit import DistanceInches, DistanceStuds from spikedev.wheel import SpikeWheel md = MoveDifferential(hub.port.E, hub.port.F, SpikeWheel, DistanceStuds(11)) # rotate 90 degrees clockwise md.turn_right(90, MotorSpeedDPS(100)) # rotate 90 degrees counter-clockwise md.turn_left(90, MotorSpeedDPS(100)) # drive forward 6 inches md.run_for_distance(DistanceInches(6), MotorSpeedDPS(100)) # Drive in arc to the right along an imaginary circle of radius 12 inches. # Drive for 6 inches around this imaginary circle. md.run_arc_right(DistanceInches(12), DistanceInches(6), MotorSpeedDPS(100))
-
run_for_distance
(distance, speed, stop=1, block=True, **kwargs)¶ Drive in a straight line for
distance
- Parameters
distance (DistanceValue) – how far the midpoint between the wheels should travel
speed (MotorSpeed) – how fast the midpoint between the wheels should travel
stop (MotorStop) – how to stop the motors, defaults to
MotorStop.BRAKE
block (bool) – if True this function will not return until the motors have finished moving
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
-
run_arc_right
(radius, distance, speed, stop=1, block=True, **kwargs)¶ Drive clockwise in a circle with
radius
fordistance
- Parameters
radius (DistanceValue) – the radius of the arc to drive in, think of this as the size of the imaginary circle the robot will follow
distance (DistanceValue) – how far the midpoint between the wheels should travel along the imaginary circle
speed (MotorSpeed) – how fast the midpoint between the wheels should travel
stop (MotorStop) – how to stop the motors, defaults to
MotorStop.BRAKE
block (bool) – if True this function will not return until the motors have finished moving
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
-
run_arc_left
(radius, distance, speed, stop=1, block=True, **kwargs)¶ Drive counter-clockwise in a circle with
radius
fordistance
- Parameters
radius (DistanceValue) – the radius of the arc to drive in, think of this as the size of the imaginary circle the robot will follow
distance (DistanceValue) – how far the midpoint between the wheels should travel along the imaginary circle
speed (MotorSpeed) – how fast the midpoint between the wheels should travel
stop (MotorStop) – how to stop the motors, defaults to
MotorStop.BRAKE
block (bool) – if True this function will not return until the motors have finished moving
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
-
turn_degrees
(degrees, speed, stop=1, block=True, **kwargs)¶ Rotate in place
degrees
. Both wheels will turn at the same speed for us to rotate in place.- Parameters
degrees (int) – the number of degrees to rotate in place
speed (MotorSpeed) – how fast each wheel should move
stop (MotorStop) – how to stop the motors, defaults to
MotorStop.BRAKE
block (bool) – if True this function will not return until the motors have finished moving
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
-
turn_right
(degrees, speed, stop=1, block=True, **kwargs)¶ Rotate clockwise
degrees
in place- Parameters
degrees (int) – the number of degrees to rotate clockwise in place
speed (MotorSpeed) – how fast each wheel should move
stop (MotorStop) – how to stop the motors, defaults to
MotorStop.BRAKE
block (bool) – if True this function will not return until the motors have finished moving
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
-
turn_left
(degrees, speed, stop=1, block=True, **kwargs)¶ Rotate counter-clockwise
degrees
in place- Parameters
degrees (int) – the number of degrees to rotate counter-clockwise in place
speed (MotorSpeed) – how fast each wheel should move
stop (MotorStop) – how to stop the motors, defaults to
MotorStop.BRAKE
block (bool) – if True this function will not return until the motors have finished moving
**kwargs – optional kwargs that will pass all the way down to the LEGO
hub.port.X.motor
API call
- MoveDifferential is a child of


| info_currencies {gt} | R Documentation |
The fmt_currency()
function lets us format numeric values as currencies.
The table generated by the info_currencies()
function provides a quick
reference to all the available currencies. The currency identifiers are
provided (name, 3-letter currency code, and 3-digit currency code) along with
the each currency's exponent value (number of digits of the currency
subunits). A formatted example is provided (based on the value of 49.95
) to
demonstrate the default formatting of each currency.
info_currencies(type = c("code", "symbol"), begins_with = NULL)
type |
The type of currency information provided. Can either be |
begins_with |
Providing a single letter will filter currencies to only
those that begin with that letter in their currency code. The default
( |
There are 172 currencies, which can lead to a verbose display table. To make
this presentation more focused on retrieval, we can provide an initial letter
corresponding to the 3-letter currency code to begins_with
. This will
filter currencies in the info table to just the set beginning with the
supplied letter.
An object of class gt_tbl
.
10-3
Other Information Functions:
info_date_style()
,
info_google_fonts()
,
info_locales()
,
info_paletteer()
,
info_time_style()
# Get a table of info on all of # the currencies where the three- # letter code begins with a "h" tab_1 <- info_currencies(begins_with = "h") # Get a table of info on all of the # common currency name/symbols that # can be used with `fmt_currency()` tab_2 <- info_currencies(type = "symbol")


Get Notified about vaccine availability in your location on email & sms ✉! Vaccinator Octocat tracks & sends personalised vaccine info everday.


Blockchain is essentially a data structure that makes it possible to create a digital ledger of data and share it among a network of independent parties. Securing this database with cryptography and by using a decentralized, anonymous, transparent and append-only value-exchange protocol, Blockchain Technology is changing the world in terms of political and financial institutions, business models and revolutionizing the ways we produce, trade and exchange.
Applications of Blockchain Technology varies from Finance, Energy, Health, Logistics, Education, Supply chains, Law, Farming, Insurance to Politics, Sociology, Economics and Governance. BlockchainIST Center helps ideas grow and scale up to viable new business. We offer a state-of-the-art environment for executive teams to explore the latest thinking, industry research and cutting-edge technology—and put that knowledge into action immediately.
As a unique feature of BlockchainIST Center, in cooperation with BAU Experimental Economics Lab, we test what we design in a laboratory environment with real users. Experimental Economics, Behavioral Finance and Game Theory literature emphasize that for any mechanism design approach, incentives of individuals matter the most. Moreover, individuals are "Boundedly Rational". Any mechanism not taking cognitive biases of individuals into consideration would not work in implementation as expected.
Lead Designer
Lead Marketer
Lead Developer
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Aut eaque, laboriosam veritatis, quos non quis ad perspiciatis, totam corporis ea, alias ut unde.
Lead Designer
Lead Marketer
Lead Developer
Lead Designer
Lead Marketer
Lead Developer
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Aut eaque, laboriosam veritatis, quos non quis ad perspiciatis, totam corporis ea, alias ut unde.
Lead Designer
Lead Marketer
Lead Developer
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Aut eaque, laboriosam veritatis, quos non quis ad perspiciatis, totam corporis ea, alias ut unde.
Lead Designer
Lead Marketer
Lead Developer
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Aut eaque, laboriosam veritatis, quos non quis ad perspiciatis, totam corporis ea, alias ut unde.
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Sunt ut voluptatum eius sapiente, totam reiciendis temporibus qui quibusdam, recusandae sit vero unde, sed, incidunt et ea quo dolore laudantium consectetur!
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Sunt ut voluptatum eius sapiente, totam reiciendis temporibus qui quibusdam, recusandae sit vero unde, sed, incidunt et ea quo dolore laudantium consectetur!
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Sunt ut voluptatum eius sapiente, totam reiciendis temporibus qui quibusdam, recusandae sit vero unde, sed, incidunt et ea quo dolore laudantium consectetur!
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Sunt ut voluptatum eius sapiente, totam reiciendis temporibus qui quibusdam, recusandae sit vero unde, sed, incidunt et ea quo dolore laudantium consectetur!
Research Projects of the BlockchainIST Center
BAU Incubation Center
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Minima maxime quam architecto quo inventore harum ex magni, dicta impedit.


Eat-Da-Burger!
Chicken Burger
Devour it!
Beef Burger
Devour it!
Fish Burger
Devour it!
Chicken Burger
Beef Burger
Fish burger
Submit


Ruby classes vs. JavaScript constructor functions
Date: Feb 05, 2015
Classes are very important in object-oriented programming. This is because a class tells us helpful information about objects, and you can think of an object as a particular instance of a class.
There are several difference between Ruby classes and JavaScript Constructor functions. First, Ruby class is can be instanciate by Class.new attribute but JavaScript needs a special function called 'prototype'.
Here is an example of Ruby's class and instantiate process.
class Person
def initialize(name, phone_number, address)
@name = name
@phone_number = phone_number
@address = address
end
def print_out
puts "#{@name}, #{@phone_number}, #{@address}"
end
end
sarah = Person.new("Sarah Kwak", "650-3810-9918", "140 Belvedere Ave. San Carlos, CA 94070")
sarah.print_out
=>
Sarah Kwak, 650-3810-9918, 140 Belvedere Ave. San Carlos, CA 94070
JavScript has 'object constructor' does do similar job but have little bit different way. Here is an example.
Person = function(name, phone_number, address) {
this.name = name,
this.phone_number = phone_number,
this.address = address
};
sarah = new Person("Sarah Kwak", "650-381-9918", "140 Belvedere Ave. San Carlos,
CA 94070");
console.log(sarah);
=>
{ name: 'Sarah Kwak',
phone_number: '650-381-9918',
address: '140 Belvedere Ave. San Carlos, CA 94070' }
The thing is that not everything can be easily inherited to the class instance. The special keyword 'prototype' allows any function to be inherited to the class instance.
Dog = function(name, breed, age) {
this.name = name,
this.breed = breed,
this.age = age
};
Dog.prototype.complain = function () {
console.log("My name is "+this.name +" and I need COOKIES!");
};
brian = new Dog("Brian", "puggle", 3);
brian.complain();
=>
My name is Brian and I need COOKIES!
"Inheritance Chain" means if a property is not defined for a class, this class's prototype chain will be traversed upwards until one is found (or not) in a parent (higher) class.
Animal = function(kind) {
this.kind = kind,
this.numLegs = 4
};
Animal.prototype.peace = function() {
console.log("We all love peace!");
};
Dog = function(name, breed, age) {
this.name = name,
this.breed = breed,
this.age = age
};
Dog.prototype = new Animal(); // This will make Brian = Dog = Animal
brian = new Dog("Brian", "puggle", 3);
console.log(brian.numLegs);
brian.peace();
=>
4
We all love peace!
Classes are very important in object-oriented programming. This is because a class tells us helpful information about objects, and you can think of an object as a particular instance of a class.
There are several difference between Ruby classes and JavaScript Constructor functions. First, Ruby class is can be instanciate by Class.new attribute but JavaScript needs a special function called 'prototype'.
Here is an example of Ruby's class and instantiate process.
JavScript has 'object constructor' does do similar job but have little bit different way. Here is an example.
The thing is that not everything can be easily inherited to the class instance. The special keyword 'prototype' allows any function to be inherited to the class instance.
"Inheritance Chain" means if a property is not defined for a class, this class's prototype chain will be traversed upwards until one is found (or not) in a parent (higher) class.


theme file path view helpers for ejs
- Source:
Methods
-
<static> extensionPublicResourcePath(ext, resource) → {string}
-
helper function to get file paths for extension resources
Parameters:
Name Type Description ext
object name of periodic extension
resource
object file path of extension resource
- Source:
Returns:
file path for extension resource
- Type
- string
-
<static> themePublicResourcePath(ext, resource) → {string}
-
helper function to get file paths for theme resources
Parameters:
Name Type Description ext
object name of periodic theme
resource
object file path of theme resource
- Source:
Returns:
file path for theme resource
- Type
- string


The Whole Nine Yards 3 and 1/2 Stars (Out of 4) Reviewed by Mac VerStandig<EMAIL_ADDRESS>http://www.moviereviews.org February 16, 2000 USA Release Date - February 18, 2000
---A copy of this review can be found at http://www.moviereviews.org/whole_nine_yards,_the.htm ---
Hollywood conservatives beware! The two best films of the new millennium aren't great dramatic narratives, heart-tugging romances or even intellectual studies. First The Big Tease, a lowbrow mockumentary cracking jokes at Scottish and homosexuals. Now The Whole Nine Yards, an uproarious date flick full of over-exaggerations.
"Oz" Oseransky (Matthew Perry) is a dentist, which, according to several sources throughout the film, makes him a likely suicide candidate. This isn't helped by the fact that his ex-partner, who also was his father-in-law, embezzled massive amounts of money before dying.
Jimmy "The Tulip" Tudesky (Bruce Willis) is a 17-times-veteran contract killer fresh out of the slammer thanks to a loose tongued plea-bargain. But Jimmy refused witness protection so he has turned to a new life in Canada for safety and good gardening soil (tomatoes grow quickly)- next door to Oz.
Janni Gogolak (Kevin Pollak) is the son of the crime-boss that Tudesky ratted out. He lives in Chicago with several hit-men, Tudesky's estranged wife (Natasha Henstridge) and a contract on Tudesky's head.
Everyone from oz's secretary to Gogolak seems to want or need someone dead for either revenge, money or necessity. Who are the double agents? Who will live? Who will die? And which one turns out to be the cop?
The Whole Nine Yards proves to be a hysterical blend of Airplane and Goodfellas. Of all the dark comedies over the past several years, none have managed to make murder as funny as it is here. Responsible for this phenomenon is undoubtedly the cast. Perry's innocent facial expressions, Willis' ability to deliver absurd lines with the utmost seriousness and Pollak's beautifully overacted gangster are certainly contributing factors. But the real treats are Michael Clarke Duncan (recently in The Green Mile) and Amanda Peet (recently in Isn't She Great) as a hit-man and secretary, respectively. Duncan, for those of you not familiar with him, is a huge African-American man who demonstrates his comedic ability with this intentionally cliched tough-guy character. Peet is an exceptionally attractive female with a knack for delivering nutty punch lines in a fashion even more impressive than Willis.
Another key factor in the film's success is its ability to handle murder in such a hysterically nonchalant manner. For every bit as ultra-disturbing and spine tingling as The Talented Mr. Ripley was, The Whole Nine Yards is boisterously entertaining. This goes to show that a grade-A comedy ensemble can make extraordinary light of what was equally serious when presented in another manner. There are actually more deaths in this film than Ripley and The Whole Nine Yards plays at a fraction of Ripley's time.
Critics will likely quip that the movie loses points at the end due to over-sappiness and a forced romance. I beg to differ. The Whole Nine Yards truly achieves its full pomp when it manages to integrate these "awe!" scenes with its uproarious comedy. The end result is something that Hollywood hasn't seen a quality version of in a long time: a Friday night date flick.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


| PERL561DELTA(1) | Perl Programmers Reference Guide | PERL561DELTA(1) |
Note that suidperl is neither built nor installed by default in any recent version of perl. Use of suidperl is highly discouraged. If you think you need it, try alternatives such as sudo first. See http://www.courtesan.com/sudo/ .
In other situations, large unsigned numbers (those above 2**31) could sometimes lose their unsignedness, causing bogus results in arithmetic operations.
Integer modulus on large unsigned integers sometimes returned incorrect values.
Perl 5.6.0 generated "not a number" warnings on certain conversions where previous versions didn't.
These problems have all been rectified.
Infinity is now recognized as a number.
Perl 5.6.0 parsed m/\x{ab}/ incorrectly, leading to spurious warnings. This has been corrected.
The RE engine found in Perl 5.6.0 accidentally pessimised certain kinds of simple pattern matches. These are now handled better.
Regular expression debug output (whether through "use re 'debug'" or via "-Dr") now looks better.
Multi-line matches like ""a\nxb\n" =~ /(?!\A)x/m" were flawed. The bug has been fixed.
Use of $& could trigger a core dump under some situations. This is now avoided.
Match variables $1 et al., weren't being unset when a pattern match was backtracking, and the anomaly showed up inside "/...(?{ ... }).../" etc. These variables are now tracked correctly.
pos() did not return the correct value within s///ge in earlier versions. This is now handled correctly.
"use warnings qw(FATAL all)" did not work as intended. This has been corrected.
Lexical warnings could leak into other scopes in some situations. This is now fixed.
warnings::enabled() now reports the state of $^W correctly if the caller isn't using lexical warnings.
"our" variables could result in bogus "Variable will not stay shared" warnings. This is now fixed.
"our" variables of the same name declared in two sibling blocks resulted in bogus warnings about "redeclaration" of the variables. The problem has been corrected.
File::Glob::glob() has been renamed to File::Glob::bsd_glob() because the name clashes with the builtin glob(). The older name is still available for compatibility, but is deprecated.
Spurious syntax errors generated in certain situations, when glob() caused File::Glob to be loaded for the first time, have been fixed.
The tainting behavior of sprintf() has been rationalized. It does not taint the result of floating point formats anymore, making the behavior consistent with that of string interpolation.
sort() is also fully reentrant, in the sense that the sort function can itself call sort(). This did not work reliably in previous releases.
Condition "0" in breakpoints is now treated correctly.
The "d" command now checks the line number.
$. is no longer corrupted by the debugger.
All debugger output now correctly goes to the socket if RemotePort is set.
substr(), join(), repeat(), reverse(), quotemeta() and string concatenation were all handling Unicode strings incorrectly in Perl 5.6.0. This has been corrected.
Support for "tr///CU" and "tr///UC" etc., have been removed since we realized the interface is broken. For similar functionality, see "pack" in perlfunc.
The Unicode Character Database has been updated to version 3.0.1 with additions made available to the public as of August 30, 2000.
The Unicode character classes \p{Blank} and \p{SpacePerl} have been added. "Blank" is like C isblank(), that is, it contains only "horizontal whitespace" (the space character is, the newline isn't), and the "SpacePerl" is the Unicode equivalent of "\s" (\p{Space} isn't, since that includes the vertical tabulator character, whereas "\s" doesn't.)
If you are experimenting with Unicode support in perl, the development versions of Perl may have more to offer. In particular, I/O layers are now available in the development track, but not in the maintenance track, primarily to do backward compatibility issues. Unicode support is also evolving rapidly on a daily basis in the development track--the maintenance track only reflects the most conservative of these changes.
The perlcc tool has been rewritten so that the user interface is much more like that of a C compiler.
The perlbc tools has been removed. Use "perlcc -B" instead.
The "-DT" command line switch outputs copious tokenizing information. See perlrun.
Arrays are now always interpolated in double-quotish strings. Previously<EMAIL_ADDRESS>used to be a fatal error at compile time, if an array @bar was not used or declared. This transitional behavior was intended to help migrate perl4 code, and is deemed to be no longer useful. See "Arrays now always interpolate into double-quoted strings".
keys(), each(), pop(), push(), shift(), splice() and unshift() can all be overridden now.
"my __PACKAGE__ $obj" now does the expected thing.
"Configure" has been enhanced in various ways:
sh /path/to/source/Configure -Dmksymlinks ... make all test install
in a directory other than the perl source directory. See INSTALL.
The following pod documents are brand new:
perlclib Internal replacements for standard C library functions perldebtut Perl debugging tutorial perlebcdic Considerations for running Perl on EBCDIC platforms perlnewmod Perl modules: preparing a new module for distribution perlrequick Perl regular expressions quick start perlretut Perl regular expressions tutorial perlutil utilities packaged with the Perl distribution
The INSTALL file has been expanded to cover various issues, such as 64-bit support.
A longer list of contributors has been added to the source distribution. See the file "AUTHORS".
Numerous other changes have been made to the included documentation and FAQs.
The following modules have been upgraded.
Perl now builds under Amdahl UTS.
Perl has also been verified to build under Amiga OS.
Support for EPOC has been much improved. See README.epoc.
Building perl with -Duseithreads or -Duse5005threads now works under HP-UX 10.20 (previously it only worked under 10.30 or later). You will need a thread library package installed. See README.hpux.
Long doubles should now work under Linux.
Mac OS Classic is now supported in the mainstream source package. See README.macos.
Support for MPE/iX has been updated. See README.mpeix.
Support for OS/2 has been improved. See "os2/Changes" and README.os2.
Dynamic loading on z/OS (formerly OS/390) has been improved. See README.os390.
Support for VMS has seen many incremental improvements, including better support for operators like backticks and system(), and better %ENV handling. See "README.vms" and perlvms.
Support for Stratus VOS has been improved. See "vos/Changes" and README.vos.
Support for Windows has been improved.
Unless specifically qualified otherwise, the remainder of this document covers changes between the 5.005 and 5.6.0 releases.
On the Windows platform, this feature is used to emulate fork() at the interpreter level. See perlfork for details about that.
This feature is still in evolution. It is eventually meant to be used to selectively clone a subroutine and data reachable from that subroutine in a separate interpreter and run the cloned subroutine in a separate thread. Since there is no shared data between the interpreters, little or no locking will be needed (unless parts of the symbol table are explicitly shared). This is obviously intended to be an easy-to-use replacement for the existing threads support.
Support for cloning interpreters and interpreter concurrency can be enabled using the -Dusethreads Configure option (see win32/Makefile for how to enable it on Windows.) The resulting perl executable will be functionally identical to one that was built with -Dmultiplicity, but the perl_clone() API call will only be available in the former.
-Dusethreads enables the cpp macro USE_ITHREADS by default, which in turn enables Perl source code changes that provide a clear separation between the op tree and the data it operates with. The former is immutable, and can therefore be shared between an interpreter and all of its clones, while the latter is considered local to each interpreter, and is therefore copied for each clone.
Note that building Perl with the -Dusemultiplicity Configure option is adequate if you wish to run multiple independent interpreters concurrently in different threads. -Dusethreads only provides the additional functionality of the perl_clone() API call and other support for running cloned interpreters concurrently.
NOTE: This is an experimental feature. Implementation details are subject to change.
This feature is expected to evolve quickly to support some form of I/O disciplines that can be used to specify the kind of input and output data (bytes or characters). Until that happens, additional modules from CPAN will be needed to complete the toolkit for dealing with Unicode.
NOTE: This should be considered an experimental feature. Implementation details are subject to change.
Strings written in this form are also useful to represent version "numbers". It is easy to compare such version "numbers" (which are really just plain strings) using any of the usual string comparison operators "eq", "ne", "lt", "gt", etc., or perform bitwise string operations on them using "|", "&", etc.
In conjunction with the new $^V magic variable (which contains the perl version as a string), such literals can be used as a readable way to check if you're running a particular version of Perl:
# this will parse in older versions of Perl also if ($^V and $^V gt v5.6.0) { # new features supported }
"require" and "use" also have some special magic to support such literals. They will be interpreted as a version rather than as a module name:
require v5.6.0; # croak if $^V lt v5.6.0 use v5.6.0; # same, but croaks at compile-time
Alternatively, the "v" may be omitted if there is more than one dot:
require 5.6.0; use 5.6.0;
Also, "sprintf" and "printf" support the Perl-specific format flag %v to print ordinals of characters in arbitrary strings:
printf "v%vd", $^V; # prints current version, such as "v5.5.650" printf "%*vX", ":", $addr; # formats IPv6 address printf "%*vb", " ", $bits; # displays bitstring
See "Scalar value constructors" in perldata for additional information.
Maintenance versions of v5.6.0 will be released as v5.6.1, v5.6.2 etc. The next development series following v5.6.0 will be numbered v5.7.x, beginning with v5.7.0, and the next major production release following v5.6.0 will be v5.8.0.
The English module now sets $PERL_VERSION to $^V (a string value) rather than $] (a numeric value). (This is a potential incompatibility. Send us a report via perlbug if you are affected by this.)
The v1.2.3 syntax is also now legal in Perl. See "Support for strings represented as a vector of ordinals" for more on that.
To cope with the new versioning system's use of at least three significant digits for each version component, the method used for incrementing the subversion number has also changed slightly. We assume that versions older than v5.6.0 have been incrementing the subversion component in multiples of 10. Versions after v5.6.0 will increment them by 1. Thus, using the new notation, 5.005_03 is the "same" as v5.5.30, and the first maintenance version following v5.6.0 will be v5.6.1 (which should be read as being equivalent to a floating point value of 5.006_001 in the older format, stored in $]).
sub mymethod : locked method; ... sub mymethod : locked method { ... } sub othermethod :locked :method; ... sub othermethod :locked :method { ... }
(Note how only the first ":" is mandatory, and whitespace surrounding the ":" is optional.)
AutoSplit.pm and SelfLoader.pm have been updated to keep the attributes with the stubs they provide. See attributes.
sub myopen { open my $fh, "@_" or die "Can't open '@_': $!"; return $fh; } { my $f = myopen("</etc/motd"); print <$f>; # $f implicitly closed here }
(1) natively as longs or ints (2) via special compiler flags (3) using long long or int64_t
is able to use "quads" (64-bit integers) as follows:
Note that unless you have the case (a) you will have to configure and compile Perl using the -Duse64bitint Configure flag.
NOTE: The Configure flags -Duselonglong and -Duse64bits have been deprecated. Use -Duse64bitint instead.
There are actually two modes of 64-bitness: the first one is achieved using Configure -Duse64bitint and the second one using Configure -Duse64bitall. The difference is that the first one is minimal and the second one maximal. The first works in more places than the second.
The "use64bitint" does only as much as is required to get 64-bit integers into Perl (this may mean, for example, using "long longs") while your memory may still be limited to 2 gigabytes (because your pointers could still be 32-bit). Note that the name "64bitint" does not imply that your C compiler will be using 64-bit "int"s (it might, but it doesn't have to): the "use64bitint" means that you will be able to have 64 bits wide scalar values.
The "use64bitall" goes all the way by attempting to switch also integers (if it can), longs (and pointers) to being 64-bit. This may create an even more binary incompatible Perl than -Duse64bitint: the resulting executable may not run at all in a 32-bit box, or you may have to reboot/reconfigure/rebuild your operating system to be 64-bit aware.
Natively 64-bit systems like Alpha and Cray need neither -Duse64bitint nor -Duse64bitall.
Last but not least: note that due to Perl's habit of always using floating point numbers, the quads are still not true integers. When quads overflow their limits (0...18_446_744_073_709_551_615 unsigned, -9_223_372_036_854_775_808...9_223_372_036_854_775_807 signed), they are silently promoted to floating point numbers, after which they will start losing precision (in their lower digits).
NOTE: 64-bit support is still experimental on most platforms. Existing support only covers the LP64 data model. In particular, the LLP64 data model is not yet supported. 64-bit libraries and system APIs on many platforms have not stabilized--your mileage may vary.
NOTE: The default action is to enable large file support, if available on the platform.
If the large file support is on, and you have a Fcntl constant O_LARGEFILE, the O_LARGEFILE is automatically added to the flags of sysopen().
Beware that unless your filesystem also supports "sparse files" seeking to umpteen petabytes may be inadvisable.
Note that in addition to requiring a proper file system to do large files you may also need to adjust your per-process (or your per-system, or per-process-group, or per-user-group) maximum filesize limits before running Perl scripts that try to handle large files, especially if you intend to write such files.
Finally, in addition to your process/process group maximum filesize limits, you may have quota limits on your filesystems that stop you (your user id or your user group id) from using large files.
Adjusting your process/user/group/file system/operating system limits is outside the scope of Perl core language. For process limits, you may try increasing the limits using your shell's limits/limit/ulimit command before running Perl. The BSD::Resource extension (not included with the standard Perl distribution) may also be of use, it offers the getrlimit/setrlimit interface that can be used to adjust process resource usage limits, including the maximum filesize limit.
For unprototyped sort subroutines, the historical behavior of passing the elements to be compared as the global variables $a and $b remains unchanged.
NOTE: This is currently an experimental feature. Interfaces and implementation are subject to change.
These changes should result in better random numbers from rand().
Thus:
$foo = ($bar) = qw(a b c); print "$foo|$bar\n";
now correctly prints "3|a", instead of "2|a".
Another familiar problem is with circular references. When an object references itself, its reference count would never go down to zero, and it would not get destroyed until the program is about to exit.
Weak references solve this by allowing you to "weaken" any reference, that is, make it not count towards the reference count. When the last non-weak reference to an object is deleted, the object is destroyed and all the weak references to the object are automatically undef-ed.
To use this feature, you need the Devel::WeakRef package from CPAN, which contains additional documentation.
NOTE: This is an experimental feature. Details are subject to change.
$answer = 0b101010; printf "The answer is: %b\n", oct("0b101010");
NOTE: This is an experimental feature. Details are subject to change.
exists() can be used to check whether an array element has been initialized. This avoids autovivifying array elements that don't exist. If the array is tied, the EXISTS() method in the corresponding tied package will be invoked.
delete() may be used to remove an element from the array and return it. The array element at that position returns to its uninitialized state, so that testing for the same element with exists() will return false. If the element happens to be the one at the end, the size of the array also shrinks up to the highest element that tests true for exists(), or 0 if none such is found. If the array is tied, the DELETE() method in the corresponding tied package will be invoked.
See "exists" in perlfunc and "delete" in perlfunc for examples.
When applied to a pseudo-hash element, exists() now reports whether the specified value exists, not merely if the key is valid.
delete() now works on pseudo-hashes. When given a pseudo-hash element or slice it deletes the values corresponding to the keys (but not the keys themselves). See "Pseudo-hashes: Using an array as a hash" in perlref.
Pseudo-hash slices with constant keys are now optimized to array lookups at compile-time.
List assignments to pseudo-hash slices are now supported.
The "fields" pragma now provides ways to create pseudo-hashes, via fields::new() and fields::phash(). See fields.
NOTE: The pseudo-hash data type continues to be experimental. Limiting oneself to the interface elements provided by the fields pragma will provide protection from any future changes.
This is not supported on some platforms like Solaris where a suitably correct implementation of fflush(NULL) isn't available.
The child process now communicates with the parent about the error in launching the external command, which allows these constructs to return with their usual error value and set $!.
Diagnostics emitted from code running in threads other than the main thread are now accompanied by the thread ID.
Embedded null characters in diagnostics now actually show up. They used to truncate the message in prior versions.
$foo::a and $foo::b are now exempt from "possible typo" warnings only if sort() is encountered in package "foo".
Unrecognized alphabetic escapes encountered when parsing quote constructs now generate a warning, since they may take on new semantics in later versions of Perl.
Many diagnostics now report the internal operation in which the warning was provoked, like so:
Use of uninitialized value in concatenation (.) at (eval 1) line 1. Use of uninitialized value in print at (eval 1) line 1.
Diagnostics that occur within eval may also report the file and line number where the eval is located, in addition to the eval sequence number and the line number within the evaluated text itself. For example:
Not enough arguments for scalar at (eval 4)[newlib/perl5db.pl:1411] line 2, at EOF
print defined(&foo,&bar,&baz); print uc("foo","bar","baz"); undef($foo,&bar);
used to be accidentally allowed in earlier versions, and produced unpredictable behaviour. Some produced ancillary warnings when used in this way; others silently did the wrong thing.
The parenthesized forms of most unary operators that expect a single argument now ensure that they are not called with more than one argument, making the cases shown above syntax errors. The usual behaviour of:
print defined &foo, &bar, &baz; print uc "foo", "bar", "baz"; undef $foo, &bar;
remains unchanged. See perlop.
The "passwd" and "shell" fields returned by the getpwent(), getpwnam(), and getpwuid() are now tainted, because the user can affect their own encrypted password and login shell.
The variable modified by shmread(), and messages returned by msgrcv() (and its object-oriented interface IPC::SysV::Msg::rcv) are also tainted, because other untrusted processes can modify messages and shared memory segments for their own nefarious purposes.
Arguments prototyped as "*" will now be visible within the subroutine as either a simple scalar or as a reference to a typeglob. See "Prototypes" in perlsub.
The old syntax has not changed. As before, `^X' may be either a literal control-X character or the two-character sequence `caret' plus `X'. When braces are omitted, the variable name stops after the control character. Thus "$^XYZ" continues to be synonymous with "$^X . "YZ"" as before.
As before, lexical variables may not have names beginning with control characters. As before, variables whose names begin with a control character are always forced to be in package `main'. All such variables are reserved for future extensions, except those that begin with "^_", which may be used by user programs and are guaranteed not to acquire special meaning in any future version of Perl.
See "Support for strings represented as a vector of ordinals" for an example.
This behavior must be specifically enabled when running Configure. See INSTALL and README.Y2K.
Literal @example now requires backslash
In versions 5.004_01 through 5.6.0, the error was
In string, @example now must be written as \@example
The idea here was to get people into the habit of writing<EMAIL_ADDRESS>when they wanted a literal "@" sign, just as they have always written "Give me back my \$5" when they wanted a literal "$" sign.
Starting with 5.6.1, when Perl now sees an "@" sign in a double-quoted string, it always attempts to interpolate an array, regardless of whether or not the array has been used or declared already. The fatal error has been downgraded to an optional warning:
Possible unintended interpolation of @example in string
This warns you that<EMAIL_ADDRESS>is going to turn into "fred.com" if you don't backslash the "@". See http://perl.plover.com/at-error.html for more details about the history here.
NOTE: The Compiler suite remains highly experimental. The generated code may not be correct, even when it manages to execute without errors.
You can now run tests for n seconds instead of guessing the right number of tests to run: e.g., timethese(-5, ...) will run each code for at least 5 CPU seconds. Zero as the "number of repetitions" means "for at least 3 CPU seconds". The output format has also changed. For example:
use Benchmark;$x=3;timethese(-5,{a=>sub{$x*$x},b=>sub{$x**2}})
will now output something like this:
Benchmark: running a, b, each for at least 5 CPU seconds... a: 5 wallclock secs ( 5.77 usr + 0.00 sys = 5.77 CPU) @ 200551.91/s (n=1156516) b: 4 wallclock secs ( 5.00 usr + 0.02 sys = 5.02 CPU) @ 159605.18/s (n=800686)
New features: "each for at least N CPU seconds...", "wallclock secs", and the "@ operations/CPU second (n=operations)".
timethese() now returns a reference to a hash of Benchmark objects containing the test results, keyed on the names of the tests.
timethis() now returns the iterations field in the Benchmark result object instead of 0.
timethese(), timethis(), and the new cmpthese() (see below) can also take a format specifier of 'none' to suppress output.
A new function countit() is just like timeit() except that it takes a TIME instead of a COUNT.
A new function cmpthese() prints a chart comparing the results of each test returned from a timethese() call. For each possible pair of tests, the percentage speed difference (iters/sec or seconds/iter) is shown.
For other details, see Benchmark.
The new version also allows a leading underscore in constant names, but disallows a double leading underscore (as in "__LINE__"). Some other names are disallowed or warned against, including BEGIN, END, etc. Some names which were forced into main:: used to fail silently in some cases; now they're fatal (outside of main::) and an optional warning (inside of main::). The ability to detect whether a constant had been set with a given name has been added.
See constant.
The XSUB implementation of Dump() is now automatically called if the "Useqq" setting is not in use.
Dumping "qr//" objects works correctly.
Perl can also optionally arrange to unload all extension shared objects loaded by Perl. To enable this, build Perl with the Configure option "-Accflags=-DDL_UNLOAD_ALL_AT_EXIT". (This maybe useful if you are using Apache with mod_perl.)
A bug that caused File::Find to lose track of the working directory when pruning top-level directories has been fixed.
File::Find now also supports several other options to control its behavior. It can follow symbolic links if the "follow" option is specified. Enabling the "no_chdir" option will make File::Find skip changing the current directory when walking directories. The "untaint" flag can be useful when running with taint checks enabled.
See File::Find.
$fullname = catfile($dir1, $dir2, $file);
instead of
$fullname = File::Spec->catfile($dir1, $dir2, $file);
Getopt::Long encourages the use of Pod::Usage to produce help messages. For example:
use Getopt::Long; use Pod::Usage; my $man = 0; my $help = 0; GetOptions('help|?' => \$help, man => \$man) or pod2usage(2); pod2usage(1) if $help; pod2usage(-exitstatus => 0, -verbose => 2) if $man; __END__ =head1 NAME sample - Using Getopt::Long and Pod::Usage =head1 SYNOPSIS sample [options] [file ...] Options: -help brief help message -man full documentation =head1 OPTIONS =over 8 =item B<-help> Print a brief help message and exits. =item B<-man> Prints the manual page and exits. =back =head1 DESCRIPTION B<This program> will read the given input file(s) and do something useful with the contents thereof. =cut
See Pod::Usage for details.
A bug that prevented the non-option call-back <> from being specified as the first argument has been fixed.
To specify the characters < and > as option starters, use ><. Note, however, that changing option starters is strongly deprecated.
You can now create a TCP-based IO::Socket::INET without forcing a connect attempt. This allows you to configure its options (like making it non-blocking) and then call connect() manually.
A bug that prevented the IO::Socket::protocol() accessor from ever returning the correct value has been corrected.
IO::Socket::connect now uses non-blocking IO instead of alarm() to do connect timeouts.
IO::Socket::accept now uses select() instead of alarm() for doing timeouts.
IO::Socket::INET->new now sets $! correctly on failure. $@ is still set for backwards compatibility.
The class method "display_format" and the corresponding object method "display_format", in addition to accepting just one argument, now can also accept a parameter hash. Recognized keys of a parameter hash are "style", which corresponds to the old one parameter case, and two new parameters: "format", which is a printf()-style format string (defaults usually to "%.15g", you can revert to the default by setting the format string to "undef") used for both parts of a complex number, and "polar_pretty_print" (defaults to true), which controls whether an attempt is made to try to recognize small multiples and rationals of pi (2pi, pi/2) at the argument (angle) of a polar complex number.
The potentially disruptive change is that in list context both methods now return the parameter hash, instead of only the value of the "style" parameter.
Pod::InputObjects defines some input objects needed by Pod::Parser, and for advanced users of Pod::Parser that need more about a command besides its name and text.
As of release 5.6.0 of Perl, Pod::Parser is now the officially sanctioned "base parser code" recommended for use by all pod2xxx translators. Pod::Text (pod2text) and Pod::Man (pod2man) have already been converted to use Pod::Parser and efforts to convert Pod::HTML (pod2html) are already underway. For any questions or comments about pod parsing and translating issues and utilities, please use the<EMAIL_ADDRESS>mailing list.
For further information, please see Pod::Parser and Pod::InputObjects.
There is also a pod2usage script which can be used from other kinds of scripts to print usage messages from pods (even for non-Perl scripts with pods embedded in comments).
For details and examples, please see Pod::Usage.
pod2man has been turned into a module, Pod::Man, which also uses Pod::Parser. In the process, several outstanding bugs related to quotes in section headers, quoting of code escapes, and nested lists have been fixed. pod2man is now a wrapper script around this module.
A bug that may have caused data loss when more than one disk block happens to be read from the database in a single FETCH() has been fixed.
Win32::FsType Win32::GetOSVersion
The remaining functions are unchanged and continue to return "undef" on error even in list context.
The Win32::SetLastError(ERROR) function has been added as a complement to the Win32::GetLastError() function.
The new Win32::GetFullPathName(FILENAME) returns the full absolute pathname for FILENAME in scalar context. In list context it returns a two-element list containing the fully qualified directory name and the filename. See Win32.
filter_store_key filter_store_value filter_fetch_key filter_fetch_value
These can be used to filter key-value pairs before the pairs are written to the database or just after they are read from the database. See perldbmfilter for further information.
Lexical warnings pragma, "use warnings;", to control optional warnings. See perllexwarn.
"use filetest" to control the behaviour of filetests ("-r" "-w" ...). Currently only one subpragma implemented, "use filetest 'access';", that uses access(2) or equivalent to check permissions instead of using stat(2) as usual. This matters in filesystems where there are ACLs (access control lists): the stat(2) might lie, but access(2) knows better.
The "open" pragma can be used to specify default disciplines for handle constructors (e.g. open()) and for qx//. The two pseudo-disciplines ":raw" and ":crlf" are currently supported on DOS-derivative platforms (i.e. where binmode is not a no-op). See also "binmode() can be used to set :crlf and :raw modes".
Support for non-Unix platforms has been improved.
As of v5.6.0, interpreter-threads support is still lacking a way to create new threads from Perl (i.e., "use Thread;" will not work with interpreter threads). "use Thread;" continues to be available when you specify the -Duse5005threads option to Configure, bugs and all.
NOTE: Support for threads continues to be an experimental feature. Interfaces and implementation are subject to sudden and drastic changes.
usemultiplicity usethreads useithreads (new interpreter threads: no Perl API yet) usethreads use5005threads (threads as they were in 5.005) use64bitint (equal to now deprecated 'use64bits') use64bitall uselongdouble usemorebits uselargefiles usesocks (only SOCKS v5 supported)
See "Large file support" for more information.
http://www.socks.nec.com/
If you previously used "Configure -Dsitelib" or "-Dsitearch" to set special values for library directories, you might wish to consider using the new "-Dsiteprefix" setting instead. Also, if you wish to re-use a config.sh file from an earlier version of perl, you should be sure to check that Configure makes sensible choices for the new directories. See INSTALL for complete details.
It is unclear whether future versions will renew support for this platform, but the possibility exists.
Expand %ENV-handling code to allow runtime mapping to logical names, CLI symbols, and CRTL environ array.
Extension of subprocess invocation code to accept filespecs as command "verbs".
Add to Perl command line processing the ability to use default file types and to recognize Unix-style "2>&1".
Expansion of File::Spec::VMS routines, and integration into ExtUtils::MM_VMS.
Extension of ExtUtils::MM_VMS to handle complex extensions more flexibly.
Barewords at start of Unix-syntax paths may be treated as text rather than only as logical names.
Optional secure translation of several logical names used internally by Perl.
Miscellaneous bugfixing and porting of new core code to VMS.
Thanks are gladly extended to the many people who have contributed VMS patches, testing, and ideas.
When given a pathname that consists only of a drivename, such as "A:", opendir() and stat() now use the current working directory for the drive rather than the drive root.
The builtin XSUB functions in the Win32:: namespace are documented. See Win32.
$^X now contains the full path name of the running executable.
A Win32::GetLongPathName() function is provided to complement Win32::GetFullPathName() and Win32::GetShortPathName(). See Win32.
POSIX::uname() is supported.
system(1,...) now returns true process IDs rather than process handles. kill() accepts any real process id, rather than strictly return values from system(1,...).
For better compatibility with Unix, "kill(0, $pid)" can now be used to test whether a process exists.
The "Shell" module is supported.
Better support for building Perl under command.com in Windows 95 has been added.
Scripts are read in binary mode by default to allow ByteLoader (and the filter mechanism in general) to work properly. For compatibility, the DATA filehandle will be set to text mode if a carriage return is detected at the end of the line containing the __END__ or __DATA__ token; if not, the DATA filehandle will be left open in binary mode. Earlier versions always opened the DATA filehandle in text mode.
The glob() operator is implemented via the "File::Glob" extension, which supports glob syntax of the C shell. This increases the flexibility of the glob() operator, but there may be compatibility issues for programs that relied on the older globbing syntax. If you want to preserve compatibility with the older syntax, you might want to run perl with "-MFile::DosGlob". For details and compatibility information, see File::Glob.
This means that the following will append "foo" to an empty file (it used to do nothing):
perl -0777 -pi -e 's/^/foo/' empty_file
The behaviour of:
perl -pi -e 's/^/foo/' empty_file
is unchanged (it continues to leave the file empty).
Lexical lookups for variables appearing in "eval '...'" within functions that were themselves called within an "eval '...'" were searching the wrong place for lexicals. The lexical search now correctly ends at the subroutine's block boundary.
The use of "return" within "eval {...}" caused $@ not to be reset correctly when no exception occurred within the eval. This has been fixed.
Parsing of here documents used to be flawed when they appeared as the replacement expression in "eval 's/.../.../e'". This has been fixed.
The mechanism for reporting such errors has been reimplemented to queue compile-time errors and report them at the end of the compilation as true errors rather than as warnings. This fixes cases where error messages leaked through in the form of warnings when code was compiled at run time using "eval STRING", and also allows such errors to be reliably trapped using "eval "..."".
The new behavior is to produce an empty list if (and only if) the original list was empty. Consider the following example:
@a = (1,undef,undef,2)[2,1,2];
The old behavior would have resulted in @a having no elements. The new behavior ensures it has three undefined elements.
Note in particular that the behavior of slices of the following cases remains unchanged:
@a = ()[1,2]; @a = (getpwent)[7,0]; @a = (anything_returning_empty_list())[2,1,2]; @a = @b[2,1,2]; @a = @c{'a','b','c'};
See perldata.
Numbers formatted according to the local numeric locale (such as using a decimal comma instead of a decimal dot) caused "isn't numeric" warnings, even while the operations accessing those numbers produced correct results. These warnings have been discontinued.
Operations that aren't filehandle constructors used to leak memory when used on invalid filehandles. This has been fixed.
Constructs that modified @_ could fail to deallocate values in @_ and thus leak memory. This has been corrected.
See "Support for CHECK blocks" for how to run things when the compile phase ends.
This caveat is now better explained in the documentation. See perldata.
$foo{$bar} $ref->{"susie"}[12]
$foo{$bar} $ref->{"susie"}[12]
or a hash or array slice, such as:
@foo[$bar, $baz, $xyzzy] @{$ref->[12]}{"susie", "queue"}
Failure of user callbacks dispatched using the "G_KEEPERR" flag could also result in this warning. See "G_KEEPERR" in perlcall.
open FOO || die;
It may also indicate a misspelled constant that has been interpreted as a bareword:
use constant TYPO => 1; if (TYOP) { print "foo" }
The "strict" pragma is useful in avoiding such errors.
See also perlport for writing portable code.
my $foo, $bar = @_;
when you meant
my ($foo, $bar) = @_;
Remember that "my", "our", and "local" bind tighter than comma.
print<EMAIL_ADDRESS>and the array @example doesn't exist, Perl is going to print "fred.com", which is probably not what you wanted. To get a literal "@" sign in a string, put a backslash before it, just as you would to get a literal "$" sign.
sub doit { use attrs qw(locked); }
You should use the new declaration syntax instead.
sub doit : locked { ...
The "use attrs" pragma is now obsolete, and is only provided for backward-compatibility. See "Subroutine Attributes" in perlsub.
Since all new warnings must be explicitly requested via the "-w" switch or the "warnings" pragma, it is ultimately the programmer's responsibility to ensure that warnings are enabled judiciously.
See "Improved Perl version numbering system" for the reasons for this change.
For example, "print 97.98.99" used to output 97.9899 in earlier versions, but now prints "abc".
See "Support for strings represented as a vector of ordinals".
See "Better pseudo-random number generator".
See "Better worst-case behavior of hashes" for additional information.
See "More consistent close-on-exec behavior".
In Perl 5.6.0 and later, "$$1" always means "${$1}".
delete(), each(), values() and hashes (e.g. "\(%h)") in a list context return the actual values in the hash, instead of copies (as they used to in earlier versions). Typical idioms for using these constructs copy the returned values, but this can make a significant difference when creating references to the returned values. Keys in the hash are still returned as copies when iterating on a hash.
See also "delete(), each(), values() and hash iteration are faster".
As a result, the parenthesized form can be used with "grep" and "map". The following construct used to be a syntax error before, but it works as expected now:
grep not($_), @things;
On the other hand, using "not" with a literal list slice may not work. The following previously allowed construct:
print not (1,2,3)[0];
needs to be written with additional parentheses now:
print not((1,2,3)[0]);
The behavior remains unaffected when "not" is not followed by parentheses.
See "More functional bareword prototype (*)".
See "Bit operators support full native integer width".
To avoid these new tainting behaviors, you can build Perl with the Configure option "-Accflags=-DINCOMPLETE_TAINTS". Beware that the ensuing perl binary may be insecure.
perl Makefile.PL POLLUTE=1
This means that there is a source compatibility issue as a result of this if your extensions attempt to use pointers to any of the Perl API functions.
Note that the above issue is not relevant to the default build of Perl, whose interfaces continue to match those of prior versions (but subject to the other options described here).
See "Background and PERL_IMPLICIT_CONTEXT" in perlguts for detailed information on the ramifications of building Perl with this option.
NOTE: PERL_IMPLICIT_CONTEXT is automatically enabled whenever Perl is built with one of -Dusethreads, -Dusemultiplicity, or both. It is not intended to be enabled by users at this time.
As of release 5.6.0, Perl's malloc family of functions have default names distinct from the system versions. You need to explicitly compile perl with "-DPERL_POLLUTE_MALLOC" to get the older behaviour. HIDEMYMALLOC and EMBEDMYMALLOC have no effect, since the behaviour they enabled is now the default.
Note that these functions do not constitute Perl's memory allocation API. See "Memory Allocation" in perlguts for further information about that.
The new names cause less pollution of the cpp namespace and reflect what the numbers have come to stand for in common practice. For compatibility, the old names are still supported when patchlevel.h is explicitly included (as required before), so there is no source incompatibility from the change.
The usethreads or usemultiplicity builds are not binary compatible with the corresponding builds in 5.005.
On platforms that require an explicit list of exports (AIX, OS/2 and Windows, among others), purely internal symbols such as parser functions and the run time opcodes are not exported by default. Perl 5.005 used to export all functions irrespective of whether they were considered part of the public API or not.
For the full list of public API functions, see perlapi.
use Tie::Hash; tie my %tie_hash => 'Tie::StdHash'; ... local($tie_hash{Foo}) = 1; # leaks
Subtest #15 of lib/b.t may fail under 64-bit builds on platforms such as HP-UX PA64 and Linux IA64. The issue is still being investigated.
The lib/io_multihomed test may hang in HP-UX if Perl has been configured to be 64-bit. Because other 64-bit platforms do not hang in this test, HP-UX is suspect. All other tests pass in 64-bit HP-UX. The test attempts to create and connect to "multihomed" sockets (sockets which have multiple IP addresses).
Note that 64-bit support is still experimental.
The subtests 19 and 20 of lib/thr5005.t test are known to fail due to fundamental problems in the 5.005 threading implementation. These are not new failures--Perl 5.005_0x has the same bugs, but didn't have these tests. (Note that support for 5.005-style threading remains experimental.)
In NEXTSTEP 3.3p2 the implementation of the strftime(3) in the operating system libraries is buggy: the %j format numbers the days of a month starting from zero, which, while being logical to programmers, will cause the subtests 19 to 27 of the lib/posix test may fail.
If compiled with gcc 2.95 the lib/sdbm test will fail (dump core). The cure is to use the vendor cc, it comes with the operating system and produces good code.
The 5.6.1 release improves support for EBCDIC platforms, but they are not fully supported yet.
Guessing which symbols your C compiler and preprocessor define... CC-20 cc: ERROR File = try.c, Line = 3 ... bad switch yylook 79bad switch yylook 79bad switch yylook 79bad switch yylook 79#ifdef A29K ... 4 errors detected in the compilation of "try.c".
The culprit is the broken awk of UNICOS/mk. The effect is fortunately rather mild: Perl itself is not adversely affected by the error, only the h2ph utility coming with Perl, and that is rather rarely needed these days.
@x->[2] scalar(@x)->[2]
These expressions will get run-time errors in some future release of Perl.
(Someday it will simply assume that an unbackslashed @ interpolates an array.)
That day has come, and this fatal error has been removed. It has been replaced by a non-fatal warning instead. See "Arrays now always interpolate into double-quoted strings" for details.
open FOO || die;
However, the developers of Perl 5.004 could not fix this bug completely, because at least two widely-used modules depend on the old meaning of "$$0" in a string. So Perl 5.004 still interprets "$$<digit>" in the old (broken) way inside strings; but it generates this message as a warning. And in Perl 5.005, this special treatment will cease.
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.
The INSTALL file for how to build Perl.
The README file for general stuff.
The Artistic and Copying files for copyright information.
Send omissions or corrections to<EMAIL_ADDRESS>| 2019-10-21 | perl v5.30.3 |


A revolutionary, new buy-sell platform where we match sellers looking to raffle off their item with hundreds of interested micro-bidders. No more indefinite waiting periods, no more hassle. An opportunity to buy everything you desire for a fraction of its price, all guilt free!
Design Document
Project Manager:
Nick Giannarakis<EMAIL_ADDRESS>Team Members:
Lucas Irvine<EMAIL_ADDRESS>Prateek Swain<EMAIL_ADDRESS>(Team Leader)
Steven Takeshita<EMAIL_ADDRESS>Antony Toron<EMAIL_ADDRESS>Dominic Whyte<EMAIL_ADDRESS>March 3, 2017
Survey classmates to measure product demand and interest.
March 7, 2012
Meeting with Professor Kernighan, obtain project approval.
March 24, 2017
Develop a structured contract between the different tiers of the application (API, data processed in database, etc.) and assign roles to each member of the team, based on interest and expertise.
March 31, 2017
Have a working prototype of the payment system (likely using Stripe), to eliminate the uncertainties associated with implementing delayed transactions. Decide on database layout and begin implementation of MVP API functions. On the front end, have a full drawn-out layout of the MVP design and begin working on implementation.
April 7, 2017
Test working server, which should implement the functions necessary for adding an item for sale, bidding on an item, and performing the lottery (including working database). Front end should be functional on large screens, work now on mobile optimization.
April 14, 2017
Project Prototype. Minimal Viable Product prototype test - By the 14th, have an initial working version which can handle the baseline functionality, ie., add an item for sale, bid on an item, and perform the lottery (including thorough documentation). Frontend must allow for this functionality. Determine bugs, areas for improvement in UI and decide what areas we need to focus on most before the April 24th launch.
April 18, 2017
Heavily polish the MVP by the 18th, and begin adding non-baseline features, such as displaying lottery odds to users and newsfeed, subject to pivot.
April 24th, 2017
Launch. Release the latest version for student use, by marketing on campus and posting to listservers. Goal will be to auction off 5 items to students in the first 10 days. In the next week, work on adding any key supplementary features and on bug fixes based on student feedback.
April 28, 2017
Alpha Test. Finalize adding supplementary features, and do stress as well as corner testing.
May 4-5, 2017
Beta test. No more feature adding - spend these days rigorously testing the existing product.
May 8-10, 2017
Demo day.
May 14, 2017 (midnight)
Final submission for Dean's Date.


Pattaya International Marathon
Pattaya THA
Website: www.pattayamarathon.go.th
Race Winners
(19 runnings)
15 Jul
2007
16 Jul
2006
17 Jul
2005
18 Jul
2004
2003
21 Jul
2002
2001
2000
1999
1998
1997
Notes: 1997 is believed to have been the inaugural year.
17
Jul
2016
2:39:33
Noah Kutung Chesergon (KEN)
3:10:16
Tabitha Wambui Gichia (KEN)
19
Jul
2015
2:32:36
Onesmus Mutisya (KEN)
3:09:51
Viola Chepchirchir Kimeli-2
27
Jul
2014
2:25:32
Alex Melly (KEN)
3:00:15
Viola Chepchirchir Kimeli (KEN)
21
Jul
2013
2:20:33
Joseph Gitau Kariuki (KEN)
2:42:46
Rose Cherotich Kosgei (KEN)
15 Jul
2012
2:22:25
Lawrence Saina Kiptoo-2
2:42:50
Elizabeth Chemweno Cheruiyot-2
17 Jul
2011
2:21:06
Lawrence Saina Kiptoo (KEN)
2:44:09
Elizabeth Chemweno Cheruiyot (KEN)
18 Jul
2010
2:23:13
Julius Kiplimo Maisei (KEN)
2:54:10
Fridah Lodepa Chepkite-2
19 Jul
2009
2:22:41
Michael Kipserem Kipkorir (KEN)
2:49:38
Sunisa Sailomyen-6
20 Jul
2008
2:16:07
Nelson Kirwa Rotich (KEN)
2:53:35
Fridah Lodepa Chepkite (KEN)
2:19:41
Joel Kemboi Kiplimo (KEN)
2:58:33
Sunisa Sailomyen-5
2:33:18
Julius Kiptum Rop (KEN)
3:10:12
Sunisa Sailomyen-4
2:34:33
John Kipngeno Rotich (KEN)
3:11:42
Sunisa Sailomyen-3
2:26:33
John Kelai Ekiru (KEN)
3:04:48
Sunisa Sailomyen-2
---
n/a
---
n/a
2:32:23
Viktor Baranov (RUS)
3:01:35
Sunisa Sailomyen (THA)
---
n/a
---
n/a
---
n/a
---
n/a
---
n/a
---
n/a
---
n/a
---
n/a
---
n/a
---
n/a
Most Wins (1997/date)
Men
2
Lawrence Saina Kiptoo (KEN)
2011-12
Women 6
Sunisa Sailomyen (THA)
2002,2004-07,2009
Prize Money
(ADR qualified runners)
Year Men Women Total 2016 $1,000 $715 $1,715 2015 1,740 1,885 3,625 .... 2009 15,880 14,995 30,875 Sums $18,620 $17,595 $36,215
Race Time Bias
(sec/km)
Insufficient information to calculate the race time bias
Competitive Level (1990-date)
Year Men Women
2013 407 231
Quality Performances
Men <2:17 1 <2:18 2 <2:19 2 <2:20 4 Women <2:44 3 <2:46 6 <2:48 7 <2:50 9
Last Updated on 20 Jul 2016
Contributor: Klaas Loonstra (5)


"" Driver for controlling the Synchronous Serial Port.
De-Init the SSP module.
Definition at line 23 of file Drv_SSP.c.
Init the SSP module.
Definition at line 13 of file Drv_SSP.c.
Configuration of format and data of the SSP module.
Definition at line 31 of file Drv_SSP.c.
| uint8_t Drv_SSP_transferByte |
( |
uint8_t |
to_send | ) |
|
Send and Receive a byte via SSP.
- Parameters
-
- Returns
- Received byte
Definition at line 59 of file Drv_SSP.c.
| uint8_t spi_rw |
( |
uint8_t |
out | ) |
|
Faster way to transfer a single a byte via SSP.
- Parameters
-
- Returns
- in Received byte
Definition at line 83 of file Drv_SSP.c.


Las Vegas police seek help finding missing woman, 48
by Alexis EgelandLas Vegas police seek the public’s help locating a missing and endangered adult woman.
Jennifer Cleary, 48, was last seen around 10 a.m. Sunday near Rancho Drive and Vegas Drive, police said.
Police said Cleary “is suffering from extreme emotional distress and may be in need of medical attention.”
Anyone with information may contact the Las Vegas Metropolitan Police Department at<PHONE_NUMBER> or the Missing Persons Detail at<PHONE_NUMBER>.


| 1 | /** | |
| 2 | * Copyright 2010 Mozilla Foundation | |
| 3 | * | |
| 4 | * Licensed to the Apache Software Foundation (ASF) under one | |
| 5 | * or more contributor license agreements. See the NOTICE file | |
| 6 | * distributed with this work for additional information | |
| 7 | * regarding copyright ownership. The ASF licenses this file | |
| 8 | * to you under the Apache License, Version 2.0 (the | |
| 9 | * "License"); you may not use this file except in compliance | |
| 10 | * with the License. You may obtain a copy of the License at | |
| 11 | * | |
| 12 | * http://www.apache.org/licenses/LICENSE-2.0 | |
| 13 | * | |
| 14 | * Unless required by applicable law or agreed to in writing, software | |
| 15 | * distributed under the License is distributed on an "AS IS" BASIS, | |
| 16 | * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | |
| 17 | * See the License for the specific language governing permissions and | |
| 18 | * limitations under the License. | |
| 19 | */ | |
| 20 | package com.mozilla.pig.eval.regex; | |
| 21 | ||
| 22 | import java.io.IOException; | |
| 23 | import java.util.regex.Matcher; | |
| 24 | import java.util.regex.Pattern; | |
| 25 | ||
| 26 | import org.apache.pig.EvalFunc; | |
| 27 | import org.apache.pig.data.Tuple; | |
| 28 | import org.apache.pig.data.TupleFactory; | |
| 29 | ||
| 30 | public class FindAll extends EvalFunc<Tuple> { | |
| 31 | ||
| 32 | private static TupleFactory tupleFactory = TupleFactory.getInstance(); | |
| 33 | | |
| 34 | private Pattern p; | |
| 35 | | |
| 36 | public FindAll(String pattern) { | |
| 37 | p = Pattern.compile(pattern); | |
| 38 | } | |
| 39 | | |
| 40 | public Tuple exec(Tuple input) throws IOException { | |
| 41 |
3
1. exec : negated conditional → NO_COVERAGE 2. exec : negated conditional → NO_COVERAGE 3. exec : ROR: changed not equals zero comparison to less than operator → NO_COVERAGE |
if (input == null || input.size() == 0) { |
| 42 |
1
1. exec : mutated return of Object value for com/mozilla/pig/eval/regex/FindAll::exec to ( if (x != null) null else throw new RuntimeException ) → NO_COVERAGE |
return null; |
| 43 | } | |
| 44 | | |
| 45 | Matcher m = p.matcher((String)input.get(0)); | |
| 46 |
2
1. exec : negated conditional → NO_COVERAGE 2. exec : ROR: changed not equals zero comparison to less than operator → NO_COVERAGE |
if (!m.find()) { |
| 47 |
1
1. exec : mutated return of Object value for com/mozilla/pig/eval/regex/FindAll::exec to ( if (x != null) null else throw new RuntimeException ) → NO_COVERAGE |
return null; |
| 48 | } | |
| 49 | | |
| 50 | Tuple result = tupleFactory.newTuple(); | |
| 51 | // Add the one we just found | |
| 52 |
1
1. exec : removed call to org/apache/pig/data/Tuple::append → NO_COVERAGE |
result.append(m.group()); |
| 53 | // Look for more | |
| 54 |
2
1. exec : negated conditional → NO_COVERAGE 2. exec : ROR: changed equals zero comparison to less than operator → NO_COVERAGE |
while (m.find()) { |
| 55 |
1
1. exec : removed call to org/apache/pig/data/Tuple::append → NO_COVERAGE |
result.append(m.group()); |
| 56 | } | |
| 57 | | |
| 58 |
1
1. exec : mutated return of Object value for com/mozilla/pig/eval/regex/FindAll::exec to ( if (x != null) null else throw new RuntimeException ) → NO_COVERAGE |
return result; |
| 59 | } | |
| 60 | | |
| 61 | } | |
Mutations | ||
| 41 |
1.1 2.2 3.3 |
|
| 42 |
1.1 |
|
| 46 |
1.1 2.2 |
|
| 47 |
1.1 |
|
| 52 |
1.1 |
|
| 54 |
1.1 2.2 |
|
| 55 |
1.1 |
|
| 58 |
1.1 |


About Me
I'm Casey Pitman, and I love solving problems.
I love puzzles. I love repairing cars and household appliances. And I love to code.
I began learning to code out of curiosity. I quickly became fascinated by the multitude of problems to solve and all the tools coding provided me. Through coding I learned to identify multiple solutions to any given problem. Solving problems through coding gives me satisfaction and a sense of purpose.
I live in Northeast Texas with my wife and two kids. There are a lot of pine trees and squirrels.
Projects
My Skills
My life has taken a few turns, and the skills I've learned have proven useful in my coding. As a journalist I learned to communicate clearly and to review, revise, and edit. As a law student I learned to think logically. As an educator I learned to organize and plan while remaining flexible enough to adapt to the unforeseen.
|
React |
Redux |
JavaScript |
|
Node.js |
HTML5 |
CSS3 |
|
Bootstrap |
Git |
GitHub |


The simplest and most intuitive workout tracker, designed to help you get better results from your workouts. Whether you want to gain strength or just stay healthy.
Whether you’re a beginner or an experienced powerlifter, we provide everything you need to record your workouts as effortlessly and as quickly as possible. Unlike other fitness apps, it doesn’t bog you down with distractions and unnecessary gimmicks you’d never use
The simplest and most intuitive workout tracker, designed to help you get better results from your workouts. Whether you want to gain strength or just stay healthy, join over 1.2 million people who have downloaded Strong to stay on track in the gym.
Whether you’re a beginner or an experienced powerlifter, Strong provides everything you need to record your workouts as effortlessly and as quickly as possible. Unlike other fitness apps, Strong doesn’t bog you down with distractions and unnecessary gimmicks you’d never use