One problem with both Ruby’s #dup and #clone methods is that they only provide shallow copying. That suffices for many purposes, but sometimes you want deeper copying. A pretty standard method for deep copying Ruby objects is to use the Marshal module’s #load and #dump methods:

    class Object
      def deep_clone
        Marshal::load(Marshal.dump(self))
      end
    end

As long the object in question is serializable and doesn’t have singleton methods installed, that works. The following is a very bare-bones first cut at another deep clone method:

    class Object
      def dclone
        case self
          when Fixnum,Bignum,Float,NilClass,FalseClass,
               TrueClass,Continuation
            klone = self
          when Hash
            klone = self.clone
            self.each{|k,v| klone[k] = v.dclone}
          when Array
            klone = self.clone
            klone.clear
            self.each{|v| klone << v.dclone}
          else
            klone = self.clone
        end
        klone.instance_variables.each {|v|
          klone.instance_variable_set(v,
            klone.instance_variable_get(v).dclone)
        }
        klone
      end
    end

Singleton methods are handled by #clone, and attributes are recursively #dclone‘d (as are elements of Arrays and Hashes).

Welcome to Siaris.net

Siaris.net is the public face of Siaris: Andrew Johnson’s software development, training, writing, and consulting activities. Utilizing a common weblog format, I will publish short and medium length articles on a variety of topics including: general programming and problem solving, object oriented programming, programming languages, teaching, and communication. Longer writings will be available under the Articles link in the navigation bar.

Siaris.net is not my personal blog (I may add one of those eventually), but a way to gather and make available both my older writings, and to add new articles. With that in mind, I’ve already converted 50 (of 89) short Perl articles (orignally published by ItWorld). Some writings are less suitable for blog publication for a variety of reasons — the Articles link in the navigation bar connect you other writings (a smallish regex tutorial for some of Perl’s additional RE features, and a link to the regex chapter of my book for starters).

Within the blog, the News category will relate information about various goings on at Siaris.net. The LanguageBits category will hold interesting bits on various languages (including how-to’s and small code examples). I expect to be adding other categories as this site evolves.

There is no feedback mechanism for articles at this time, but I am considering setting up either a comment forum or a wiki for such a purpose — possibly requiring login to discourage comment/content spamming. In the meantime, comments about this site, or any particular article can be sent directly to me via email (andrew@siaris.net). I hope you find this site useful and enjoy visiting from time to time.

  Best regards,
  Andrew L Johnson

The Map

Once I would go
to the edge of the map.
To the empty,
white
space.

To where there be dragons
and perils unknown.
One could fall off
edges of
worlds.

Now would I go
to the edge of the map.
To the swirling
black
hole.

Forever uncharted
to those left behind.
One could fall off
edges of
Time.

  — Andrew L. Johnson (1985)

Siaris — Simplicity, Clarity, and Vision — a little more of what the world needs today.

Complexity is the prodigy of the world. Simplicity is the sensation of the universe. Behind complexity, there is always simplicity to be revealed. Inside simplicity, there is always complexity to be discovered.   — Gang Yu

Siaris.net

Siaris.net is the public face of Siaris: Andrew Johnson’s programming, training, writing, and consulting activities. In keeping with the motto of simplicity, primary content is served in typical weblog fashion — simple to publish new articles and information, and simple for readers to browse, search, and subscribe. The focus is on content.

Siaris

Siaris provides software development, training, and consulting to developers, businesses, and individuals.

Software Development: 15+ years experience

Utilizing languages such as: C, Perl, Ruby, and Python (and others) in cross-platform web, database, and networking application domains.

Teaching: 8+ years experience

Including: introductory programming, introductory and advanced Perl, and undergraduate human osteology and anthropology labs.

Technical Writing:

Elements of Programming with Perl (Manning Publications: 2000)
Over 80 Perl Newsletter articles for ItWorld.
A handful of articles for the Linux Journal and Linux Gazette.

Contact Siaris

    contact@siaris.net      Siaris
                            263 Knightsbridge Drive
                            Winnipeg, MB   R2M 4K5
                            Canada

ItWorld is discontinuing the Perl newsletter, so this is my farewell article. That being the case, I decided to try to leave you with a few tidbits of wisdom and suggestions of where else to turn for help.

The first place to turn for help is perl itself — running perl with the -w switch and ‘use strict’ enabled will help you catch many little bugs, typos, and questionable practices.

    #!/usr/bin/perl -w
    use strict;

If you know your program will be used only with Perl-5.6 and later version you can use the ‘warnings’ pragma to turn on warnings instead of the -w switch (this pragma allows more control over warnings, see the ‘perllexwarn’ manpage for further information):

    #!/usr/bin/perl
    use strict;
    use warnings;

The perl distribution also comes with copious amounts of documentation that you can read via a browser (if the docs are installed in .html format), the unix ‘man’ utility, or the supplied ‘perldoc’ utility. The 3 major pages (documents) you should be familiar with are:

    perldoc perl     --> the intro perl documentation
    perldoc perlfaq  --> many frequently asked questions (and answers)
    perldoc perlfunc --> documentation on builtin functions

There are quite a few mailing lists you can participate in at various levels (including lists for beginners, module authors, specific modules or distributions, and even a ‘fun with perl’ list). Information can be found at:

    http://lists.perl.org/

The ‘use Perl’ site publishes news and informative tidbits (along with other features), perl.com also publishes articles on various themes and at various levels, and The Perl Journal (now part of SysAdmin magazine) is a very good print publication:

    http://use.perl.org/
    http://www.perl.com/
    http://www.tpj.com/

Join or start your own local chapter of a ‘Perl Mongers’ group by checking out this site:

    http://www.pm.org/

And, lastly, the Perl Monks site is a web forum for questions, answers, tutorials, and discussions on Perl related topics (there are quite a few very knowledgeable individuals there):

    http://www.perlmonks.org/

And, last but certainly not least, do not forget about CPAN (comprehensive perl archive network) — there are loads and loads of free modules there that you should not ignore. Everything from dealing with CSV files to networking to graphics manipulation (and a whole lot more) can be found therein. A few CPAN entry points:

    http://www.cpan.org/
    http://search.cpan.org/
    http://theoryx5.uwinnipeg.ca/CPAN/cpan-search.html

I have very much enjoyed writing these (80+) weekly articles, and I appreciate the numerous comments and suggestions I have received from many of you (even if I didn’t get around to writing on all of the suggested topics). Thank you and I wish you all the best of luck with your Perl programming and perhaps I’ll run into some of you in the future.

            Best regards,
            andrew

END

Perl has a special kind of block called a do-block (the ‘do’ keyword followed by a block). This kind of block can be used as a term in an expression, or it can take a statement modifier.

When used as a term, the result returned is the value of the last statement evaluated in the block (rather like a subroutine’s default return value):

    my $in = do{print "Enter a number:";<STDIN>};
    print $in;

The context of the return value is the context of the expression (in the above case, since we assigned to a scalar, scalar context). The above isn’t a terribly useful example — but what about when you want to localize a global for a limited scope? Consider reading in an entire file into a scalar (inside of a larger script where you don’t want to change $/ for the duration of the script):

    my $file = 'data';
    open(FILE, $file) || die "Can't open $file: $!";
    my $contents;
    {
        local $/;   # $/ is locally undefined
        $contents = <FILE>;
    }
    print $contents;

A simpler method using a do-block might be:

    my $file = 'data';
    open(FILE, $file) || die "Can't open $file: $!";
    my $contents = do{local $/;<FILE>};
    print $contents;

With a statement modifier, this kind of block allows for a ‘run at least once’ form of the while statement:

    my $rand = int(rand(10)) + 1;
    my $guess;
    do{
        print "Enter your guess: ";
        $guess = <STDIN>;
    } while $guess != $rand;
    print "Yes: the number is $guess";

This allows us to use what looks like an uninitialized value in the conditional — it works only because the condition is tested after each block (by which time the $guess variable has a value).

The do block is also convenient for switch or case like statement blocks:

    my $rand = int(rand(10)) + 1;
    {
        print "Enter your guess: ";
        chomp(my $guess = <STDIN>);
        $guess < $rand && do{print "Too low\n"; redo};
        $guess > $rand && do{print "Too high\n";redo};
    }
    print "You guessed it!\n";

These case like examples could easily be solved using other means (like standard if/else statements), this is just another example of TMTOWTDI (there’s more than one way to do it).

*****