Evalution Principle
Username:  
Password:
  > Home
> User Guide
v Reference
    v Introduction
       o How to use this doc
       o Background
       v Design Principles
          o Black-box Principle
          o Generosity Principle
          o Evalution Principle
       o Characterising BEE
       o How BEE runs
       o What is a BEE Web Site
    > CROFT
    > BEE Variables
    > BEE Syntax
    > BEE Commands
    > Database Operation
    > Content Management
    > Objects and Classes
    > Interface with others
    o Glossary
> Portal Object
> Development Guide


Shortcuts
sys Class
debug Class
Intrinsic Conversions
>> Reference >> Introduction >> Design Principles >> Evalution Principle <=  =>      <  1  >  
The Evalution Principle

Software is a living thing.  Applications change to their environment and requirements.  Changes cause pain, especially among component interfaces.  Some how, the structure of position independent name-value pair gives flexibility in interface design, because:

  • The caller is allowed to omit arguments, so that it will not fail when new arguments are introduced.  (The callee function will take the default for missing arguments.)
  • The caller can omit all arguments and let the callee function to find out from the html form.  (This point was in OLDPAL.  In BEE Script, form variable is only one of many ways to pass arguments.)

Future development of BEE will aim at distributed processing and in particular focus on Web Services technology.  Software components may run on remote machines and common standards like XML and SOAP are being used across the net.

 

Previous Page       Next Page

Accsoft Computer Technology Pty Ltd     ABN: 98 065 617 549
PO Box 892, Epping NSW 1710         Level 1, Epping Office Park, 242 Beecroft Rd, Epping NSW 2121, Australia
Tel: Sydney - (02)98691668     National - 1300-881668         Fax: (02)98691866
© Copyright 2003 Accsoft Computer Technology Pty Ltd