Inside Irie Tools Limited

Taking another look at supporting Amazon Web Services.

2010-09-01T20:24:00.000-05:00

I'm taking another look at supporting Amazon Web Services (AWS) with the next release of Irie Pascal.

So far (fingers crossed) things are looking good, I haven't seen anything that will make it really difficult to support AWS. I did discover that parts of Amazon S3 (the main AWS storage service) use something called "eventual consistency", which is a new concept for me. I will have to let this roll around in my head for a while before I know whether or not "eventual consistency" is going to be a problem. I found this article, Read-After-Write Consistency in Amazon S3 that explains the concept.

I'm excited about supporting AWS because it could make it easy and cheap to host applications built using Irie Pascal. Right now, it can be a little difficult to find a hosting company that will host Irie Pascal applications (unless you get a dedicated server).

Anybody out there, have any experience with AWS?

Irie Pascal 3 - August Progress Report

2010-08-27T18:51:00.000-05:00

The new IDE
The design work and the coding to change the current IDE, which is designed for compiling Pascal programs, into the new IDE, which is designed for creating websites (powered by Pascal programs), is going well. The core changes have already been made, the new IDE can:

Create a new website.
Open an existing website.
Create a new file.
Open an existing file.

The next big change is to add support for creating web pages (using Jump templates).

The new compiler
Some of the new compiler features, that I've been writing about, won't make it into the next release. The new release is taking much longer than I thought it would, so I will have to leave out some things. For example, support for Unicode, and support for compiling multi-module programs, will have to wait for a later release.

The idea is to focus the next release on making the transition from a Pascal programming tool into a website development tool, while making as few changes to the compiler as possible.

Until next time.

Irie Pascal 3.0. Adding support for multi-module programs.

2010-04-13T20:35:00.001-05:00

I'm currently working on adding support for writing multi-module programs. I've decided to support the Object Pascal syntax for this. If you're not familiar with this syntax (with UNITs and USES clauses) then please see chapter 3: Programs and Units in the Object Pascal Language Guide for a look at this syntax.

NOTE: Irie Pascal will NOT be able to use most units written for other compilers, and I am NOT planning to create units for Irie Pascal that are similiar to units available for other compilers.

I am planning to make sure that the units supplied with Irie Pascal don't have the same names as units available for other compilers (maybe I'll prefix the Irie Pascal unit names with "Irie"). So I'm leaving the door open for someone else to write units for Irie Pascal that are similiar to units available for other compilers. I'm not going out of my way to make Irie Pascal incompatible with other compilers (I don't like it when vendors do that), but I'm not making any heroic efforts to make it compatible either.

I'm adding a linker.
Right now, Irie Pascal doesn't use a linker, instead the compiler just generates executables directly from the source files. This is not difficult, because Irie Pascal builds each program from a single module, but building programs from multiple modules is much more complicated so I've decided to build programs in two phases.

A compile phase. In this phase the compiler generates intermediate object files from the source files.
A link phase. In this phase the linker generates an executable object file from all of the intermediate object files in the project.

Adding support for multi-module programs

Already done

Design a new object file format. All of these changes to Irie Pascal mean that a new object file format is necessary.

To be done

Switch over to the new object file format. Which means updating Irie Pascal to compile existing (single-module) programs in two phases and generate files in the new format).
Test the updated Irie Pascal.
Add syntax-only support for multi-module programs (i.e. update Irie Pascal to recognize the new multi-module syntax but don't generate any code for it yet).
Gradually add full support for multi-module programs (i.e. gradually start generating code for each piece of the new multi-module syntax).
Add new programs to the Irie Pascal test suite (to test the new syntax).
Done.

Irie Pascal 3.0. Added support for HTMLHelp.

2010-04-13T18:54:00.000-05:00

Work on the next release of Irie Pascal is continuing.

I have finished adding support for HTMLHelp (the newer Windows Help format that replaces WinHelp). Irie Pascal now includes both WinHelp and HTMLHelp versions of the online help manuals. The HTMLHelp versions are used when Irie Pascal is run on Windows 2000 or later, while the WinHelp versions are used on earlier versions of Windows.

A web programming section has been added to the new Irie Tools website.

2010-02-22T19:03:00.000-05:00

I just finished adding a new secton to the new Irie Tools website:

Irie Pascal web programming

Ok, this "new" section is not really new (it's just a slightly updated version of the Common Gateway Interface (CGI) section from the old website), but it's still a good introduction to CGI.

The new Irie Tools website is live.

2010-02-18T16:06:00.008-05:00

All of the new pages were created with Jump (the web template technology I've been working on), and so far so good. I'm now going to use Jump to redo some more pages from the old website. This time I'll redo the pages about web programming with Irie Pascal, using the Common Gateway Interface (CGI).

The new website is still at: http://www.irietools.com/ (I've just added some new pages and updated some of the existing ones).

New look for IrieTools.com

2010-01-15T18:00:00.000-05:00

I've been working on a new look for the Irie Tools website. I have a demo of what the new front page will look like at the address below. Please note that only this page has been done, so the links on this page either don't point anywhere or they point at old content that will be removed or updated.

Address of new page: www.irietools.com/demos

This is actually my second try at creating a new look for the Irie Tools website. I got some very useful feedback from my first try, which I've used to make a second attempt.

What do you think about the new page?

A preview of the new Irie Tools website (created with Jump).

2009-12-22T18:20:00.000-05:00

I have been using Jump to create the new Irie Tools website, and it's looking pretty good. So far I have completed the new home page, which you can see at the address below:

http://www.irietools.com/demos/

NOTE: Only the home page is done, so the links don't go anywhere.

As a result of my ... ahhh, how to put this kindly ... limited design skills, it has taken a long time to complete the home page, but I'm excited by the results, and Jump is working perfectly so far.

Your comments on the new home page would be greatly appreciated.

The First Jump Template.

2009-11-19T19:14:00.000-05:00

I have finally finished the first actual real-life Jump template. It's written using XHTML 1.0 Strict, and I've validated it with the W3C Markup Validation Service.

So now that I have a Jump template, I'm planning to use it to redo the Irie Tools website. I'm guessing that I will have to make some minor changes to the template, but I don't expect any major changes.

I've put the template on the Irie Tools website for anyone who is interested (the link is below):

First Jump Template

By the way, this is just a template, so the the text is just made-up. and links and buttons just go to the home page.

Jump first, ask questions later (sorry, I know that was corny but I couldn't resist).

Stuart
This Blog: Inside Irie Tools Limited
Website: Irie Tools Limited

Jump to the Rescue - an easy way to generate web pages

2009-11-04T20:30:00.000-05:00

The Problem
Right now Irie Pascal does not provide an easy way to generate web pages, you have to use a writeln to output each line of the page. There is no way to add a web page to an Irie Pascal program without manually converting the page into a series of writeln's.

The Solution
The solution that I have come up with is a very simple language, which I'm calling Jump for the time being. Jump is so simple that I don't even know what to call it (it only has five keywords: jump, var, page, css, end). Anyway, it's simple enough that I designed it and wrote an implementation in a little over a week. I'm going to bang on the implementation a bit more before releasing it. Right now, I'm using it to redo the Irie Tools website. When that is done it should be ready for release.

In the meantime, here is a sneak preview of Jump

//Hello world Jump Program
jump
var
   //Define one variable called "message" with the value "Hello World!!!".
   //NOTE: Your program can easily change the value of the variable
   //             and thereby change the page generated.
   message
      Hello World!!!
   end message
end var
page<html><head>
<title>
   <?jump !message ?>
</title>
</head>
<body>
   <p>
    <?jump !message ?>
   </p>
</body>
</html>
end page
end jump

As you can see, most of the program is taken up by the web page. However I think in most case, you would put the page in a seperate file. So if you removed everything between the page and the end page, and put it in a file called hello.html then the program is greatly simplified as shown below.

jump
var
   //Define one variable called "message" with the value "Hello World!!!".
   //NOTE: Your program can easily change the value of the variable
   //             and thereby change the page generated.
   message
      Hello World!!!
   end message

end var
!page hello.html
end jump

Welcome to Inside Irie Tools Limited.

2009-10-20T18:18:00.000-05:00

What is Inside Irie Tools Limited?
Inside Irie Tools Limited gives you a look behind the website at what is going on inside Irie Tools as well as an outline of what is planned for the future. The main reason for creating this blog is to help answer questions like:

What kind of company is this really?
Who are the people behind the company (or for right now, who is the person behind the company)?

You won't find too much product or technology details here (those details will will be covered by product specific blogs, the first of which has just recently been launch, Web Programming in C).