text:
Bandwidth—the number of bits per second that a device or connection can transfer every second—is the number that everyone loves to talk about. Whether it be the gigabit per second that your Ethernet card does, boasting about your fancy new FTTP Internet connection at 85 megabits per second, or bemoaning the lousy 128 kilobits per second you get on hotel Wi-Fi, bandwidth gets the headlines.
Bandwidth isn't, however, the only number that's important when it comes to network performance. Latency—the time it takes the message you send to arrive at the other end—is also critically important. Depending on what you're trying to do, high latency can make your network connections crawl, even if your bandwidth is abundant.
Why latency matters
It's easy to understand why bandwidth is important. If a YouTube stream has a bitrate of 1Mb/s, it's obvious that to play it back in real time, without buffering, you'll need at least 1Mb/s of bandwidth. If the game you're installing from Steam is about 3.6GB and your bandwidth is about 8Mb/s, it will take about an hour to download.
Latency issues can be a bit subtler. Some are immediately obvious; others are less so.
Nowadays, almost all international phone calls are typically placed over undersea cables, but not too long ago, satellite routing was common. Anyone who's used one or seen one on TV will know that the experience is rather odd. Conversation takes on a disjointed character because of the noticeable delay between saying something and getting acknowledgement or a response from the person you're talking to. Free-flowing conversation is impossible. That's latency at work.
There are some applications, such as voice and video chatting, which suffer in exactly the same way as satellite calls of old. The time delay is directly observable, and it disrupts the conversation.
However, this isn't the only way in which latency can make its presence felt; it's merely the most obvious. Just as we acknowledge what someone is telling us in conversation (with the occasional nod of the head, "uh huh," "go on," and similar utterances), most Internet protocols have a similar system of acknowledgement. They don't send a continuous never-ending stream of bytes. Instead, they send a series of discrete packets. When you download a big file from a Web server, for example, the server doesn't simply barrage you with an unending stream of bytes as fast as it can. Instead, it sends a packet of perhaps a few thousand bytes at a time, then waits to hear back that they were received correctly. It doesn't send the next packet until it has received this acknowledgement.
Because of this two-way communication, latency can have a significant impact on a connection's throughput. All the bandwidth in the world doesn't help you if you're not actually sending any data because you're still waiting to hear back if the last bit of data you sent has arrived.
How latency works
It's traditional to examine networks using a layered model that separates different aspects of the network (the physical connection, the basic addressing and routing, the application protocol) and analyze them separately. There are two models in wide use, a 7-layered one called the OSI model and a 4-layered one used by IP, the Internet Protocol. IP's 4-layer model is what we're going to talk about here. It's a simpler model, and for most purposes, it's just as good.
Sometimes c just isn't enough
The bottom layer is called the link layer. This is the layer that provides local physical connectivity; this is where you have Ethernet, Wi-Fi, dial-up, or satellite connectivity, for example. This is the layer where we get bitten by an inconvenient fact of the universe: the speed of light is finite.
Take those satellite phones, for example. Communications satellites are in geostationary orbits, putting them about 35,786 kilometers above the equator. Even if the satellite is directly overhead, a signal is going to have to travel 71,572 km—35,786 km up, 35,786 km down. If you're not on the equator, directly under the satellite, the distance is even greater. Even at light speed that's going to take 0.24 seconds; every message you send over the satellite link will arrive a quarter of a second later. The reply to the message will take another quarter of a second, for a total round trip time of half a second.
Undersea cables are a whole lot shorter. While light travels slower in glass than it does in air, the result is a considerable improvement. The TAT-14 cable between the US and Europe has a total round trip length of about 15,428 km—barely more than a fifth the distance that a satellite connection has to go. Using undersea cables like TAT-14, the round trip time between London and New York can be brought down below 100 milliseconds, reaching about 60 milliseconds on the fastest links. The speed of light means that there's a minimum bound of about 45 milliseconds between the cities.
The link layer can have impact closer to home, too. Many of us use Wi-Fi on our networks. The airwaves are a shared medium: if one system is transmitting on a particular frequency, no other system nearby can use the same frequency. Sometimes two systems will start broadcasting simultaneously anyway. When this happens, they have to stop broadcasting and wait a random amount of time for a quiet period before trying again. Wired Ethernet can have similar collisions, though the modern prevalence of switches (replacing the hubs of old) has tended to make them less common.
The Internet is an internetwork
The link layer is the part that moves traffic around the local network. There are usually lots of links involved in using the Internet. For example, you might have home Wi-Fi and copper Ethernet to your modem, VDSL to a cabinet in the street, optical MPLS to an ISP, and then who knows. If you're unlucky, you might even have some satellite action in there. How does the data know where to go? That's all governed by the next layer up: the internet layer. This links the disparate hardware into a singular large internetwork.
The internet layer offers plenty of scope for injection of latency all of its own—and this isn't just a few milliseconds here and there for signals to move around the world. You can get seconds of latency without the packets of data going anywhere.
The culprit here is Moore's Law, the rule of thumb stating that transistor density doubles every 18 months or so. This doubling has the consequence that RAM halves in price—or becomes twice as large—every 18 months. While RAM was once a precious commodity, today it's dirt cheap. As a result, systems that once had just a few kilobytes of RAM are now blessed with copious megabytes.
Normally, this is a good thing. Sometimes, however, it's disastrous. A widespread problem with IP networks tends more to the disastrous end of the spectrum: bufferbloat.
Network traffic tends to be bursty. Click a link on a webpage and you'll do lots of traffic as your browser fetches the new page from the server, but then the connection will be idle for a while as you read the new page. Network infrastructure—routers, network cards, that kind of thing—all has to have a certain amount of buffering to temporarily hold packets before transmitting them to handle this bursty behavior and smooth over some of the peaks. The difficult part is getting those buffers the right size. A lot of the time, they're far, far too big.
That sounds counter-intuitive, since normally when it comes to memory, bigger means better. As a general rule, the network connection you have locally, whether wired or wireless, is a lot faster than your connection to the wider Internet. It's not too unusual to have gigabit local networking with just a megabit upstream bandwidth to the 'Net, a ratio of 1,000:1.
Thanks again to Moore's Law (making it ridiculously cheap to throw in some extra RAM), the DSL modem/router that joins the two networks might have several megabytes of buffer in it. Even a megabyte of buffer is a problem. Imagine you're uploading a 20MB video to YouTube, for example. A megabyte of buffer will fill in about eight milliseconds, because it's on the fast gigabit connection. But a megabyte of buffer will take eight seconds to actually upload to YouTube.
If the only traffic you cared about was your YouTube connection, this wouldn't be a big deal. But it normally isn't. Normally you'll leave that tediously slow upload to churn away in one tab while continuing to look at cat pictures in another tab. Here's where the problem bites you: each request you send for a new cat picture will get in the same buffer, at the back. It will have to wait for the megabyte of traffic in front of it to be uploaded before it can finally get onto the Internet and retrieve the latest Maru. Which means it has to wait eight seconds. Eight seconds in which your browser can do nothing bit twiddle its thumbs.
Eight seconds to load a webpage is bad; it's an utter disaster when you're trying to transmit VoIP voice traffic or Skype video.


text:
Videos for Grace Church
More stuff from "Grace Church"
311 Videos
13 Followers
1 Moderator
Heads up: the shoutbox will be retiring soon. It's tired of working, and can't wait to relax. You can still send a message to the channel owner, though!
Channels are a simple, beautiful way to showcase and watch videos. Browse more Channels.

subset: commoncrawl


text:
*Valid for purchases of at least 2499円, ends 07/10
14 hrs 30 min 42 sec
The perfect gift
Receive exclusive offers, find inspiration and discover the new arrivals. Enjoy 25% off prints the next time you shop.
Inspired. Affordable.
The product has been added to your cart
Here you'll find your saved products
Added to cart
Posterstore.co.uk uses cookies to give you the best experience on our website, as well as for marketing and analytical purposes. By clicking "Close and accept", you confirm that you have read our Cookie policy and agree to our use of cookies. If you do not want to agree, or want to read more about how we handle cookies, see our Cookie Policy.


text:
Honda XR250 L Muffler / Silencer
Suitable for: 2005 models
Muffler Model: MH258
Header Model: MH041
Gasket Model: MG4638
Clamp Model: MC49
High Quality mufflers / silencers from Musket Mufflers.
Not sure how to install the Honda XR250 L Muffler? Call Us: 06-754-7460 (New Zealand) or International: 0011-64-6-754-7460 (We are having problems with overseas callers getting through to us, if you experience problems please email us through our contact form).
We Ship Internationally!
Please contact us if you'd like to order this item.
We are open 9am - 5pm on Weekdays NZST (GMT +12). If you are calling after-hours, please leave your name, preferred mode of contact and a convenient time you'd like for us to call you back.
Otherwise, please send us an email with your muffler model number and brand. We'll be in touch as soon as possible!
Can't find your model?
Please contact us as we may be able to custom manufacture for your needs and our range is constantly changing!


text:
Perfect Pancake Recipes
Flavor pancakes with apple, fill them with cream cheese, add multigrain options — choose the recipe that suits your tastes!
Hearty Multigrain Pancakes
We added whole grains to these flapjacks to help ward off the morning munchies. Personalize this breakfast or brunch recipe with chocolate chips, blueberries and other stir-ins.
Lemon-Ricotta Hotcakes
When life gives you lemons, make the legendary lemon-ricotta hotcakes from Hell's Kitchen, a Minneapolis favorite.
Apple Pie Pancakes
Apple pie spice, apple juice and apples give these pancakes a triple dose of fruit. Both pancakes and maple syrup have a rich tradition in the Midwest, where winter and spring festivals celebrate the syrup harvest.
Whole-Grain Buttermilk Pancakes
Pile your breakfast plate high with our 100-percent-whole-wheat (yet still fluffy) buttermilk pancakes. Serve with syrup or jazz up with one of the quick and easy toppers in our recipe.
Lemon Ricotta Pancakes with Warm Blueberry Compote
Rise and shine with these special-occasion pancakes from Chicago chef Mindy Sega. Ricotta makes them moist and rich; lemon curd gives sweet-tart punch.
Finnish Baked Pancakes
This recipe comes from the Poplar Creek Guesthouse Bed and Breakfast on the Gunflint Trail near Grand Marais, Minnesota. The traditional big pancake has been adapted into a lighter version: puffed pancakes (recipe link abov). Poplar Creek also serves up a delicious Stuffed French Toast, flavored with cream cheese, apricot preserves and pecans.
Gingerbread Pancakes
Make a weekend breakfast extraordinary with a stack of these cakes featuring ginger, nutmeg, cinnamon, molasses and fresh-picked apples sliced paper-thin.
Chocolate Chip Pancakes with Raspberry Sauce
Kids will love helping make this breakfast or brunch treat, but don't save it just for them - adults like chocolate chip pancakes, too! The raspberry sauce can be made ahead of time.
Hint-of-Orange Pancakes with Grapefruit Syrup
This recipe couldn't be simpler! Just simmer grapefruit slices in maple syrup for a delicious, rosy compote to serve over waffles, French toast, crepes-or these subtly orange-flavored pancakes.
Mile-High Buttermilk Pancakes
These light-textured, melt-in-your-mouth hotcakes taste heavenly slathered with butter and dripping with syrup. The recipe comes from The Black & White restaurant in Little Falls, Minnesota.
Cream Cheese-Filled Breakfast Pancakes
Topped with fresh fruit and wrapped around a rich cream cheese filling, these crepelike pancakes add color and flavor to any special-occasion breakfast or brunch. The recipe comes from the Artists Colony Inn in Nashville, Indiana.
Peach Pancakes and Chai Syrup
Pureed canned peaches and whipping cream make a rich, flavorful pancake. Top with maple syrup instead of the chai syrup if you prefer. Add chopped peaches for even more fruit flavor.
Blueberry Buckwheat Pancakes
Made with buckwheat, a whole grain, these easy pancakes offer a low-fat, low-sodium breakfast or brunch alternative.
Four-Grain Pancakes
Whole-wheat flour, rolled oats, cornmeal and wheat germ give these buttermilk pancakes great flavor and texture.
Oatmeal Pancakes with Strawberry-Orange Sauce
Made with brown sugar and rolled oats, these pancakes taste almost like a soft oatmeal cookie. Top with either strawberry-orange sauce or maple syrup.
Snow-Season Pancakes
As the snow piles up outside Prairie Sky Guest and Game Ranch in Veblen, South Dakota, owner Corrine Prins heats up the griddle for her buttermilk pancakes that early risers can't resist. Teach your kids -- or grandkids -- to flip the flapjacks when you prepare this kid-favorite breakfast.


text:
The secret ingredient is love, kitchen towel embroidery, gingham buffalo plaid tartan machine embroidery designs valentine love saying quote
You will get only 1 design - The secret ingredient is love
1 design in 4 sizes
Sizes for hoops
4x4 and
5x7 recommended
Whole SET of 6 designs is here:
* * *
*ART- by request, please, contact me via email
* * *
JPG files Thread color-charts included
* * *
This is an embroidery file, it is a digital file. Not a patch. You must have an embroidery machine to use these designs.
* * *
INSTANT DOWNLOAD / designs are available for instant download
* * *
You can use this everywhere, your choice. You may stitch the design, and sell the finished item. You are not allowed to sell, share, give away or trade Artapli designs.
Your files will be available to download once payment is confirmed.
But please contact me if you have any problems with your order.
After download unzip the folder and transfer embroidery designs from your computer to your embroidery machine with USB, cable or card reader.
Most ZIP folder contain embroidery files in multiple sizes for embroidery hoops 4x4, 5x7, 6x10 and 8x12 and the following file formats: PES, DST, EXP, VIP, XXX, JEF, VP3, HUS, BX.
NOTE! in each listing description are marked exact sizes and file formats available.
If you're using WINDOWS:
Right click on the zip folder, then choose "Extract all.."
(remember where you save the files, so can easy find the files later on your PC)
If you're using MAC:
Double click the zip folder. Create a new folder, and move the zip into there. Then use terminal and the command line "unzip" command
All designs are commercially allowed to use. You may stitch design, and sell the finished item. You are not allowed to sell, share, give away or trade Artapli designs. All designs in the shop are worry-free, which means you may use them on your items for sale with confidence since all embroidery designs are unique and made by Artapli. As well as all alphabets.
Newsletter with free designs weekly, subscribe here:
According To each design and its size is created PDF or JPG file. So you may preview files on Android, iOS or on PC. Most PC already have the Adobe PDF software installed, in case you do not, this software is free here: www.adobe.com/reader/
PDF color-charts give total information about an embroidery design: size, stitch count, thread color changes, names, axes lines. PDF allows you to zoom in to the original size or print out, which is perfect to arrange the future design on the item to see how will look like the project.
Usually, it is allowed to enlarge or downsize embroidery designs by 10% maximum. The stitch count does not change, it means at downsizing stitches are just more packed together into a smaller area. At enlarging, stitches are spread out. Some software will allow you to process and designs can be resized and the stitches will automatically adjust. BUT not always they do good work. Any modified files may get mixed results, always do a sew-out on similar material. Please, contact me if you need any adjustments.
It is possible to convert files to ART format or change size, add or remove color, or any other modification by request and agreement.
* Sign in to Etsy.com and go to Your account.
* Go to Purchases and reviews.
* Next to the order, select Download Files. This goes to the Downloads page for all the files attached to your order.
There are generally no limits for when or how many times you can download a file. In most cases, you can access a file at any time on your Purchases page.
Please note: I reserve the right to change designs or remove items from my shop without notice. So, be sure to download your designs as soon as you purchase.
If you do not log in to your Etsy account and you checked out as a guest, the designs will not be available on your purchases page. You'll find a link to download your purchase in the receipt email that was sent to you after purchase.
If you can't seem to find your download notification email.
First, check your spam or junk inbox. If you use Gmail, also check your Social and Promotions tabs. If it's not there, add email@example.com to your address book or safe list.
For all complicated designs and ITH in-the-hoop embroidery projects are provided PDF instructions with a lot of photos.
My YouTube channel:


text:
Awards & Recognition
Whether awarded for a business achievement, academic accomplishment, athletic success, or civic or charitable contribution, everyone appreciates the recognition represented in an engraved plaque, custom trophy, or corporate gift.
Of course, you'll appreciate the wide selection and personalization potential of the many awards and recognition products at Allegra North York!
Don't overlook their value in building your business. Wall plaques and trophies, as well as acrylic, crystal, and glass awards, make for excellent individual employee appreciation items. And valued customers or loyal workers are prime candidates for corporate gifts.
With award plaques and trophies ready to be customized with your organization's logo, and individualized with the honoree's name and accomplishment, there's sure to be one at Allegra North York that perfectly matches the occasion … and your budget.


text:
Vertical Glide Out Slab Storage Rack For Quartz Stone Tile Display
|Metal,plastic,wood,mdf or Custom
|Black,white,grey etc or Custom
|Advertising, Display, Exhibition, Promotion for carpet
|Surface Treament:
|Polishing, Podwer Coating,Painting Etc or Custom
|Sample Cost:
|3 Times of Quotation
|Sample Time:
|7~10 days
|Production Time:
|20~30 days
|Use bubble pack,stretch film, strong export carton and,pallet packing.
We are serious and unremitting in making Slab Storage Rack,quartz stone Storage Rack,tile Slab Storage Rack,stone slab storage rack.
We will have new stone display racks on the shelves every month, and different styles and series of stone display racks will provide you with more choices.
|Product Name
|Vertical Glide Out Slab Storage Rack For Quartz Stone Tile Display
|Sample Dimenison
|On the picture/Customized According to the panels size
|White , Black , Silver , etc
|Metal, Hardwood, MDF,or Customized
|Acid Pickling, Baking Finish, Anti-rust Processed
|Logo Print
|As Per Customer's Request
|Exhibition, Showroom, Chain-store,shop
|Easy Disassembled for Delivery and Installation
|Support the OEM and ODM service
1.The display rack can display stone in a limited space,makes the space uses effectively.
2.Our display rack product with great durability and strengths.
3. Color: customer can choose their want .
4. The display rack can designed and make according to each customer's requirement.
Slab Storage Rack is mostly made by steel and metal material,which is special for stone products display purpose.
With the fashion design and competitive price, it is widely used for displaying marble, granite, quartz, craftstone, moasic samples.
It provides a better way for people to show the products to their customers.and help in promoting their business sales.
YIDU Industrial & Trading Co.,Ltd is a professional Sliding Tile Display Rack supplier for all kinds of stone display racks.Most of our products can be customized to your request.
How to custom your Tile Floor Display Stand?
Customizing your brand logo stone display racks is easy. Please follow below steps:
1. Firstly, we will listen you carefully and understand your needs.
2. Second, Tsianfan will provide you drawing before sample is made.
3. Third, We will follow your comments on the sample.
4. After the sample is approved, we will start production.
5. Before delivery, Hicon will assemble stone displays and check the quality.
6. We will contact you to make sure everything is OK after shipment.
Why choose YIDu?
We focus on custom Tile Floor Display Stand that attract shoppers, maintain an edge over competitors and increase the potential for sales.
We have worked for brand stone tile products supplier like Siltstone, Cambria, Caesar stone. We know how to show stones floor tiles in a unique way.
Dear Clients:
Please kindly share your Business Card with us when sending the inquiry, otherwise we are not able to send you any formal quotation.
Please trust us that we won't send you any unwanted Emails, and we will always keep your contact information confidential.
Thanks for your kind attention, we are now ready to bring you satisfactory.
Send Enquiry:


text:
Click the button below to add the PLANTRONICS, INC. 209745-104 BLACKWIRE,C3220 USB-A,BLACK to your wish list.
View All Products
We promise to never spam you, and just use your email address to identify you as a valid customer.
This product hasn't received any reviews yet. Be the first to review this product!
Write a review
Welcome to my Goods! Enjoy browsing our vast catalog of …
All prices are in USD.
Copyright 2022 My Goods.
Sitemap |
Ecommerce Solution by BigCommerce


text:
Summary Index Markets Research estimates that the Tableware Ceramic Decal market size will grow from xxx Million USD in 2020 to xxxx Million USD by 2025, and with a CAGR of xx%. The base year considered for this report is 2019, and the market forecast is projected from 2021 to 2025.
The global market report offers details on current and future growth trends pertaining to the business besides information on numerous regions across the geographical landscape of the Market. The report also expands on complete details regarding the supply and demand analysis, participation by major industry players and market share growth statistics of the business sphere. The sales and marketing channels of global market, traders, distributors and dealers of global Tableware Ceramic Decal market are evaluated completely. The market analysis is provided for the international markets that cover development trends, competitive landscape analysis, and key regions development status. It presents a deep analysis of the vendor landscape, offering a complete picture of current and future competitive scenarios of the market. Most of the data is demonstrated with charts, graphs, and practical figures, showing the status of the particular business on the worldwide and territorial stage. It highlights the latest trends, growth, new opportunities to feature an inclusive view of the global market.
The report has covered and analyzed the potential of the market and provides statistics and information on market size, shares and growth factors. The report intends to provide cutting-edge market intelligence and help decision makers take sound investment evaluation. Besides, the market report also identifies and analyses the emerging trends along with major drivers, challenges and opportunities. Additionally, the report also highlights market entry strategies for various companies. The objective of the report is to present a comprehensive assessment of the market and contains thoughtful insights, facts, historical data, industry-validated market data and projections with a suitable set of assumptions and methodology. The report also helps in understanding dynamics, structure by analyzing the market segments and, project the global market.
Key Reasons to shop for the report:
1 To induce a discriminating survey of have a big that means of the worldwide market and its comprehensive landscape
2 To grasp the foremost huge drives and restraint forces in its collision within the international market
3 To possess a summaries of market methods that are being applied by leading individual industries
4 To possess a comprehensive outlook and prospects for the market
5 To have the vital information of the market and their production.
6 To grasp the market earning, revenue, cost value of current and future market
Market Segment as follows:
Product Type Segmentation Includes Digital Decals Silkscreen Decal Others
Application Segmentation Includes Bowl Dish Spoon Others
Companies Includes Stecol Ceramic Crafts Tangshan Jiali Handan Ceramic Jiangsu Nanyang Concord Ceramics Leipold International Hi-Coat Tullis Russell Design Point Decal Tony Transfer Bel Decal Deco Art Yimei Bailey Siak Transfers Trinity Decals
Note: Sample report does not include any data or related information of the research study. It only showcase flow of information and different section covered. It is a paid report.
Note: Sample report does not include any data or related information of the research study. It only showcase flow of information and different section covered. It is a paid report.
Research Framework
Index Markets Research presents a detailed picture of the market by way of study, synthesis, and summation of data from multiple sources. The analysts have presented the various facets of the market with a particular focus on identifying the key industry influencers. The data thus presented is comprehensive, reliable, and the result of extensive research, both primary and secondary.
Information Sources
- Manufacturers and suppliers
- Channel partners
- Industry experts
- Strategic decision makers
Primary sources
- Industry journals and periodicals
- Government data
- Financial reports of key industry players
- Historical data
- Press releases
Secondary sources
Data Analysis
- Collation of data
- Estimation of key figures
- Analysis of derived insights
Data Synthesis
- Triangulation with data models
- Reference against proprietary databases
- Corroboration with industry experts
Data Validation
Report Writing
- Market drivers
- Market challenges
- Market trends
- Five forces analysis
- Market size and forecast
- Market segmentation
- Geographical insights
- Competitive landscape


text:
my variables now handled at run-time
use utf8, almost)
perldelta - what is new for perl v5.8.0
This document describes differences between the 5.6.0 release and the 5.8.0 release.
Many of the bug fixes in 5.8.0 were already seen in the 5.6.1 maintenance release since the two releases were kept closely coordinated (while 5.8.0 was still called 5.7.something).
Changes that were integrated into the 5.6.1 release are marked
Many of these changes have been further developed since 5.6.1 was released,
those are marked
You can see the list of changes in the 5.6.1 release (both from the 5.005_03 release and the 5.6.0 release) by reading perl561delta.
Perl 5.8 is not binary compatible with earlier releases of Perl.
You have to recompile your XS modules.
(Pure Perl modules should continue to work.)
The major reason for the discontinuity is the new IO architecture called PerlIO. PerlIO is the default configuration because without it many new features of Perl 5.8 cannot be used. In other words: you just have to recompile your modules containing XS code, sorry about that.
In future releases of Perl, non-PerlIO aware XS modules may become completely unsupported. This shouldn't be too difficult for module authors, however: PerlIO has been designed as a drop-in replacement (at the source code level) for the stdio interface.
Depending on your platform, there are also other reasons why we decided to break binary compatibility, please read on.
If your pointers are 64 bits wide, the Perl malloc is no longer being used because it does not work well with 8-byte pointers. Also, usually the system mallocs on such platforms are much better optimized for such large memory models than the Perl malloc. Some memory-hungry Perl applications like the PDL don't work well with Perl's malloc. Finally, other applications than Perl (such as mod_perl) tend to prefer the system malloc. Such platforms include Alpha and 64-bit HPPA, MIPS, PPC, and Sparc.
The AIX dynaloading now uses in AIX releases 4.3 and newer the native dlopen interface of AIX instead of the old emulated interface. This change will probably break backward compatibility with compiled modules. The change was made to make Perl more compliant with other applications like mod_perl which are using the AIX native interface.
my variables now handled at run-time
my EXPR : ATTRS syntax now applies variable attributes at
run-time. (Subroutine and
our variables still get attributes applied
at compile-time.) See attributes for additional details. In particular,
however, this allows variable attributes to be useful for
tie interfaces,
which was a deficiency of earlier releases. Note that the new semantics
doesn't work with the Attribute::Handlers module (as of version 0.76).
The Socket extension is now dynamically loaded instead of being statically built in. This may or may not be a problem with ancient TCP/IP stacks of VMS: we do not know since we weren't able to test Perl in such configurations.
Perl now uses IEEE format (T_FLOAT) as the default internal floating point format on OpenVMS Alpha, potentially breaking binary compatibility with external libraries or existing data. G_FLOAT is still available as a configuration option. The default on VAX (D_FLOAT) has not changed.
use utf8, almost)
Previously in Perl 5.6 to use Unicode one would say "use utf8" and then the operations (like string concatenation) were Unicode-aware in that lexical scope.
This was found to be an inconvenient interface, and in Perl 5.8 the Unicode model has completely changed: now the "Unicodeness" is bound to the data itself, and for most of the time "use utf8" is not needed at all. The only remaining use of "use utf8" is when the Perl script itself has been written in the UTF-8 encoding of Unicode. (UTF-8 has not been made the default since there are many Perl scripts out there that are using various national eight-bit character sets, which would be illegal in UTF-8.)
See perluniintro for the explanation of the current model, and utf8 for the current use of the utf8 pragma.
Unicode scripts are now supported. Scripts are similar to (and superior to) Unicode blocks. The difference between scripts and blocks is that scripts are the glyphs used by a language or a group of languages, while the blocks are more artificial groupings of (mostly) 256 characters based on the Unicode numbering.
In general, scripts are more inclusive, but not universally so. For
example, while the script
Latin includes all the Latin characters and
their various diacritic-adorned versions, it does not include the various
punctuation or digits (since they are not solely
A number of other properties are now supported, including
\p{Blank} [561] and
\p{SpacePerl} [561] (along with their
\P{...} versions, of course).
See perlunicode for details, and more additions.
In or
Is prefix to names used with the
\p{...} and
are now almost always optional. The only exception is that a
In prefix
is required to signify a Unicode block when a block name conflicts with a
script name. For example,
\p{Tibetan} refers to the script, while
\p{InTibetan} refers to the block. When there is no name conflict, you
can omit the
In from the block name (e.g.
\p{BraillePatterns}), but
to be safe, it's probably best to always use the
A reference to a reference now stringifies as "REF(0x81485ec)" instead of "SCALAR(0x81485ec)" in order to be more consistent with the return value of ref().
The undocumented pack/unpack template letters D/F have been recycled for better use: now they stand for long double (if supported by the platform) and NV (Perl internal floating point type). (They used to be aliases for d/f, but you never knew that.)
The list of filenames from glob() (or <...>) is now by default sorted alphabetically to be csh-compliant (which is what happened before in most UNIX platforms). (bsd_glob() does still sort platform natively, ASCII or EBCDIC, unless GLOB_ALPHASORT is specified.) [561]
CORE::dump(), but in future
releases the behaviour of an unqualified
dump() call may change.
\w character.
package; syntax (
package without an argument) has been
deprecated. Its semantics were never that clear and its
implementation even less so. If you have used that feature to
disallow all but fully qualified variables,
use strict; instead.
:raw "discipline" was the inverse of
Turning off "clrfness" is no longer enough to make a stream truly
binary. So the PerlIO
:raw layer (or "discipline", to use the Camel
book's older terminology) is now formally defined as being equivalent
to binmode(FH) - which is in turn defined as doing whatever is
necessary to pass each byte as-is without any translation. In
particular binmode(FH) - and hence
:raw - will now turn off both
CRLF and UTF-8 translation and remove other layers (e.g. :encoding())
which would modify byte stream.
fields pragma interface will remain
available. The restricted hashes interface is expected to
be the replacement interface (see Hash::Util). If your existing
programs depends on the underlying implementation, consider using
Class::PseudoHash from CPAN.
@a->[...] and
%h->{...} have now been deprecated.
Thread) is deprecated and expected
to be removed in Perl 5.10. Multithreaded code should be migrated to
the new ithreads model (see threads, threads::shared and
exec LIST and
system LIST operations now produce warnings on
tainted data and in some future release they will produce fatal errors.
Unicode in general should be now much more usable than in Perl 5.6.0 (or even in 5.6.1). Unicode can be used in hash keys, Unicode in regular expressions should work now, Unicode in tr/// should work now, Unicode in I/O should work now. See perluniintro for introduction and perlunicode for details.
The properties \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.)
See "New Unicode Properties" earlier in this document for additional information on changes with Unicode properties.
IO is now by default done via PerlIO rather than system's "stdio". PerlIO allows "layers" to be "pushed" onto a file handle to alter the handle's behaviour. Layers can be specified at open time via 3-arg form of open:
open($fh,'>:crlf :utf8', $path) || ...
or on already opened handles via extended
The built-in layers are: unix (low level read/write), stdio (as in previous Perls), perlio (re-implementation of stdio buffering in a portable manner), crlf (does CRLF <=> "\n" translation as on Win32, but available on any platform). A mmap layer may be available if platform supports it (mostly UNIXes).
Layers to be applied by default may be specified via the 'open' pragma.
See /"Installation and Configuration Improvements" for the effects of PerlIO on your architecture name.
If your platform supports fork(), you can use the list form of
for pipes. For example:
open KID_PS, "-|", "ps", "aux" or die $!;
forks the ps(1) command (without spawning a shell, as there are more
than three arguments to open()), and reads its standard output via the
KID_PS filehandle. See perlipc.
File handles can be marked as accepting Perl's internal encoding of Unicode (UTF-8 or UTF-EBCDIC depending on platform) by a pseudo layer ":utf8" :
Note for EBCDIC users: the pseudo layer ":utf8" is erroneously named for you since it's not UTF-8 what you will be getting but instead UTF-EBCDIC. See perlunicode, utf8, and http://www.unicode.org/unicode/reports/tr16/ for more information. In future releases this naming may change. See perluniintro for more information about UTF-8.
If your environment variables (LC_ALL, LC_CTYPE, LANG, LANGUAGE) look
like you want to use UTF-8 (any of the the variables match
your STDIN, STDOUT, STDERR handles and the default open layer
(see open) are marked as UTF-8. (This feature, like other new
features that combine Unicode and I/O, work only if you are using
PerlIO, but that's the default.)
Note that after this Perl really does assume that everything is UTF-8: for example if some input handle is not, Perl will probably very soon complain about the input data like this "Malformed UTF-8 ..." since any old eight-bit data is not legal UTF-8.
Note for code authors: if you want to enable your users to use UTF-8
as their default encoding but in your code still have eight-bit I/O streams
(such as images or zip files), you need to explicitly open() or binmode()
:bytes (see perlfunc/open and perlfunc/binmode), or you
can just use
binmode(FH) (nice for pre-5.8.0 backward compatibility).
File handles can be opened to "in memory" files held in Perl scalars via:
open($fh,'>', \$variable) || ...
Anonymous temporary files are available without need to 'use FileHandle' or other module via
open($fh,"+>", undef) || ...
That is a literal undef, not an undefined value.
The new interpreter threads ("ithreads" for short) implementation of multithreading, by Arthur Bergman, replaces the old "5.005 threads" implementation. In the ithreads model any data sharing between threads must be explicit, as opposed to the model where data sharing was implicit. See threads and threads::shared, and perlthrtut.
As a part of the ithreads implementation Perl will also use any necessary and detectable reentrant libc interfaces.
A restricted hash is restricted to a certain set of keys, no keys outside the set can be added. Also individual keys can be restricted so that the key cannot be deleted and the value cannot be changed. No new syntax is involved: the Hash::Util module is the interface.
Perl used to be fragile in that signals arriving at inopportune moments could corrupt Perl's internal state. Now Perl postpones handling of signals until it's safe (between opcodes).
This change may have surprising side effects because signals no longer interrupt Perl instantly. Perl will now first finish whatever it was doing, like finishing an internal operation (like sort()) or an external operation (like an I/O operation), and only then look at any arrived signals (and before starting the next operation). No more corrupt internal state since the current operation is always finished first, but the signal may take more time to get heard. Note that breaking out from potentially blocking operations should still work, though.
In general a lot of fixing has happened in the area of Perl's
understanding of numbers, both integer and floating point. Since in
many systems the standard number parsing functions like
atof() seem to have bugs, Perl tries to work around their
deficiencies. This results hopefully in more accurate numbers.
Perl now tries internally to use integer values in numeric conversions and basic arithmetics (+ - * /) if the arguments are integers, and tries also to keep the results stored internally as integers. This change leads to often slightly faster and always less lossy arithmetics. (Previously Perl always preferred floating point numbers in its math.)
In double-quoted strings, arrays now interpolate, no matter what. The behavior in earlier versions of perl 5 was that arrays would interpolate into strings if the array had been mentioned before the string was compiled, and otherwise Perl would raise a fatal compile-time error. In versions 5.000 through 5.003, the error was
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
"fred\@example.com" when they wanted a literal
@ sign, just as
they have always written
"Give me back my \$5" when they wanted a
$ 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
"firstname.lastname@example.com" is going to turn into
fred.com if you don't backslash the
See http://www.plover.com/~mjd/perl/at-error.html for more details
about the history here.
The $Config{byteorder} (and corresponding BYTEORDER in config.h) was previously wrong in platforms if sizeof(long) was 4, but sizeof(IV) was 8. The byteorder was only sizeof(long) bytes long (1234 or 4321), but now it is correctly sizeof(IV) bytes long, (12345678 or 87654321). (This problem didn't affect Windows platforms.)
Also, $Config{byteorder} is now computed dynamically--this is more robust with "fat binaries" where an executable image contains binaries for more than one binary platform, and when cross-compiling.
perl -d:Module=arg,arg,arg now works (previously one couldn't pass
in multiple arguments.)
do followed by a bareword now ensures that this bareword isn't
a keyword (to avoid a bug where
do q(foo.pl) tried to call a
subroutine called
q). This means that for example instead of
do format() you must write
do &format().
dump() better written as CORE::dump(),
meaning that by default
dump(...) is resolved as the builtin
dump() which dumps core and aborts, not as (possibly) user-defined
sub dump. To call the latter, qualify the call as
(The whole dump() feature is to considered deprecated, and possibly
removed/changed in future releases.)
prototype("CORE::chomp") is undefined,
because it cannot be expressed and therefore one cannot really write
replacements to override these builtins.
undef in list context. However,
the lvalue subroutine feature still remains experimental. [561+]
$^N, which contains the most-recently closed group (submatch).
no Module; does not produce an error even if Module does not have an
unimport() method. This parallels the behavior of
use vis-a-vis
import. [561]
undef if either operand
is a NaN. Previously the behaviour was unspecified.
our can now have an experimental optional attribute
unique that
affects how global variables are shared among multiple interpreters,
see perlfunc/our.
pack() / unpack() can now group template letters with
() and then
apply repetition/count modifiers on the groups.
pack() / unpack() can now process the Perl internal numeric types:
IVs, UVs, NVs-- and also long doubles, if supported by the platform.
The template letters are
F, and
pack('U0a*', ...) can now be used to force a string to UTF8.
The printf() and sprintf() now support parameter reordering using the
%\d+\$ and
*\d+\$ syntaxes. For example
print "%2\$s %1\$s\n", "foo", "bar";
will print "bar foo\n". This feature helps in writing internationalised software, and in general when the order of the parameters can vary.
-t is available. It is the
little brother of
-T: instead of dying on taint violations,
lexical warnings are given. This is only meant as a temporary
debugging aid while securing the code of old legacy applications.
This is not a substitute for -T.
exec LIST and
system LIST have now been
considered too risky (think
exec @ARGV: it can start any program
with any arguments), and now the said forms cause a warning under
lexical warnings. You should carefully launder the arguments to
guarantee their validity. In future releases of Perl the forms will
become fatal errors so consider starting laundering now.
utime undef, undef, @files to change the
file timestamps to the current time.
${^TAINT}, indicates whether taint mode is enabled.
Use of the
/c match modifier without an accompanying
/g modifier
elicits a new warning:
Use of /c modifier is meaningless without /g.
Use of
/c in substitutions, even with
/g, elicits
Use of /c modifier is meaningless in s///.
Use of
/g with
split elicits
Use of /g modifier is meaningless
in split.
Support for the
CLONE special subroutine had been added.
With ithreads, when a new thread is created, all Perl data is cloned,
however non-Perl data cannot be cloned automatically. In
CLONE you
can do whatever you need to do, like for example handle the cloning of
non-Perl data, if necessary.
CLONE will be executed once for every
package that has it defined or inherited. It will be called in the
context of the new thread, so all modifications are made in the new area.
See perlmod
Attribute::Handlers, originally by Damian Conway and now maintained
by Arthur Bergman, allows a class to define attribute handlers.
package MyPack; use Attribute::Handlers; sub Wolf :ATTR(SCALAR) { print "howl!\n" }
# later, in some package using or inheriting from MyPack...
my MyPack $Fluffy : Wolf; # the attribute handler Wolf will be called
Both variables and routines can have attribute handlers. Handlers can be specific to type (SCALAR, ARRAY, HASH, or CODE), or specific to the exact compilation phase (BEGIN, CHECK, INIT, or END). See Attribute::Handlers.
B::Concise, by Stephen McCamant, is a new compiler backend for
walking the Perl syntax tree, printing concise info about ops.
The output is highly customisable. See B::Concise. [561+]
Class::ISA, by Sean Burke, is a module for reporting the search
path for a class's ISA tree. See Class::ISA.
Cwd now has a split personality: if possible, an XS extension is
used, (this will hopefully be faster, more secure, and more robust)
but if not possible, the familiar Perl implementation is used.
Devel::PPPort, originally by Kenneth Albanowski and now
maintained by Paul Marquess, has been added. It is primarily used
h2xs to enhance portability of XS modules between different
versions of Perl. See Devel::PPPort.
Digest, frontend module for calculating digests (checksums), from
Gisle Aas, has been added. See Digest.
Digest::MD5 for calculating MD5 digests (checksums) as defined in
RFC 1321, from Gisle Aas, has been added. See Digest::MD5.
use Digest::MD5 'md5_hex';
$digest = md5_hex("Thirsty Camel");
print $digest, "\n"; # 01d19d9d2045e005c3f1b80e8b164de1
NOTE: the
MD5 backward compatibility module is deliberately not
included since its further use is discouraged.
See also PerlIO::via::QuotedPrint.
Encode, originally by Nick Ing-Simmons and now maintained by Dan
Kogai, provides a mechanism to translate between different character
encodings. Support for Unicode, ISO-8859-1, and ASCII are compiled in
to the module. Several other encodings (like the rest of the
ISO-8859, CP*/Win*, Mac, KOI8-R, three variants EBCDIC, Chinese,
Japanese, and Korean encodings) are included and can be loaded at
runtime. (For space considerations, the largest Chinese encodings
have been separated into their own CPAN module, Encode::HanExtra,
which Encode will use if available). See Encode.
Any encoding supported by Encode module is also available to the ":encoding()" layer if PerlIO is used.
Hash::Util is the interface to the new restricted hashes
feature. (Implemented by Jeffrey Friedl, Nick Ing-Simmons, and
Michael Schwern.) See Hash::Util.
I18N::Langinfo can be used to query locale information.
See I18N::Langinfo.
I18N::LangTags, by Sean Burke, has functions for dealing with
RFC3066-style language tags. See I18N::LangTags.
ExtUtils::Constant, by Nicholas Clark, is a new tool for extension
writers for generating XS code to import C header constants.
See ExtUtils::Constant.
Filter::Simple, by Damian Conway, is an easy-to-use frontend to
Filter::Util::Call. See Filter::Simple.
# in MyFilter.pm:
package MyFilter;
use Filter::Simple sub { while (my ($from, $to) = splice @_, 0, 2) { s/$from/$to/g; } };
# in user's code:
use MyFilter qr/red/ => 'green';
print "red\n"; # this code is filtered, will print "green\n" print "bored\n"; # this code is filtered, will print "bogreen\n"
no MyFilter;
print "red\n"; # this code is not filtered, will print "red\n"
File::Temp, by Tim Jenness, allows one to create temporary files
and directories in an easy, portable, and secure way. See File::Temp.
Filter::Util::Call, by Paul Marquess, provides you with the
framework to write source filters in Perl. For most uses, the
frontend Filter::Simple is to be preferred. See Filter::Util::Call.
if, by Ilya Zakharevich, is a new pragma for conditional inclusion
of modules.
libnet, by Graham Barr, is a collection of perl5 modules related to network programming. See Net::FTP, Net::NNTP, Net::Ping (not part of libnet, but related), Net::POP3, Net::SMTP, and Net::Time.
Perl installation leaves libnet unconfigured; use libnetcfg to configure it.
List::Util, by Graham Barr, is a selection of general-utility
list subroutines, such as sum(), min(), first(), and shuffle().
See List::Util.
Locale::Language, and Locale::Script, by Neil Bowers, have
been added. They provide the codes for various locale standards, such
as "fr" for France, "usd" for US Dollar, and "ja" for Japanese.
use Locale::Country;
$country = code2country('jp'); # $country gets 'Japan' $code = country2code('Norway'); # $code gets 'no'
See Locale::Constants, Locale::Country, Locale::Currency, and Locale::Language.
Locale::Maketext, by Sean Burke, is a localization framework. See
Locale::Maketext, and Locale::Maketext::TPJ13. The latter is an
article about software localization, originally published in The Perl
Journal #13, and republished here with kind permission.
Math::BigRat for big rational numbers, to accompany Math::BigInt and
Math::BigFloat, from Tels. See Math::BigRat.
Memoize can make your functions faster by trading space for time,
from Mark-Jason Dominus. See Memoize.
MIME::Base64, by Gisle Aas, allows you to encode data in base64,
as defined in RFC 2045 - MIME (Multipurpose Internet Mail
use MIME::Base64;
$encoded = encode_base64('Aladdin:open sesame'); $decoded = decode_base64($encoded);
print $encoded, "\n"; # "QWxhZGRpbjpvcGVuIHNlc2FtZQ=="
See MIME::Base64.
MIME::QuotedPrint, by Gisle Aas, allows you to encode data
in quoted-printable encoding, as defined in RFC 2045 - MIME
(Multipurpose Internet Mail Extensions).
use MIME::QuotedPrint;
$encoded = encode_qp("Smiley in Unicode: \x{263a}"); $decoded = decode_qp($encoded);
print $encoded, "\n"; # "Smiley in Unicode: =263A"
See also PerlIO::via::QuotedPrint.
NEXT, by Damian Conway, is a pseudo-class for method redispatch.
See NEXT.
open is a new pragma for setting the default I/O layers
for open().
PerlIO::scalar, by Nick Ing-Simmons, provides the implementation
of IO to "in memory" Perl scalars as discussed above. It also serves
as an example of a loadable PerlIO layer. Other future possibilities
include PerlIO::Array and PerlIO::Code. See PerlIO::scalar.
PerlIO::via, by Nick Ing-Simmons, acts as a PerlIO layer and wraps
PerlIO layer functionality provided by a class (typically implemented
in Perl code).
PerlIO::via::QuotedPrint, by Elizabeth Mattijsen, is an example
of a
PerlIO::via class:
use PerlIO::via::QuotedPrint; open($fh,">:via(QuotedPrint)",$path);
This will automatically convert everything output to
$fh to
Quoted-Printable. See PerlIO::via and PerlIO::via::QuotedPrint.
Pod::ParseLink, by Russ Allbery, has been added,
to parse L<> links in pods as described in the new
Pod::Text::Overstrike, by Joe Smith, has been added.
It converts POD data to formatted overstrike text.
See Pod::Text::Overstrike. [561+]
Scalar::Util is a selection of general-utility scalar subroutines,
such as blessed(), reftype(), and tainted(). See Scalar::Util.
sort is a new pragma for controlling the behaviour of sort().
Storable gives persistence to Perl data structures by allowing the
storage and retrieval of Perl data to and from files in a fast and
compact binary format. Because in effect Storable does serialisation
of Perl data structures, with it you can also clone deep, hierarchical
datastructures. Storable was originally created by Raphael Manfredi,
but it is now maintained by Abhijit Menon-Sen. Storable has been
enhanced to understand the two new hash features, Unicode keys and
restricted hashes. See Storable.
Switch, by Damian Conway, has been added. Just by saying
use Switch;
you have
switch and
case available in Perl.
use Switch;
switch ($val) {
case 1 { print "number 1" } case "a" { print "string a" } case [1..10,42] { print "number in list" } case (@array) { print "number in list" } case /\w+/ { print "pattern" } case qr/\w+/ { print "pattern" } case (%hash) { print "entry in hash" } case (\%hash) { print "entry in hash" } case (\&sub) { print "arg to subroutine" } else { print "previous case not true" } }
See Switch.
Test::More, by Michael Schwern, is yet another framework for writing
test scripts, more extensive than Test::Simple. See Test::More.
Test::Simple, by Michael Schwern, has basic utilities for writing
tests. See Test::Simple.
Text::Balanced, by Damian Conway, has been added, for extracting
delimited text sequences from strings.
use Text::Balanced 'extract_delimited';
($a, $b) = extract_delimited("'never say never', he never said", "'", '');
$a will be "'never say never'", $b will be ', he never said'.
In addition to extract_delimited(), there are also extract_bracketed(), extract_quotelike(), extract_codeblock(), extract_variable(), extract_tagged(), extract_multiple(), gen_delimited_pat(), and gen_extract_tagged(). With these, you can implement rather advanced parsing algorithms. See Text::Balanced.
threads, by Arthur Bergman, is an interface to interpreter threads.
Interpreter threads (ithreads) is the new thread model introduced in
Perl 5.6 but only available as an internal interface for extension
writers (and for Win32 Perl for
fork() emulation). See threads,
threads::shared, and perlthrtut.
threads::shared, by Arthur Bergman, allows data sharing for
interpreter threads. See threads::shared.
Tie::File, by Mark-Jason Dominus, associates a Perl array with the
lines of a file. See Tie::File.
Tie::Memoize, by Ilya Zakharevich, provides on-demand loaded hashes.
See Tie::Memoize.
Tie::RefHash::Nestable, by Edward Avis, allows storing hash
references (unlike the standard Tie::RefHash) The module is contained
within Tie::RefHash. See Tie::RefHash.
Time::HiRes, by Douglas E. Wegscheid, provides high resolution
timing (ualarm, usleep, and gettimeofday). See Time::HiRes.
Unicode::UCD offers a querying interface to the Unicode Character
Database. See Unicode::UCD.
Unicode::Collate, by SADAHIRO Tomoyuki, implements the UCA
(Unicode Collation Algorithm) for sorting Unicode strings.
See Unicode::Collate.
Unicode::Normalize, by SADAHIRO Tomoyuki, implements the various
Unicode normalization forms. See Unicode::Normalize.
XS::APItest, by Tim Jenness, is a test extension that exercises XS
APIs. Currently only
printf() is tested: how to output various
basic data types from XS.
XS::Typemap, by Tim Jenness, is a test extension that exercises
XS typemaps. Nothing gets installed, but the code is worth studying
for extension writers.
no AutoLoader;.
The English module can now be used without the infamous performance hit by saying
use English '-no_match_vars';
(Assuming, of course, that you don't need the troublesome variables
$&, or
$'.) Also, introduced
@LAST_MATCH_START and
@LAST_MATCH_END English aliases for
@- and
use/no warnings 'File::Find';.
GLOB_LIMIT constant to limit the size of
the returned list of filenames.
(usually meaning that the operating system will make one up.)
Net::Ping has been considerably enhanced by Rob Brown: multihoming is now supported, Win32 functionality is better, there is now time measuring functionality (optionally high-resolution using Time::HiRes), and there is now "external" protocol which uses Net::Ping::External module which runs your external ping utility and parses the output. A version of Net::Ping::External is available in CPAN.
Note that some of the Net::Ping tests are disabled when running under the Perl distribution since one cannot assume one or more of the following: enabled echo port at localhost, full Internet connectivity, or sympathetic firewalls. You can set the environment variable PERL_TEST_Net_Ping to "1" (one) before running the Perl test suite to enable all the Net::Ping tests.
%INC is now localised in a Safe compartment so that
use/require work.
our() does not and will not support.)
utf8:: name space (as in the pragma) provides various
Perl-callable functions to provide low level access to Perl's
internal Unicode representation. At the moment only length()
has been implemented.
enc2xs is a tool for people adding their own encodings to the
Encode module.
h2ph now supports C trigraphs.
h2xs now produces a template README.
h2xs now uses
Devel::PPPort for better portability between
different versions of Perl.
h2xs uses the new ExtUtils::Constant module
which will affect newly created extensions that define constants.
Since the new code is more correct (if you have two constants where the
first one is a prefix of the second one, the first constant never
got defined), less lossy (it uses integers for integer constant,
as opposed to the old code that used floating point numbers even for
integer constants), and slightly faster, you might want to consider
regenerating your extension code (the new scheme makes regenerating
easy). h2xs now also supports C trigraphs.
libnetcfg has been added to configure libnet.
perlbug is now much more robust. It also sends the bug report to
perl.org, not perl.com.
perlcc has been rewritten and its user interface (that is,
command line) is much more like that of the UNIX C compiler, cc.
(The perlbc tools has been removed. Use
perlcc -B instead.)
Note that perlcc is still considered very experimental and
unsupported. [561]
perlivp is a new Installation Verification Procedure utility
for running any time after installing Perl.
piconv is an implementation of the character conversion utility
iconv, demonstrating the new Encode module.
pod2html now allows specifying a cache directory.
pod2html now produces XHTML 1.0.
pod2html now understands POD written using different line endings
(PC-like CRLF versus UNIX-like LF versus MacClassic-like CR).
s2p has been completely rewritten in Perl. (It is in fact a full
implementation of sed in Perl: you can use the sed functionality by
using the
psed utility.)
xsubpp now understands POD documentation embedded in the *.xs
files. [561]
xsubpp now supports the OUT keyword.
The following platform-specific documents are available before the installation as README.platform, and after the installation as perlplatform:
perlaix perlamiga perlapollo perlbeos perlbs2000 perlce perlcygwin perldgux perldos perlepoc perlfreebsd perlhpux perlhurd perlirix perlmachten perlmacos perlmint perlmpeix perlnetware perlos2 perlos390 perlplan9 perlqnx perlsolaris perltru64 perluts perlvmesa perlvms perlvos perlwin32
These documents usually detail one or more of the following subjects: configuring, building, testing, installing, and sometimes also using Perl on the said platform.
Eastern Asian Perl users are now welcomed in their own languages: README.jp (Japanese), README.ko (Korean), README.cn (simplified Chinese) and README.tw (traditional Chinese), which are written in normal pod but encoded in EUC-JP, EUC-KR, EUC-CN and Big5. These will get installed as
perljp perlko perlcn perltw
sort() has been changed to use primarily mergesort internally as
opposed to the earlier quicksort. For very small lists this may
result in slightly slower sorting times, but in general the speedup
should be at least 20%. Additional bonuses are that the worst case
behaviour of sort() is now better (in computer science terms it now
runs in time O(N log N), as opposed to quicksort's Theta(N**2)
worst-case run time behaviour), and that sort() is now stable
(meaning that elements with identical keys will stay ordered as they
were before the sort). See the
sort pragma for information.
The story in more detail: suppose you want to serve yourself a little slice of Pi.
@digits = ( 3,1,4,1,5,9 );
A numerical sort of the digits will yield (1,1,3,4,5,9), as expected.
1 comes first is hard to know, since one
1 looks pretty
much like any other. You can regard this as totally trivial,
or somewhat profound. However, if you just want to sort the even
digits ahead of the odd ones, then what will
sort { ($a % 2) <=> ($b % 2) } @digits;
yield? The only even digit,
4, will come first. But how about
the odd numbers, which all compare equal? With the quicksort algorithm
used to implement Perl 5.6 and earlier, the order of ties is left up
to the sort. So, as you add more and more digits of Pi, the order
in which the sorted even and odd digits appear will change.
and, for sufficiently large slices of Pi, the quicksort algorithm
in Perl 5.8 won't return the same results even if reinvoked with the
same input. The justification for this rests with quicksort's
worst case behavior. If you run
sort { $a <=> $b } ( 1 .. $N , 1 .. $N );
(something you might approximate if you wanted to merge two sorted arrays using sort), doubling $N doesn't just double the quicksort time, it quadruples it. Quicksort has a worst case run time that can grow like N**2, so-called quadratic behaviour, and it can happen on patterns that may well arise in normal use. You won't notice this for small arrays, but you will notice it with larger arrays, and you may not live long enough for the sort to complete on arrays of a million elements. So the 5.8 quicksort scrambles large arrays before sorting them, as a statistical defence against quadratic behaviour. But that means if you sort the same large array twice, ties may be broken in different ways.
Because of the unpredictability of tie-breaking order, and the quadratic worst-case behaviour, quicksort was almost replaced completely with a stable mergesort. Stable means that ties are broken to preserve the original order of appearance in the input array. So
sort { ($a % 2) <=> ($b % 2) } (3,1,4,1,5,9);
will yield (4,3,1,1,5,9), guaranteed. The even and odd numbers appear in the output in the same order they appeared in the input. Mergesort has worst case O(N log N) behaviour, the best value attainable. And, ironically, this mergesort does particularly well where quicksort goes quadratic: mergesort sorts (1..$N, 1..$N) in O(N) time. But quicksort was rescued at the last moment because it is faster than mergesort on certain inputs and platforms. For example, if you really don't care about the order of even and odd digits, quicksort will run in O(N) time; it's very good at sorting many repetitions of a small number of distinct elements. The quicksort divide and conquer strategy works well on platforms with relatively small, very fast, caches. Eventually, the problem gets whittled down to one that fits in the cache, from which point it benefits from the increased memory speed.
Quicksort was rescued by implementing a sort pragma to control aspects
of the sort. The stable subpragma forces stable behaviour,
regardless of algorithm. The _quicksort and _mergesort
subpragmas are heavy-handed ways to select the underlying implementation.
The leading
_ is a reminder that these subpragmas may not survive
beyond 5.8. More appropriate mechanisms for selecting the implementation
exist, but they wouldn't have arrived in time to save quicksort.
-S can now run non-interactively. [561]
@Config{qw(db_version_major db_version_minor db_version_patch)}
from Perl and as
DB_VERSION_PATCH_CFG from C.
If your file system supports symbolic links, you can build Perl outside of the source directory by
mkdir /tmp/perl/build/directory cd /tmp/perl/build/directory sh /path/to/perl/source/Configure -Dmksymlinks ...
This will create in /tmp/perl/build/directory a tree of symbolic links pointing to files in /path/to/perl/source. The original files are left unaffected. After Configure has finished, you can just say
make all test
and Perl will be built and tested, all in /tmp/perl/build/directory. [561]
For Perl developers, several new make targets for profiling and debugging have been added; see perlhack.
The Thread extension is now not built at all under ithreads
Configure -Duseithreads) because it wouldn't work anyway (the
Thread extension requires being Configured with
Note that the 5.005 threads are unsupported and deprecated: if you have code written for the old threads you should migrate it to the new ithreads model.
The obsolete method of making a special (e.g., debugging) flavor of perl by saying
make LIBPERL=libperld.a
has been removed. Use -DDEBUGGING instead.
For the list of platforms known to support Perl, see perlport/"Supported Platforms".
Numerous memory leaks and uninitialized memory accesses have been hunted down. Most importantly, anonymous subs used to leak quite a bit. [561]
(unknown) for subroutines that have
been removed from the symbol table.
"0" now treated correctly, the
d command now checks
line number,
$. no longer gets corrupted, and all debugger output
now goes correctly to the socket if RemotePort is set. [561]
The debugger (perl5db.pl) has been modified to present a more consistent commands interface, via (CommandSet=580). perl5db.t was also added to test the changes, and as a placeholder for further tests.
See perldebug.
dumpDepth option to control the maximum
depth to which nested structures are dumped. The
x command has
been extended so that
x N EXPR dumps out the value of EXPR to a
depth of at most N levels.
*foo{FORMAT} now works.
eval "...".
use warnings qw(FATAL all) did not work as intended. This has been
corrected. [561]
#line now works. [561]
Localised tied variables no longer leak memory
use Tie::Hash; tie my %tied_hash => 'Tie::StdHash';
# Used to leak memory every time local() was called; # in a loop, this added up. local($tied_hash{Foo}) = 1;
Localised hash elements (and %ENV) are correctly unlocalised to not exist, if they didn't before they were localised.
use Tie::Hash; tie my %tied_hash => 'Tie::StdHash';
# Nothing has set the FOO element so far
{ local $tied_hash{FOO} = 'Bar' }
# This used to print, but not now. print "exists!\n" if exists $tied_hash{FOO};
As a side effect of this fix, tied hash interfaces must define the EXISTS and DELETE methods.
-Duselongdouble. This version of Perl detects this brokenness
and has a workaround for it. The glibc release 2.2.2 is known to have
fixed the modfl() bug.
qw(a\\b) now parses correctly as
'a\\b': that is, as three
characters, not four. [561]
[[:space:]] to include the (very
rarely used) vertical tab character. Added a new POSIX-ish character
[[:blank:]] which stands for horizontal whitespace
(currently, the space and the tab).
use re 'debug'
or via
-Dr) now looks better. [561]
"a\nxb\n" =~ /(?!\A)x/m were flawed. The
bug has been fixed. [561]
${$num}) was accidentally disabled. This works
again now. [561]
LOG_AUTH constant.
STDERR is tied, warnings caused by
warn and
die now
correctly pass to it.
Several Unicode fixes.
IsAlpha, and
IsWord now match titlecase.
. operator or via variable interpolation,
quotemeta, the
x operator,
substitution with
s///, single-quoted UTF8, should now work.
tr/// operator now works. Note that the
functionality has been removed (but see pack('U0', ...)).
eval "v200" now works.
Perl now works on post-4.0 BSD/OSes.
All BSDs
$0 now works (as much as possible; see perlvar for details).
Numerous updates; currently synchronised with Cygwin 1.3.10.
EPOC now better supported. See README.epoc. [561]
FreeBSD 3.*
Perl now works on post-3.0 FreeBSDs.
README.hpux updated;
Configure -Duse64bitall now works;
now uses HP-UX malloc instead of Perl malloc.
Numerous compilation flag and hint enhancements; accidental mixing of 32-bit and 64-bit libraries (a doomed attempt) made much harder.
Mac OS Classic
Compilation of the standard Perl distribution in Mac OS Classic should now work if you have the Metrowerks development environment and the missing Mac-specific toolkit bits. Contact the macperl mailing list for details.
MPE/iX update after Perl 5.6.0. See README.mpeix. [561]
Perl now works on NetBSD/sparc.
Now works with usethreads (see INSTALL). [561]
64-bitness using the Sun Workshop compiler now works.
Stratus VOS
The native build method requires at least VOS Release 14.5.0 and GNU C++/GNU Tools 2.0.1 or later. The Perl pack function now maps overflowed values to +infinity and underflowed values to -infinity.
Tru64 (aka Digital UNIX, aka DEC OSF/1)
The operating system version letter now recorded in $Config{osvers}. Allow compiling with gcc (previously explicitly forbidden). Compiling with gcc still not recommended because buggy code results, even with gcc 2.95.2.
Fixed various alignment problems that lead into core dumps either during build or later; no longer dies on math errors at runtime; now using full quad integers (64 bits), previously was using only 46 bit integers for speed.
See /"Socket Extension Dynamic in VMS" and /"IEEE-format Floating Point Default on OpenVMS Alpha" for important changes not otherwise listed here.
chdir() now works better despite a CRT bug; now works with MULTIPLICITY (see INSTALL); now works with Perl's malloc.
The tainting of
%ENV elements via
keys or
values was previously
unimplemented. It now works as documented.
waitpid emulation has been improved. The worst bug (now fixed)
was that a pid of -1 would cause a wildcard search of all processes on
the system.
POSIX-style signals are now emulated much better on VMS versions prior to 7.0.
system function and backticks operator have improved
functionality and better error handling. [561]
File access tests now use current process privileges rather than the user's default privileges, which could sometimes result in a mismatch between reported access and actual access. This improvement is only available on VMS v6.0 and later.
There is a new
kill implementation based on
sys$sigprc that allows
older VMS systems (pre-7.0) to use
kill to send signals rather than
simply force exit. This implementation also allows later systems to
kill from within a signal handler.
Iterative logical name translations are now limited to 10 iterations in imitation of SHOW LOGICAL and other OpenVMS facilities.
The following modules now work on Windows:
ExtUtils::Embed [561] IO::Pipe IO::Poll Net::Ping
waitpid($pid, &POSIX::WNOHANG).
The behavior of system() with multiple arguments has been rationalized.
Each unquoted argument will be automatically quoted to protect whitespace,
and any existing whitespace in the arguments will be preserved. This
improves the portability of system(@args) by avoiding the need for
cmd shell specific quoting in perl programs.
Note that this means that some scripts that may have relied on earlier
buggy behavior may no longer work correctly. For example,
system("nmake /nologo", @args) will now attempt to run the file
nmake /nologo and will fail when such a file isn't found.
On the other hand, perl will now execute code such as
system("c:/Program Files/MyApp/foo.exe", @args) correctly.
File::Spec->tmpdir() now prefers C:/temp over /tmp
(works better when perl is running as service).
Please see perldiag for more details.
\9, and
\_. There is no need to escape any of the
\w characters.
<-- HERE marker.
-M and
-m options now warn if you didn't supply the module name.
use specify a required minimum version, modules matching
the name and but not defining a $VERSION will cause a fatal failure.
main:: prefix for filehandles in the
main package,
for example
STDIN instead of
push @a; and
unshift @a; (with no values to push or unshift)
now give a warning. This may be a problem for generated and evaled
"C" format you will get an optional warning. Similarly
for the
"c" format and a number less than -128 or more than 127.
P format now demands an explicit size.
w now warns of unterminated compressed integers.
(?o) make sense only if applied to
the entire regex. You will get an optional warning if you try to do
has been deprecated for a while. Now you will get an optional warning.
sort in scalar context now issues an optional warning.
This didn't do anything useful, as the sort was not performed.
make -f Makefile.micro should be enough. Beware: microperl makes
many assumptions, some of which may be too bold; the resulting
executable may crash or otherwise misbehave in wondrous ways.
For careful hackers only.
'P') have been macrofied
PERL_MAGIC_TIED) for better source code readability
and maintainability.
offsets member of the
struct regexp. See perldebguts for more
complete information.
gcc -Wall clean. Some warning
messages still remain in some platforms, so if you are compiling with
gcc you may see some warnings about dubious practices. The warnings
are being worked on.
(This change was already made in 5.7.0 but bears repeating here.) (5.7.0 came out before 5.6.1: the development branch 5.7 released earlier than the maintenance branch 5.6)
A potential security vulnerability in the optional suidperl component of Perl was identified in August 2000. suidperl is neither built nor installed by default. As of November 2001 the only known vulnerable platform is Linux, most likely all Linux distributions. CERT and various vendors and distributors have been alerted about the vulnerability. See http://www.cpan.org/src/5.0/sperl-2000-08-05/sperl-2000-08-05.txt for more information.
The problem was caused by Perl trying to report a suspected security exploit attempt using an external program, /bin/mail. On Linux platforms the /bin/mail program had an undocumented feature which when combined with suidperl gave access to a root shell, resulting in a serious compromise instead of reporting the exploit attempt. If you don't have /bin/mail, or if you have 'safe setuid scripts', or if suidperl is not installed, you are safe.
The exploit attempt reporting feature has been completely removed from Perl 5.8.0 (and the maintenance release 5.6.1, and it was removed also from all the Perl 5.7 releases), so that particular vulnerability isn't there anymore. However, further security vulnerabilities are, unfortunately, always possible. The suidperl functionality is most probably going to be removed in Perl 5.10. In any case, suidperl should only be used by security experts who know exactly what they are doing and why they are using suidperl instead of some other solution such as sudo ( see http://www.courtesan.com/sudo/ ).
Several new tests have been added, especially for the lib and ext subsections. There are now about 69 000 individual tests (spread over about 700 test scripts), in the regression suite (5.6.1 has about 11 700 tests, in 258 test scripts) The exact numbers depend on the platform and Perl configuration used. Many of the new tests are of course introduced by the new modules, but still in general Perl is now more thoroughly tested.
Because of the large number of tests, running the regression suite will take considerably longer time than it used to: expect the suite to take up to 4-5 times longer to run than in perl 5.6. On a really fast machine you can hope to finish the suite in about 6-8 minutes (wallclock time).
The tests are now reported in a different order than in earlier Perls. (This happens because the test scripts from under t/lib have been moved to be closer to the library/extension they are testing.)
The compiler suite is slowly getting better but it continues to be highly experimental. Use in production environments is discouraged.
local %tied_array;
doesn't work as one would expect: the old value is restored incorrectly. This will be changed in a future release, but we don't know yet what the new semantics will exactly be. In any case, the change will break existing code that relies on the current (ill-defined) semantics, so just avoid doing this in general.
Some extensions like mod_perl are known to have issues with `largefiles', a change brought by Perl 5.6.0 in which file offsets default to 64 bits wide, where supported. Modules may fail to compile at all, or they may compile and work incorrectly. Currently, there is no good solution for the problem, but Configure now provides appropriate non-largefile ccflags, ldflags, libswanted, and libs in the %Config hash (e.g., $Config{ccflags_nolargefiles}) so the extensions that are having problems can try configuring themselves without the largefileness. This is admittedly not a clean solution, and the solution may not even work at all. One potential failure is whether one can (or, if one can, whether it's a good idea to) link together at all binaries with different ideas about file offsets; all this is platform-dependent.
for (1..5) { $_++ }
works without complaint. It shouldn't. (You should be able to modify only lvalue elements inside the loops.) You can see the correct behaviour by replacing the 1..5 with 1, 2, 3, 4, 5.
Use mod_perl 1.27 or higher.
Don't panic. Read the 'make test' section of INSTALL instead.
Use libwww-perl 5.65 or later.
Use PDL 2.3.4 or later.
You may get errors like 'Undefined symbol "Perl_get_sv"' or "can't resolve symbol 'Perl_get_sv'", or the symbol may be "Perl_sv_2pv". This probably means that you are trying to use an older shared Perl library (or extensions linked with such) with Perl 5.8.0 executable. Perl used to have such a subroutine, but that is no more the case. Check your shared library path, and any shared Perl libraries in those directories.
Sometimes this problem may also indicate a partial Perl 5.8.0 installation, see /"Mac OS X dyld undefined symbols" for an example and how to deal with it.
Self-tying of arrays and hashes is broken in rather deep and hard-to-fix ways. As a stop-gap measure to avoid people from getting frustrated at the mysterious results (core dumps, most often), it is forbidden for now (you will get a fatal error even from an attempt).
A change to self-tying of globs has caused them to be recursively referenced (see: perlobj/"Two-Phased Garbage Collection"). You will now need an explicit untie to destroy a self-tied glob. This behaviour may be fixed at a later date.
Self-tying of scalars and IO thingies works.
If this test fails, it indicates that your libc (C library) is not threadsafe. This particular test stress tests the localtime() call to find out whether it is threadsafe. See perlthrtut for more information.
Note that support for 5.005-style threading is deprecated, experimental and practically unsupported. In 5.10, it is expected to be removed. You should migrate your code to ithreads.
The following tests 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.
../ext/B/t/xref.t 255 65280 14 12 85.71% 3-14 ../ext/List/Util/t/first.t 255 65280 7 4 57.14% 2 5-7 ../lib/English.t 2 512 54 2 3.70% 2-3 ../lib/FileCache.t 5 1 20.00% 5 ../lib/Filter/Simple/t/data.t 6 3 50.00% 1-3 ../lib/Filter/Simple/t/filter_only. 9 3 33.33% 1-2 5 ../lib/Math/BigInt/t/bare_mbf.t 1627 4 0.25% 8 11 1626-1627 ../lib/Math/BigInt/t/bigfltpm.t 1629 4 0.25% 10 13 1628- 1629 ../lib/Math/BigInt/t/sub_mbf.t 1633 4 0.24% 8 11 1632-1633 ../lib/Math/BigInt/t/with_sub.t 1628 4 0.25% 9 12 1627-1628 ../lib/Tie/File/t/31_autodefer.t 255 65280 65 32 49.23% 34-65 ../lib/autouse.t 10 1 10.00% 4 op/flip.t 15 1 6.67% 15
These failures are unlikely to get fixed as 5.005-style threads are considered fundamentally broken. (Basically what happens is that competing threads can corrupt shared global state, one good example being regular expression engine's state.)
The following tests may fail intermittently because of timing problems, for example if the system is heavily loaded.
t/op/alarm.t ext/Time/HiRes/HiRes.t lib/Benchmark.t lib/Memoize/t/expmod_t.t lib/Memoize/t/speed.t
In case of failure please try running them manually, for example
./perl -Ilib ext/Time/HiRes/HiRes.t
For normal arrays
$foo = \$bar[1] will assign
undef to
$bar[1] (assuming that it didn't exist before), but for
tied/magical arrays and hashes such autovivification does not happen
because there is currently no way to catch the reference creation.
The same problem affects slicing over non-existent indices/keys of
a tied/magical array/hash.
One can have Unicode in identifier names, but not in package/class or subroutine names. While some limited functionality towards this does exist as of Perl 5.8.0, that is more accidental than designed; use of Unicode for the said purposes is unsupported.
One reason of this unfinishedness is its (currently) inherent unportability: since both package names and subroutine names may need to be mapped to file and directory names, the Unicode capability of the filesystem becomes important-- and there unfortunately aren't portable answers.
vac 126.96.36.199 May Produce Buggy Code For Perl
The AIX C compiler vac version 188.8.131.52 may produce buggy code, resulting in a few random tests failing when run as part of "make test", but when the failing tests are run by hand, they succeed. We suggest upgrading to at least vac version 126.96.36.199, that has been known to compile Perl correctly. "lslpp -L|grep vac.C" will tell you the vac version. See README.aix.
If building threaded Perl, you may get compilation warning from pp_sys.c:
"pp_sys.c", line 4651.39: 1506-280 (W) Function argument assignment between types "unsigned char*" and "const void*" is not allowed.
This is harmless; it is caused by the getnetbyaddr() and getnetbyaddr_r() having slightly different types for their first argument.
If you see op/pack, op/pat, op/regexp, or ext/Storable tests failing in a Linux/alpha or *BSD/Alpha, it's probably time to upgrade your gcc. gccs prior to 2.95.3 are definitely not good enough, and gcc 3.1 may be even better. (RedHat Linux/alpha with gcc 3.1 reported no problems, as did Linux 2.4.18 with gcc 2.95.4.) (In Tru64, it is preferable to use the bundled C compiler.)
Perl 5.8.0 doesn't build in AmigaOS. It broke at some point during the ithreads work and we could not find Amiga experts to unbreak the problems. Perl 5.6.1 still works for AmigaOS (as does the the 5.7.2 development release).
The following tests fail on 5.8.0 Perl in BeOS Personal 5.03:
t/op/lfs............................FAILED at test 17 t/op/magic..........................FAILED at test 24 ext/Fcntl/t/syslfs..................FAILED at test 17 ext/File/Glob/t/basic...............FAILED at test 3 ext/POSIX/t/sigaction...............FAILED at test 13 ext/POSIX/t/waitpid.................FAILED at test 1
See perlbeos (README.beos) for more details.
For example when building the Tk extension for Cygwin, you may get an error message saying "unable to remap". This is known problem with Cygwin, and a workaround is detailed in here: http://sources.redhat.com/ml/cygwin/2001-12/msg00894.html
One can build but not install (or test the build of) the NDBM_File on FAT filesystems. Installation (or build) on NTFS works fine. If one attempts the test on a FAT install (or build) the following failures are expected:
../ext/NDBM_File/ndbm.t 13 3328 71 59 83.10% 1-2 4 16-71 ../ext/ODBM_File/odbm.t 255 65280 ?? ?? % ?? ../lib/AnyDBM_File.t 2 512 12 2 16.67% 1 4 ../lib/Memoize/t/errors.t 0 139 11 5 45.45% 7-11 ../lib/Memoize/t/tie_ndbm.t 13 3328 4 4 100.00% 1-4 run/fresh_perl.t 97 1 1.03% 91
NDBM_File fails and ODBM_File just coredumps.
t/op/stat............................FAILED at test 29 lib/File/Find/t/find.................FAILED at test 1 lib/File/Find/t/taint................FAILED at test 1 lib/h2xs.............................FAILED at test 15 lib/Pod/t/eol........................FAILED at test 1 lib/Test/Harness/t/strap-analyze.....FAILED at test 8 lib/Test/Harness/t/test-harness......FAILED at test 23 lib/Test/Simple/t/exit...............FAILED at test 1
The above failures are known as of 5.8.0 with native builds with long filenames, but there are a few more if running under dosemu because of limitations (and maybe bugs) of dosemu:
t/comp/cpp...........................FAILED at test 3 t/op/inccode.........................(crash)
and a few lib/ExtUtils tests, and several hundred Encode/t/Aliases.t failures that work fine with long filenames. So you really might prefer native builds and long filenames.
This is a known bug in FreeBSD 4.5's readdir_r(), it has been fixed in FreeBSD 4.6 (see perlfreebsd (README.freebsd)).
The ISO 8859-15 locales may fail the locale test 117 in FreeBSD. This is caused by the characters \xFF (y with diaeresis) and \xBE (Y with diaeresis) not behaving correctly when being matched case-insensitively. Apparently this problem has been fixed in the latest FreeBSD releases. ( http://www.freebsd.org/cgi/query-pr.cgi?pr=34308 )
IRIX with MIPSpro 126.96.36.199m or 184.108.40.206m compiler may fail the List::Util test ext/List/Util/t/shuffle.t by dumping core. This seems to be a compiler error since if compiled with gcc no core dump ensues, and no failures have been seen on the said test on any other platform.
Similarly, building the Digest::MD5 extension has been known to fail with "*** Termination code 139 (bu21)".
The cure is to drop optimization level (Configure -Doptimize=-O2).
If perl is configured with -Duse64bitall, the successful result of the subtest 10 of lib/posix may arrive before the successful result of the subtest 9, which confuses the test harness so much that it thinks the subtest 9 failed.
This is a known bug in the glibc 2.2.5 with long long integers. ( http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=65612 )
No known fix.
Please remember to set your environment variable LC_ALL to "C" (setenv LC_ALL C) before running "make test" to avoid a lot of warnings about the broken locales of Mac OS X.
The following tests are known to fail in Mac OS X 10.1.5 because of buggy (old) implementations of Berkeley DB included in Mac OS X:
Failed Test Stat Wstat Total Fail Failed List of Failed ------------------------------------------------------------------------- ../ext/DB_File/t/db-btree.t 0 11 ?? ?? % ?? ../ext/DB_File/t/db-recno.t 149 3 2.01% 61 63 65
If you are building on a UFS partition, you will also probably see t/op/stat.t subtest #9 fail. This is caused by Darwin's UFS not supporting inode change time.
Also the ext/POSIX/t/posix.t subtest #10 fails but it is skipped for now because the failure is Apple's fault, not Perl's (blocked signals are lost).
If you Configure with ithreads, ext/threads/t/libc.t will fail. Again, this is not Perl's fault-- the libc of Mac OS X is not threadsafe (in this particular test, the localtime() call is found to be threadunsafe.)
If after installing Perl 5.8.0 you are getting warnings about missing symbols, for example
dyld: perl Undefined symbols _perl_sv_2pv _perl_get_sv
you probably have an old pre-Perl-5.8.0 installation (or parts of one) in /Library/Perl (the undefined symbols used to exist in pre-5.8.0 Perls). It seems that for some reason "make install" doesn't always completely overwrite the files in /Library/Perl. You can move the old Perl shared library out of the way like this:
cd /Library/Perl/darwin/CORE mv libperl.dylib libperlold.dylib
and then reissue "make install". Note that the above of course is extremely disruptive for anything using the /usr/local/bin/perl. If that doesn't help, you may have to try removing all the .bundle files from beneath /Library/Perl, and again "make install"-ing.
The following tests are known to fail on OS/2 (for clarity only the failures are shown, not the full error messages):
../lib/ExtUtils/t/Mkbootstrap.t 1 256 18 1 5.56% 8 ../lib/ExtUtils/t/Packlist.t 1 256 34 1 2.94% 17 ../lib/ExtUtils/t/basic.t 1 256 17 1 5.88% 14 lib/os2_process.t 2 512 227 2 0.88% 174 209 lib/os2_process_kid.t 227 2 0.88% 174 209 lib/rx_cmprt.t 255 65280 18 3 16.67% 16-18
The op/sprintf tests 91, 129, and 130 are known to fail on some platforms. Examples include any platform using sfio, and Compaq/Tandem's NonStop-UX.
Test 91 is known to fail on QNX6 (nto), because
sprintf '%e',0
incorrectly produces
0.000000e+0 instead of
For tests 129 and 130, the failing platforms do not comply with the ANSI C Standard: lines 19ff on page 134 of ANSI X3.159 1989, to be exact. (They produce something other than "1" and "-1" when formatting 0.6 and -0.6 using the printf format "%.0f"; most often, they produce "0" and "-0".)
In case you are still using Solaris 2.5 (aka SunOS 5.5), you may experience failures (the test core dumping) in lib/locale.t. The suggested cure is to upgrade your Solaris.
The following tests are known to fail in Solaris x86 with Perl configured to use 64 bit integers:
ext/Data/Dumper/t/dumper.............FAILED at test 268 ext/Devel/Peek/Peek..................FAILED at test 7
The following tests are known to fail on SUPER-UX:
op/64bitint...........................FAILED tests 29-30, 32-33, 35-36 op/arith..............................FAILED tests 128-130 op/pack...............................FAILED tests 25-5625 op/pow................................ op/taint..............................# msgsnd failed ../ext/IO/lib/IO/t/io_poll............FAILED tests 3-4 ../ext/IPC/SysV/ipcsysv...............FAILED tests 2, 5-6 ../ext/IPC/SysV/t/msg.................FAILED tests 2, 4-6 ../ext/Socket/socketpair..............FAILED tests 12 ../lib/IPC/SysV.......................FAILED tests 2, 5-6 ../lib/warnings.......................FAILED tests 115-116, 118-119
The op/pack failure ("Cannot compress negative numbers at op/pack.t line 126") is serious but as of yet unsolved. It points at some problems with the signedness handling of the C compiler, as do the 64bitint, arith, and pow failures. Most of the rest point at problems with SysV IPC.
Use Term::ReadKey 2.20 or later.
During Configure, the test
Guessing which symbols your C compiler and preprocessor define...
will probably fail with error messages like
CC-20 cc: ERROR File = try.c, Line = 3 The identifier "bad" is undefined.
bad switch yylook 79bad switch yylook 79bad switch yylook 79bad switch yylook 79#ifdef A29K ^
CC-65 cc: ERROR File = try.c, Line = 3 A semicolon is expected at this point.
This is caused by a bug in the awk utility of UNICOS/mk. You can ignore the error, but it does cause a slight problem: you cannot fully benefit from the h2ph utility (see h2ph) that can be used to convert C headers to Perl libraries, mainly used to be able to access from Perl the constants defined using C preprocessor, cpp. Because of the above error, parts of the converted headers will be invisible. Luckily, these days the need for h2ph is rare.
There are a few known test failures, see perluts (README.uts).
When Perl is built using the native build process on VOS Release 14.5.0 and GNU C++/GNU Tools 2.0.1, all attempted tests either pass or result in TODO (ignored) failures.
There should be no reported test failures with a default configuration, though there are a number of tests marked TODO that point to areas needing further debugging and/or porting work.
In multi-CPU boxes, there are some problems with the I/O buffering: some output may appear twice.
Use XML::Parser 2.31 or later.
z/OS has rather many test failures but the situation is actually much better than it was in 5.6.0; it's just that so many new modules and tests have been added.
Failed Test Stat Wstat Total Fail Failed List of Failed --------------------------------------------------------------------------- ../ext/Data/Dumper/t/dumper.t 357 8 2.24% 311 314 325 327 331 333 337 339 ../ext/IO/lib/IO/t/io_unix.t 5 4 80.00% 2-5 ../ext/Storable/t/downgrade.t 12 3072 169 12 7.10% 14-15 46-47 78-79 110-111 150 161 ../lib/ExtUtils/t/Constant.t 121 30976 48 48 100.00% 1-48 ../lib/ExtUtils/t/Embed.t 9 9 100.00% 1-9 op/pat.t 922 7 0.76% 665 776 785 832- 834 845 op/sprintf.t 224 3 1.34% 98 100 136 op/tr.t 97 5 5.15% 63 71-74 uni/fold.t 780 6 0.77% 61 169 196 661 710-711
The failures in dumper.t and downgrade.t are problems in the tests, those in io_unix and sprintf are problems in the USS (UDP sockets and printf formats). The pat, tr, and fold failures are genuine Perl problems caused by EBCDIC (and in the pat and fold cases, combining that with Unicode). The Constant and Embed are probably problems in the tests (since they test Perl's ability to build extensions, and that seems to be working reasonably well.)
Though mostly working, Unicode support still has problem spots on
EBCDIC platforms. One such known spot are the
\p{} and
regular expression constructs for code points less than 256: the
pP are testing for Unicode code points, not knowing about EBCDIC.
Time::Piece (previously known as
Time::Object) was removed
because it was felt that it didn't have enough value in it to be a
core module. It is still a useful module, though, and is available
from the CPAN.
Perl 5.8 unfortunately does not build anymore on AmigaOS; this broke accidentally at some point. Since there are not that many Amiga developers available, we could not get this fixed and tested in time for 5.8.0. Perl 5.6.1 still works for AmigaOS (as does the the 5.7.2 development release).
PerlIO::Scalar and
PerlIO::Via (capitalised) were renamed as
PerlIO::scalar and
PerlIO::via (all lowercase) just before 5.8.0.
The main rationale was to have all core PerlIO layers to have all
lowercase names. The "plugins" are named as usual, for example
threads::shared::queue and
threads::shared::semaphore were
renamed as
Thread::Queue and
Thread::Semaphore just before 5.8.0.
The main rationale was to have thread modules to obey normal naming,
Thread:: (the
threads and
threads::shared themselves are
more pragma-like, they affect compile-time, so they stay lowercase).
If you find what you think is a bug, you might check the articles recently posted to the comp.lang.perl.misc newsgroup and the perl bug database at http://bugs.perl.org/ . There may also be information at http://www.perl.com/ , the Perl Home Page.
If you believe you have an unreported bug, please run the perlbug
program included with your release. Be sure to trim your bug down
to a tiny but sufficient test case. Your bug report, along with the
output of
perl -V, will be sent off to firstname.lastname@example.com to be
analysed by the Perl porting team.
The Changes file for exhaustive details on what changed.
The INSTALL file for how to build Perl.
The README file for general stuff.
The Artistic and Copying files for copyright information.
Written by Jarkko Hietaniemi <email@example.com>.


text: MIT is at the forefront of developing and applying learning technologies in the classroom. Faculty and instructors are pioneering pedagogical implementation of research-based teaching practices to bring digital innovations to residential education. This is achieved through leveraging the capabilities of MITx and other digital tools and resources. These initiatives deepen and strengthen learning for on-campus students. View the course list below.


text:
2 Inkfirst® Toner Cartridges MLT-D108S MLTD108S Compatible Remanufactured for Samsung ML-1640 ML1640 Black ML-2240
Available online only
These Inkfirst® compatible remanufactured ML-1640 black toner cartridges are manufactured in ISO9001 and ISO40001 certified manufacturing facilities. These compatible cartridges for Samsung ML-1640 are cost-effective and they offer professional high printing quality for all your printing needs. You'll be getting quality compatible cartridges for Samsung ML-1640 (MLT-D108S) toner cartridges that produce sharp & crisp text with consistent and stable performance.
Save even more now with the purchasing of this value pack of 2 compatible toner cartridges for Samsung ML-1640.
These compatible cartridges for Samsung ML-1640 are for use in the following Samsung printers: Samsung ML-1640 / ML-2240.
Storage Tips: Please store in a typical environment with non-extreme heat, cold and humidity & Keep in original sealed package until installation.
- This Value Pack contains a total of 2 Inkfirst® Compatible Toner Cartridges for Samsung ML-1640. It includes: 2 x Toner.
- British Columbia (Remote)
- Alberta (Remote)
- Saskatchewan (Remote)
- Manitoba (Remote)
- Ontario (Remote)
- Quebec (Remote)
- New Brunswick (Remote)
- Nova Scotia (Remote)
- Prince Edward Island (Remote)
- Newfoundland and Labrador (Remote)
- Yukon
- Northwest Territories
- Nunavut
|Restocking Fees / Return Eligibility
|Return Period
|Office Supply Consumables (Ink, Toner, etc.)
|30 Days
|Not Returnable
All returned products must include original packaging.
Return shipping costs will be paid by the seller for all cases where the product is defective, damaged or incorrect. For other cases (e.g. you changed your mind), you will be responsible for this cost.
To request a return
Please contact the seller directly from your Order details page, and provide the following information:
- Web ID (8-digit number) & product description
- Number of items to be returned
- Date you received your product
- Condition of product
- Condition of packaging
- Reason for return
All refunds will be processed within 4 Business Days.


text:
A buck white-tailed deer (Odocoileus virginianus) portrait during a snowstorm. Twin Cities, Minnesota.
All Museum Quality Prints are printed on Hahnemuhle Photo Rag Pearl myself using an Epson SureColor P9000 in my studio. This a natural white pearl-gloss paper that will not yellow and offers a phenomenal color gamut, clarity, and an exceptionally long life. These are loose prints shipped rolled around a hard tube, enclosed in a protective package.
The Metal and Acrylic options are printed by one of the industry's best labs. Both options offer a clean modern appearance to the artwork, which looks as if it's floating off the wall with the included hanging hardware. The Metal prints are lightweight, durable and have a HD glossy finish that come ready to hang via float hanger attached to the back of the piece. The Acrylic prints are lustre fine-art paper mounted to 1/4" thick glossy acrylic with di-bond backing and a cleat hanger.