Skip to main content

Lazy Fibonacci Array

What’s the 1,337th number in the Fibonacci sequence? It’s 1.1667830241021E+279, of course!

Here’s an cool snippet of PHP code I wrote several months ago which implements not only PHP’s Iterator interface to provide an lazily-iterable list of Fibonacci numbers, but also the ArrayAccess interface and some fancy math to provide indexed access, too. Lazy evaluation is pretty cool because it saves memory. In this case, in effect you have an array of 1,478 of elements (bound only by the capacity of float values) while only using 984 bytes of memory for the object:

<?php
class Fibonacci implements Iterator, ArrayAccess
{
    const PHI = 1.618033989;

    private $a;
    private $b;
    private $i;

    public function __construct() {
    }

    public function rewind() {
        $this->a = 1;
        $this->b = 0;
        $this->i = 0;
    }

    public function current() {
        return $this->b;
    }

    public function key() {
       return $this->i;
    }

    public function next() {
        $this->i++;
        $tmp = $this->a + $this->b;
        $this->a = $this->b;
        $this->b = $tmp;
    }

    public function valid() {
        return $this->offsetExists($this->i);
    }

    public function offsetExists($i) {
        // Fib(1476) = float(1.30698922376E+308)
        // Fib(1477) = float(INF)
        return $i > -1 && $i < 1478;
    }

    public function offsetGet($i) {
        // en.wikipedia.org/wiki/Fibonacci_number#Computation_by_rounding
        return floor((pow(self::PHI, $i) / sqrt(5)) + 0.5);
    }

    public function offsetSet($i, $val) {
        throw new Exception("sequence is read-only");
    }

    public function offsetUnset($i) {
        throw new Exception("sequence is read-only");
    }
}

$mem = memory_get_usage();
$fib = new Fibonacci();

echo "Memory used for Fibonacci object: " . (memory_get_usage() - $mem) . "\n";
echo "The 1337th number in the sequence is: " . $fib[1337] . "\n";

echo "Here is the sequence:\n";
foreach ($fib as $i => $f) {
    var_dump($f);
}

Comments

Popular posts from this blog

Composing Music with PHP

I’m not an expert on probability theory, artificial intelligence, and machine learning. And even my Music 201 class from years ago has been long forgotten. But if you’ll indulge me for the next 10 minutes, I think you’ll find that even just a little knowledge can yield impressive results if creatively woven together. I’d like to share with you how to teach PHP to compose music. Here’s an example: You’re looking at a melody generated by PHP. It’s not the most memorable, but it’s not unpleasant either. And surprisingly, the code to generate such sequences is rather brief. So what’s going on? The script calculates a probability map of melodic intervals and applies a Markov process to generate a new sequence. In friendlier terms, musical data is analyzed by a script to learn which intervals make up pleasing melodies. It then creates a new composition by selecting pitches based on the possibilities it’s observed. . Standing on Shoulders Composition doesn’t happen in a vacuum. Bach wa

Learning Prolog

I'm not quite sure exactly I was searching for, but somehow I serendipitously stumbled upon the site learnprolognow.org a few months ago. It's the home for an introductory Prolog programming course. Logic programming offers an interesting way to think about your problems; I've been doing so much procedural and object-oriented programming in the past decade that it really took effort to think at a higher level! I found the most interesting features to be definite clause grammars (DCG), and unification. Difference lists are very powerful and Prolog's DCG syntax makes it easy to work with them. Specifying a grammar such as: s(s(NP,VP)) --> np(NP,X,Y,subject), vp(VP,X,Y). np(np(DET,NBAR,PP),X,Y,_) --> det(DET,X), nbar(NBAR,X,Y), pp(PP). np(np(DET,NBAR),X,Y,_) --> det(DET,X), nbar(NBAR,X,Y). np(np(PRO),X,Y,Z) --> pro(PRO,X,Y,Z). vp(vp(V),X,Y) --> v(V,X,Y). vp(vp(V,NP),X,Y) --> v(V,X,Y), np(NP,_,_,object). nbar(nbar(JP),X,3) --> jp(JP,X). pp(pp(PREP,N

What's Wrong with OOP

Proponents of Object Oriented Programming feel the paradigm yields code that is better organized, easier to understand and maintain, and reusable. They view procedural programming code as unwieldy spaghetti and embrace OO-centric design patterns as the "right way" to do things. They argue objects are easier to grasp because they model how we view the world. If the popularity of languages like Java and C# is any indication, they may be right. But after almost 20 years of OOP in the mainstream, there's still a large portion of programmers who resist it. If objects truly model the way people think of things in the real world, then why do people have a hard time understanding and working in OOP? I suspect the problem might be the focus on objects instead of actions. If I may quote from Steve Yegge's Execution in the Kingdom of Nouns : Verbs in Javaland are responsible for all the work, but as they are held in contempt by all, no Verb is ever permitted to wander about