Lifting Moose.Key

Total Page:16

File Type:pdf, Size:1020Kb

Lifting Moose.Key Lifting Moose Shawn M Moore @sartak Behavior State Identity Object-oriented programming is about behavior, state, and identity. Behavior as in message passing, method calls. State as in attributes, properties. Identity as in two objects with the same values for their properties are distinct. Every object-oriented programming language provides these core principles. But then there’s the details. Ohh the details. Class vs prototype “final” or open Behavior Dynamic or static State Generic methods Identity Traits / Roles Operator overload Rebless Every programming language provides a unique take on object-oriented programming. For example, some languages provide inheritance via classes, others via prototype. Some have “final” declarations, some have dynamic dispatch, some generic methods, etc. etc. It’s almost like you could pick any mix of features that make sense together and there’d be a language there. Some exist even where their list of features don’t really make sense together. Object-oriented Programming C# Java CLOS C++ PHP Lua Elk JS Perl Py Ruby Smalltalk We could even treat languages as points on a plane, where position is determined by the set of OOP tradeoffs that language has made. Perl is here. Obviously. And then there’s a bunch of other languages that are more or less different from other languages. By the way, don’t take this chart too literally; it’s merely demonstrative. PHP Lua Perl Python Ruby Smalltalk Let’s zoom in around Perl. All the usual suspects are here. None of these languages provide exactly the same OOP. For example Ruby lets you subclass builtin types like string and array. In Python you don’t have to explicitly “bless” a reference into an object but is otherwise pretty similar to Perl. But they’re all similar in that they’re dynamic, more-or-less-hash-based, weakly typed languages, so that’s why they’re in a quadrant together. PHP Lua Inside-out Perl Spiffy Class::Accessor Python Ruby Smalltalk But you might be thinking… hey, there’s more than one way to do it. The way I write OOP Perl is different from the way you write OOP Perl. And Ingy writes Perl like no one else. shawn ❤️ ingy CC BY-SA @miyagawa http://flickr.com/photos/bulknews/4731400345 Hey, Spiffy may not have worked out, but don’t hate on Ingy! Inside-out Spiffy Standard Perl Class::Accessor You might be wondering where Moose is on this chart. Moose Inside-out Spiffy Standard Perl Class::Accessor Moose as it exists out of the box is here. But there’s something more going on. Moose is flexible and extensible in ways that these other systems are not. In fact, you can extend Moose to be like any of these other systems. And anywhere in between. Moose Inside-out Spiffy Standard Perl Class::Accessor So we might render Moose as a region instead of a point. Moose can work like any of these other systems…. hang on a sec, this isn’t very Moosey. Moose Inside-out Spiffy Standard Perl Class::Accessor That’s better. So, for example, MooseX::InsideOut lets you store properties outside of the object, especially useful when subclassing someone else’s code. And of course you can tweak that to be a point close to, but not exactly, standard inside-out objects. Perhaps you want to store properties by something other than object address, like some kind of application-specific identifier. Moose Inside-out Spiffy Standard Perl Class::Accessor This is the crux of the talk: with Moose you can move to any point in this region that makes sense for your application. In other words (shedding the point/region metaphor), with Moose you can select exactly the set of OOP features you want for your application. All without leaving Perl for a different language. All while being able to robustly interoperate with code from CPAN and other developers. That’s the true power of Moose. That’s what keeps me writing Perl. Not “has”. Instance Class Method Attribute Moose pulls this off by doing something so simple you probably wouldn’t believe it could work. Moose itself is implemented using instances, classes, methods, and attributes. The other systems mentioned, like standard Perl OOP, are implemented with things like hash tables, C functions, structs, pointers, glob assignment. This means you can’t subclass or use any other OOP technique to extend or modify their behavior; each is a static artifact: a singular, area-less point on the OOP chart. You get what you get and you don’t throw a fit. package Reluctant; use Moose::Role; before new_object => sub { warn “Another one…? �”; sleep 1; }; Because Moose is OOP it’s very familiar to extend it. You do it in two parts: first, write the extension. The extension can usually be a role. It’s okay if you haven’t seen roles before, the example will still be clear. In this example I looked at Moose’s documentation or its code to figure out that new_object is the method we wanted to override. Then just use an “before” method modifier to whinge and drag my feet about it. So you get the standard behavior for classes that Moose provides, plus this one tiny incremental change. package Person; use Moose -traits => ‘Reluctant’; Person->new(name => ‘Stevan’); # Another one…? � Person->new(name => ‘Yuval’); # Another one…? � Then we tell Moose we want to use this extension in our class. Done. Note that this is robust and modular: only Person and its subclasses will get this behavior, no one else. This is much better than alternatives like monkeypatching! Behind the scenes this is just saying “give me a subclass of the standard Moose class with the Reluctant role”. Easy peasy. It’s just object-oriented programming. You’ve subclassed a million classes by now. You got dis! By the way there are literally millions of Moose extensions on CPAN. Each of these MooseX modules fills in and expands the region of OOP that Moose supports. So a lot of times you can skip that first step and just go to using these existing extensions. Public domain http://bit.ly/1Mjdi0P Because it’s all OOP, there are no black boxes in Moose. In other words, in Moose, the plumbing (the internals) and the porcelain (the user interface) are one and the same; there’s nothing hidden beneath the surface. This is a huge benefit in so many ways because it means there’s a unified model, and it’s a model you’re already familiar with. You can use porcelain to extend any part of Moose because it’s all porcelain, and by the way, our porcelain is terrific. Single parameters to new() must be a HASH ref at /Users/ sartak/.perl/perls/perl-5.22.0/lib/site_perl/5.22.0/ darwin-2level/Moose/Exception.pm line 37 Moose::Exception::_build_trace('Moose::Exception::SinglePa ramsToNewMustBeHashRef=HASH(0x7fd49af417a8)') called at reader Moose::Exception::trace (defined at /Users/ sartak/.perl/perls/perl-5.22.0/lib/site_perl/5.22.0/ darwin-2level/Moose/Exception.pm line 9) line 7 Moose::Exception::trace('Moose::Exception::SingleParamsToN ewMustBeHashRef=HASH(0x7fd49af417a8)') called at /Users/ sartak/.perl/perls/perl-5.22.0/lib/site_perl/5.22.0/ darwin-2level/Moose/Exception.pm line 49 Moose::Exception::BUILD('Moose::Exception::SingleParamsToN ewMustBeHashRef=HASH(0x7fd49af417a8)', 'HASH(0x7fd49af42f70)') called at /Users/sartak/.perl/ perls/perl-5.22.0/lib/site_perl/5.22.0/darwin-2level/ Class/MOP/Method.pm line 126 But sometimes this power backfires and you get a plumbing problem where you were expecting a porcelain problem. Like the real world, this is a crappy situation to be in. Sorry. � US Patent #4320756 “A method for breathing fresh air in a room filled with toxic smoke” https://www.google.com/patents/US4320756 “The recent rash of fires in high-rise hotels and deaths occasioned thereby has given rise to the need for a breathing device and method for supplying a hotel guest and/or fireman with fresh air until he can be rescued. The device and method of this invention provide for the insertion of a breathing tube through the water trap of a toilet to expose an open end thereof to fresh air from a vent pipe connected to a sewer line of the toilet, to enable the user to breathe fresh air through the tube.” CC BY-NC-SA http://flickr.com/photos/foxtongue/3237307610 And here’s where we get into the title of the talk. What’s this lifting business about. While yes, it is wonderful that there’s an extension that adds multi- methods to Moose. But Moose extensions really don’t need to be “about” object-oriented programming. There are no limits here. Your Moose extensions can be domain-specific, or “about” your application. Application Moose perl OS Imagine your application as a pink pill sitting at the top of a stack including Moose, Perl, and the OS. What I’m proposing is that you… Application Moose perl OS …lift Moose more into your application, so that Moose not something you merely sit on, it becomes an active participant in how your application is architected. Don’t reinvent half of Moose poorly. Web Forms has email => ( is => ‘rw’, ); The canonical example might be web forms. Your classes have attributes and perhaps you’re writing a web form to populate those attributes. Well, you can start by looking at the core Moose options for attributes. Web Forms has email => ( is => ‘rw’, required => 1, ); Requiredness is easy enough. Just inspect the attribute’s “required” property and if so add the little asterisk to indicate that it’s required.
Recommended publications
  • Perl Baseless Myths & Startling Realities
    http://xkcd.com/224/ 1 Perl Baseless Myths & Startling Realities by Tim Bunce, February 2008 2 Parrot and Perl 6 portion incomplete due to lack of time (not lack of myths!) Realities - I'm positive about Perl Not negative about other languages - Pick any language well suited to the task - Good developers are always most important, whatever language is used 3 DISPEL myths UPDATE about perl Who am I? - Tim Bunce - Author of the Perl DBI module - Using Perl since 1991 - Involved in the development of Perl 5 - “Pumpkin” for 5.4.x maintenance releases - http://blog.timbunce.org 4 Perl 5.4.x 1997-1998 Living on the west coast of Ireland ~ Myths ~ 5 http://www.bleaklow.com/blog/2003/08/new_perl_6_book_announced.html ~ Myths ~ - Perl is dead - Perl is hard to read / test / maintain - Perl 6 is killing Perl 5 6 Another myth: Perl is slow: http://www.tbray.org/ongoing/When/200x/2007/10/30/WF-Results ~ Myths ~ - Perl is dead - Perl is hard to read / test / maintain - Perl 6 is killing Perl 5 7 Perl 5 - Perl 5 isn’t the new kid on the block - Perl is 21 years old - Perl 5 is 14 years old - A mature language with a mature culture 8 How many times Microsoft has changed developer technologies in the last 14 years... 9 10 You can guess where thatʼs leading... From “The State of the Onion 10” by Larry Wall, 2006 http://www.perl.com/pub/a/2006/09/21/onion.html?page=3 Buzz != Jobs - Perl5 hasn’t been generating buzz recently - It’s just getting on with the job - Lots of jobs - just not all in web development 11 Web developers tend to have a narrow focus.
    [Show full text]
  • Current Issues in Perl Programming Overview
    Current Issues In Perl Programming Lukas Thiemeier Current Issues In Perl Programming DESY, Zeuthen, 2011-04-26 Overview > Introduction > Moose – modern object-orientation in Perl > DBIx::Class – comfortable an flexible database access > Catalyst – a MVC web application framework Lukas Thiemeier | Current issues in Perl programming | 2011-04-26 | Page 2 Introduction > What is this talk about? . Modern Perl can do more than most people know . A quick overview about some modern features . Illustrated with some short examples > What is this talk not about? . Not an introduction to the Perl programming language . Not a Perl tutorial . Not a complete list of all current issues in Perl 5 . Not a complete HowTo for the covered topics Lukas Thiemeier | Current issues in Perl programming | 2011-04-26 | Page 3 Overview > Introduction > Moose – modern object-orientation in Perl . About Moose . Creating and extending classes . Some advanced features > DBIx::Class – comfortable an flexible database access > Catalyst – a MVC web application framework Lukas Thiemeier | Current issues in Perl programming | 2011-04-26 | Page 4 About Moose > “A postmodern object system for Perl 5” > Based on Class::MOP, a metaclass system for Perl 5 > Look and feel similar to the Perl 6 object syntax “The main goal of Moose is to make Perl 5 Object Oriented programming easier, more consistent and less tedious. With Moose you can to think more about what you want to do and less about the mechanics of OOP.” Lukas Thiemeier | Current issues in Perl programming | 2011-04-26 | Page 5 Creating Classes > A very simple Moose-Class: . Create a file called “MyAnimalClass.pm” with the following content: package MyAnimalClass; use Moose; no Moose; 1; Lukas Thiemeier | Current issues in Perl programming | 2011-04-26 | Page 6 Creating Classes > A very simple Moose-Class: The package name is used as class name.
    [Show full text]
  • A Retrospective on Pugs ☺
    ☺ A retrospective on Pugs ☺ Ingo Blechschmidt <[email protected]> Augsburg.pm (April 13th, 2015) Pugs, an experimental Perl 6 platform: a retrospective 1 / 37 April 13th, 2015 Abstract. “Hi. Today I have started working on specifying and implementing Feath- erweight Perl 6 (FP6), a side-effect-free subset of Perl 6.” Audrey Tang used these words to unveil the Pugs project in February of 2005. Initially conceived as an imple- mentation of a small subset of Perl 6 in Haskell, the project quickly grew to contain a full-fledged compiler and interpreter for Perl 6 and aracted a large and diverse community. e talk will give a subjective survey of the history of Pugs. We will pay particular aention to the special manner with which Audrey led the project and what the phi- losophy “-Ofun” meant to the developers. We’ll also discuss which parts of Pugs were absorbed into other implementations of Perl 6 and which influence Pugs had on the Perl and Haskell communities. About me. I contributed to Pugs as a school student in 2005, at first by porting modules and writing tests, then gradually also by writing Haskell code and later by implement- ing a JavaScript backend. Audrey and the unique spirit in the Pugs community had a strong and lasting influence on me (exposing me to Haskell, category theory, and a beautiful way of tending communities); I look back on very exciting and fun days. Warning. e account is mostly from memory and not properly researched. Try not to trust it! Also note that the timeline covers only the year 2005 and that the code excerpts are edited for legibility, i.
    [Show full text]
  • Perl 6 Audrey Tang
    Deploying Perl 6 Audrey Tang 1 Perl 6 is here Today! 2 Perl 6 is here Today! (YAPC::NA 2005) 3 Pugs 6.2.12 •Released on June 26th •3x faster build time •10x faster compilation •2x faster runtime •2000+ commits since 6.2.11 4 Parrot 0.4.5 •Released last June 19th •Unicode identifiers •Hierarchical namespace •New .NET CLR translator •Much faster compiler tools 5 Great for experimenting 6 But not for production 7 ...not this Christmas 8 9 CPAN is the language 10 Perl is just its syntax 11 Perl 5.000b3h (October 1994) 12 • use 5.000; • use strict; • require 'fastcwd.pl'; • require 'newgetopt.pl'; • require 'exceptions.pl'; • # ... • 13 Continuity++ 14 Pugs 6.2.2 (June 2005) 15 • use v6-pugs; • use perl5:DBI; • use perl5:Encode; • use perl5:Template; • # ... • 16 Still need to install Pugs 17 Perl 5.9.3 (Jan 2006) 18 • use v5.9.3; • use feature qw(switch say err ~~); • given (shift()) { • when ['‐h', '‐‐help'] { • say "Usage: $0"; • } • default { • $0 ~~ 'moose.exe' err die "Not Moose"; • } • } • 19 How to get Perl 6 into Production? 20 Production • Work with existing code • Must support Perl 5 and XS • No from‐scratch rewrites 21 Frontends? Tcl Python Scheme Parrot 22 Frontends? Tcl Python Scheme Perl 5 (Ponie) Parrot Perl 6 23 Backends! Pugs Java Haskell Perl 5 Script 24 Backends! JVM? YARV? Pugs CLR? PyPy? Java Haskell Perl 5 Script 25 Pugs on Perl 5 26 Perl 6 Runtime Implemented as Perl 5 Modules 27 Sane Perl 5 (not source filters) 28 Available On CPAN Today 29 Moose.pm ☯ 30 What is Moose? • Complete object model for Perl 5 • Based on the
    [Show full text]
  • Perl Baseless Myths & Startling Realities
    http://xkcd.com/224/ Perl Baseless Myths & Startling Realities by Tim Bunce, July 2008 Prefer ‘Good Developers’ over ‘Good Languages’ “For all program aspects investigated, the performance variability that derives from differences among programmers of the same language—as described by the bad-to-good ratios—is on average as large or larger than the variability found among the different languages.” — An empirical comparison of C, C++, Java, Perl, Python, Rexx, and Tcl. IEEE Computer Journal October 2000 Who am I? - Tim Bunce - Author of the Perl DBI module - Using Perl since 1991 - Involved in the development of Perl 5 - “Pumpkin” for 5.4.x maintenance releases - http://blog.timbunce.org ~ Myths ~ ~ Myths ~ - Perl is dead - Perl is hard to read / test / maintain - Perl 6 is killing Perl 5 ~ Myths ~ - Perl is dead - Perl is hard to read / test / maintain - Perl 6 is killing Perl 5 Perl 5 - Perl 5 isn’t the new kid on the block - Perl is 21 years old - Perl 5 is 14 years old - A mature language with a mature culture Buzz != Jobs - Perl5 hasn’t been generating buzz recently - It’s just getting on with the job - Lots of jobs - - just not all in web development Guess the Languages “web developer” Yes, Perl is growing more slowly than others but these are just “web developer” jobs “software engineer” Perl is mentioned in many more software engineer/developer jobs. “foo developer” Perl is the primary focus of more developer jobs. Want a fun new job? Become a Perl developer! Massive Module Market - Large and vibrant developer community - Over 15,000 distributions (58,000 modules) - Over 6,700 ‘authors’ (who make releases) - One quarter of all CPAN distributions have been updated in the last 4 months! - Half of all updated in the last 17 months! Top Modules -Many gems, including..
    [Show full text]
  • Pragmaticperl-Interviews-A4.Pdf
    Pragmatic Perl Interviews pragmaticperl.com 2013—2015 Editor and interviewer: Viacheslav Tykhanovskyi Covers: Marko Ivanyk Revision: 2018-03-02 11:22 © Pragmatic Perl Contents 1 Preface .......................................... 1 2 Alexis Sukrieh (April 2013) ............................... 2 3 Sawyer X (May 2013) .................................. 10 4 Stevan Little (September 2013) ............................. 17 5 chromatic (October 2013) ................................ 22 6 Marc Lehmann (November 2013) ............................ 29 7 Tokuhiro Matsuno (January 2014) ........................... 46 8 Randal Schwartz (February 2014) ........................... 53 9 Christian Walde (May 2014) .............................. 56 10 Florian Ragwitz (rafl) (June 2014) ........................... 62 11 Curtis “Ovid” Poe (September 2014) .......................... 70 12 Leon Timmermans (October 2014) ........................... 77 13 Olaf Alders (December 2014) .............................. 81 14 Ricardo Signes (January 2015) ............................. 87 15 Neil Bowers (February 2015) .............................. 94 16 Renée Bäcker (June 2015) ................................ 102 17 David Golden (July 2015) ................................ 109 18 Philippe Bruhat (Book) (August 2015) . 115 19 Author .......................................... 123 i Preface 1 Preface Hello there! You have downloaded a compilation of interviews done with Perl pro- grammers in Pragmatic Perl journal from 2013 to 2015. Since the journal itself is in Russian
    [Show full text]
  • Effective Perl Programming
    Effective Perl Programming Second Edition The Effective Software Development Series Scott Meyers, Consulting Editor Visit informit.com/esds for a complete list of available publications. he Effective Software Development Series provides expert advice on Tall aspects of modern software development. Books in the series are well written, technically sound, and of lasting value. Each describes the critical things experts always do—or always avoid—to produce outstanding software. Scott Meyers, author of the best-selling books Effective C++ (now in its third edition), More Effective C++, and Effective STL (all available in both print and electronic versions), conceived of the series and acts as its consulting editor. Authors in the series work with Meyers to create essential reading in a format that is familiar and accessible for software developers of every stripe. Effective Perl Programming Ways to Write Better, More Idiomatic Perl Second Edition Joseph N. Hall Joshua A. McAdams brian d foy Upper Saddle River, NJ • Boston • Indianapolis • San Francisco New York • Toronto • Montreal • London • Munich • Paris • Madrid Capetown • Sydney • Tokyo • Singapore • Mexico City Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The authors and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein.
    [Show full text]
  • Compiling Your Own Perl
    APPENDIX A Compiling Your Own Perl Compiling Perl on a Unix-like system is simple. First, obtain the source for Perl from CPAN (dppl6++_l]j*lanh*knc+on_+NA=@IA*dpih). Then input the following sequence of commands: p]nvtrblanh)1*4*4*p]n*cv _`lanh)1*4*4 od?kjbecqna)`ao i]ga i]gapaop oq`ki]gaejop]hh On most Unix systems, this code will result in your lanh being installed into the +qon+ hk_]h+ directory tree. If you want it installed elsewhere—for example, in the local directory in your home directory—then replace od?kjbecqna)`a with the following: od?kjbecqna)`ao)@lnabet9z+hk_]h+ which should enable you to install Perl on your computer without root access. Note that the )`ao flag uses all the default options for compiling Perl. If you know that you want nonstandard configuration, just use the flag )`a instead to be prompted for your requirements. Be aware that the source for Perl 5.10.0 requires a patch to work properly with Catalyst. This is fixed in subsequent versions of Perl 5.10. If you need to test code guaranteed to run on a wide range of systems, you should con- sider using Perl version 5.8.7. Perl versions greater than 5.8.7 contain features that were not available in earlier versions of Perl, so Perl 5.8.7 is feature complete for all versions of Perl that Catalyst will run on (version 5.8.1 and later). Put another way, versions 5.8.8 and later have new features that you can’t rely on in earlier releases.
    [Show full text]
  • Modern Perl, Fourth Edition
    Prepared exclusively for none ofyourbusiness Prepared exclusively for none ofyourbusiness Early Praise for Modern Perl, Fourth Edition A dozen years ago I was sure I knew what Perl looked like: unreadable and obscure. chromatic showed me beautiful, structured expressive code then. He’s the right guy to teach Modern Perl. He was writing it before it existed. ➤ Daniel Steinberg President, DimSumThinking, Inc. A tour de force of idiomatic code, Modern Perl teaches you not just “how” but also “why.” ➤ David Farrell Editor, PerlTricks.com If I had to pick a single book to teach Perl 5, this is the one I’d choose. As I read it, I was reminded of the first time I read K&R. It will teach everything that one needs to know to write Perl 5 well. ➤ David Golden Member, Perl 5 Porters, Autopragmatic, LLC I’m about to teach a new hire Perl using the first edition of Modern Perl. I’d much rather use the updated copy! ➤ Belden Lyman Principal Software Engineer, MediaMath It’s not the Perl book you deserve. It’s the Perl book you need. ➤ Gizmo Mathboy Co-founder, Greater Lafayette Open Source Symposium (GLOSSY) Prepared exclusively for none ofyourbusiness We've left this page blank to make the page numbers the same in the electronic and paper books. We tried just leaving it out, but then people wrote us to ask about the missing pages. Anyway, Eddy the Gerbil wanted to say “hello.” Prepared exclusively for none ofyourbusiness Modern Perl, Fourth Edition chromatic The Pragmatic Bookshelf Dallas, Texas • Raleigh, North Carolina Prepared exclusively for none ofyourbusiness Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks.
    [Show full text]
  • Moose Quickref Card
    Attribute Constructor Options Moose Quick-Ref Card trigger => sub {…} A modern object system for Perl 5 is => ‘rw’|’ro’ Code to run after attribute is set. Is Creates a read/write or read-only passed ($self, $new_val). accessor. If you omit this option, no Exported Functions accessor will be created. default => $val | sub{ []|{}|sub{…} } use Moose; isa => $type_name | '$ta|$tb|…' Default value to initialize attribute. Turns on strict and warnings. Set up run-time type checking. The outer sub{} is passed $self. Exports confess and blessed. See below for $type_name details. predicate => $name extends @superclasses does => $role Method $name will perform a basic Moose’s alternative to use base. Value’s class must consume $role. defined test on the attribute. Note that it will re-set @ISA. metaclass => $name reader|writer|clearer => $sub_name with @roles Extend attribute via a metaclass. Provide the subroutine names used to with $role => { %options } read from, write to, and uninitialize the Consume roles (interfaces) as an traits => [@role_names] stored value. alternative to extending classes. Apply roles to attribute’s meta-object. builder => $sub_name has $name => %options coerce => 1|0 Separate method to return default value. Allow coercion to $type_name on storage. Install an attribute into this class. Better than default for subclassing. See below for details. See below for %options details. lazy_build => 1 required => 1|0 has “+$name” => %options Sets lazy, required, predicate (has_$name), Attribute must always have a value. Clone and extend an attribute. clearer (clear_$name) and builder (_build_$name). before @names => sub {…} weak_ref => 1|0 around @names => sub {…} Value is stored as weakened ref init_arg => $name after @names => sub {…} (note: conflicts with coercion).
    [Show full text]
  • State of Alaska Department of Military and Veteran Affairs
    AALLAASSKKAA AAllll--HHaazzaarrdd RRiisskk MMiittiiggaattiioonn PPllaann State of Alaska Department of Military and Veteran Affairs Prepared By Division of Homeland Security & Emergency Management October 2007 Table of Contents STATE OF ALASKA ALL-HAZARD RISK MITIGATION PLAN Table of Contents October 2007 Executive Summary ........................................................................................................... i Table of Contents............................................................................................. iii 1.0 Introduction .................................................................................................................1 1.1 Purpose.......................................................................................................1 1.2 Assumptions................................................................................................1 1.3 Authority ......................................................................................................1 1.4 A Guide to this Plan.....................................................................................2 1.5 Alaska Background Information...................................................................5 1.6 Alaska’s Structure .......................................................................................5 1.7 General Facts..............................................................................................5 1.8 Land Transportation ....................................................................................8
    [Show full text]
  • The Oxford Democrat: Vol. 62, No. 47
    The Oxford Democrat. NUMBER 47. you mk 62. SOUTH PARIS, MAINE, TUESDAY. 19,189». NOVEMBER offorta to advance the it* l,u0 tho linn in their HAIR SOAP. .,ΕΟΚι.Κ 1> ΚΙ^ΒΚ*. POTATOES IN THE UNITED STATES OVER THE SEA TO SKYE. field te kvard opponentV g·"»! HaadtV· Obotlnvj. CHINESE AMONG THE F ARMEES. the bull. He two outstretched hand*, The crop is not but fai THE BACK. The F Lirficld t<ani, weakened by dodges doe· not al I» only large, by QUARTER À child's obstinacy way* It la to Look ai, but time us a him- ΙΜμ(τμ·ΙιΙ« at Law. the ever , Sing mc a son* oî a la·! 0»»' ·· K«nc· abeetia of two of it* ho hours a fall tackier hurl* "irnu Tas now.* largest grown. The acreagi regular players a* fortunate résulta un was the Counsellor cuul'l that 1»>I I ί brjng Ki'. ll. iit Kffwt. was increased out of all Sav, whoso were filled Mibstitutw, self forward in tbe effort to grasp him. suddenly pro Merrv of he *alle«l on a wo how wo are to win l.laces by case with the great musician. mains. μ soul, <lay "I don't Handel, uf ('hina run Μ»··κι» falls, ; Corm>i—ixteii· «- t>rw>a1rai atftVultura. to demands for it going Ho feels rather than hears the ruah of In the empire yon Κι ι»|Ία portion consumption, over the «a to Skye. seemed unable to «top the onward rush, an a to wQctUnl. A'Mrvw *11 ruMauitMUumli with the team in it* state—Fred Him resoluteness boy writ·* response to ill-advised from present feet behind bin own men extraordinary acr<*s some very odd things, lenie-l fur ihU b> Hkohi I).
    [Show full text]