Home Accessibility Courses Twitter The Mouth Facebook Resources Site Map About Us Contact
 
For 2021 - online Python 3 training - see ((here)).

Our plans were to retire in summer 2020 and see the world, but Coronavirus has lead us into a lot of lockdown programming in Python 3 and PHP 7.
We can now offer tailored online training - small groups, real tutors - works really well for groups of 4 to 14 delegates. Anywhere in the world; course language English.

Please ask about private 'maintenance' training for Python 2, Tcl, Perl, PHP, Lua, etc.
Town simulation - town type definitions
this example from a Well House Consultants training course
More on this [link]

This example is described in the following article(s):
   • New Lua Examples - for last weeks delegates - [link]
   • For Lua Programmers AND for Town Planners - [link]

Source code: towns.lua Module: U050
--[[
This file defines the table types and functions that can run
on those tables for two types of town - a growth town and a
stable town. Unlike Java, you can define multiple types in
the same file, and you would logically do so if they are always
going to be used in the same appliaction and maintained by the
same person / team.

In both table types in this file, we have provided functions
of the same name, meaning that our main code can simply ask
for (example) the growth factor for a town, and know that the
program itself will know WHICH growth factor algorithm to use
for that particular town - known in OO as "polymorphism"
]]


growth = growth or {}
stable = stable or {}
local meta_g = {}
local meta_s = {}

-- Define a new growth town

function growth.new(place,pop,tph, houseprice)
        -- save the data
        local town = {}
        town["place"] = place
        town["pop"] = pop
        town["tph"] = tph
        town["houseprice"] = houseprice

        -- The following add functionallity to a growth town
        -- Some of these routines are specific to a growth town
        -- but others are shared with a static town
        town["getfact"] = growth.getfactor
        town["addpeeps"] = addpeeps
        town["wastage"] = wastage
        town["change_house_prices"] = growth.change_house_prices
        -- As these are just references being copied, we do
        -- NOT have an efficiency problem!

        -- Also set the metatable so that our application can
        -- pick up underlying code to define other non-standard
        -- functionallity, such as how to add (merge) two towns
        -- as the grow into each other, and how to format them
        -- as a string when they are printed out
        setmetatable(town,meta_g)
        return town
        end

function stable.new(place,pop,tph, houseprice)
        -- A lot of common code with growth.new ...
        -- So perhaps a case for an internal shared function?
        local town = {}
        town["place"] = place
        town["pop"] = pop
        town["tph"] = tph
        town["houseprice"] = houseprice
        town["getfact"] = stable.getfactor
        town["addpeeps"] = addpeeps
        town["wastage"] = wastage
        town["change_house_prices"] = stable.change_house_prices
        setmetatable(town,meta_s)
        return town
        end

-- Differing algorithms defined

function growth.getfactor(self)
        return self.pop / self.houseprice / self.houseprice * (6 + self.tph)
        end

function stable.getfactor(self)
        return self.pop / self.houseprice / self.houseprice * (3 + self.tph)
        end

function growth.print(self)
        return string.format("%12s - %6d - %6s - %7d",
                self.place, self.pop, "FAST", self.houseprice);
        end

function stable.print(self)
        return string.format("%12s - %6d - %6s - %7d",
                self.place, self.pop, "STABLE", self.houseprice);
        end

function stable.change_house_prices(self,inc,out)
        factor = (out/inc) * (out/inc) + 0.02
        self.houseprice = self.houseprice * factor
        end

function growth.change_house_prices(self,inc,out)
        factor = out/inc - 0.01
        self.houseprice = self.houseprice * factor
        end

-- Shared algorithms defined
-- (but these should really be in a table of their own to avoid
-- namespace clutter!)

function addpeeps(self,extra)
        self.pop = self.pop + extra
        end

function wastage(self)
        self.pop = self.pop * 0.99
        end

-- Defining operations in the metatables - saying what to
-- run when we 'print' a town.

meta_g.__tostring = growth.print
meta_s.__tostring = stable.print


Learn about this subject
This module and example are covered as required on private courses. Should you wish to cover this example and associated subjects, and you're attending a public course to cover other topics with us, please see our extra topic program.

Books covering this topic
Yes. We have over 700 books in our library. Books covering Lua are listed here and when you've selected a relevant book we'll link you on to Amazon to order.

Other Examples
This example comes from our "this" training module. You'll find a description of the topic and some other closely related examples on the "this" module index page.

Full description of the source code
You can learn more about this example on the training courses listed on this page, on which you'll be given a full set of training notes.

Many other training modules are available for download (for limited use) from our download centre under an Open Training Notes License.

Other resources
• Our Solutions centre provides a number of longer technical articles.
• Our Opentalk forum archive provides a question and answer centre.
The Horse's mouth provides a daily tip or thought.
• Further resources are available via the resources centre.
• All of these resources can be searched through through our search engine
• And there's a global index here.

Web site author
This web site is written and maintained by Well House Consultants.

Purpose of this website
This is a sample program, class demonstration or answer from a training course. It's main purpose is to provide an after-course service to customers who have attended our public private or on site courses, but the examples are made generally available under conditions described below.

Conditions of use
Past attendees on our training courses are welcome to use individual examples in the course of their programming, but must check the examples they use to ensure that they are suitable for their job. Remember that some of our examples show you how not to do things - check in your notes. Well House Consultants take no responsibility for the suitability of these example programs to customer's needs.

This program is copyright Well House Consultants Ltd. You are forbidden from using it for running your own training courses without our prior written permission. See our page on courseware provision for more details.

Any of our images within this code may NOT be reused on a public URL without our prior permission. For Bona Fide personal use, we will often grant you permission provided that you provide a link back. Commercial use on a website will incur a license fee for each image used - details on request.

You can Add a comment or ranking to this page

© WELL HOUSE CONSULTANTS LTD., 2021: 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01144 1225 708225 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho

PAGE: http://www.wellho.net/resources/ex.php4 • PAGE BUILT: Sun Oct 11 14:50:09 2020 • BUILD SYSTEM: JelliaJamb