Showing posts from December, 2021

CodeSnip 4.19.0 Released

I've just released v4.19.0 of CodeSnip. You can get it from GitHub . For the low down see the announcement on the CodeSnip blog.

Code Snippets Database HOTFIX 2.1.1 released

Embarrassed face emoji! Following the release of v2.1.0 of the Code Snippets Database  a few days ago, I've just run CodeSnip in the debugger only to find it was detecting and gently ignoring some errors when loading the release! So I've rushed out a hotfix: v2.1.1. If you followed my advise a few days back and updated to v2.1.0, you really need to get this hotfix. Grab it from the project's GitHub release page for hotfix 2.1.1 . Whoops!

Released v2.1.0 of the Code Snippets Database

Just completed v2.1.0 of the Code Snippets Database collection . This version tidies up the meta-data to make it more consistent and to leave behind some old legacy data that dates back to the CodeSnip program's early days. Also fixed some minor bugs and updated a few descriptions. No new snippets though. I advise any CodeSnip users to update since future CodeSnip releases will probably drop backwards compatibility with the now deprecated v2.0.x file format. Information on how to update can be found from within CodeSnip by choosing the Database | Install or Update DelphiDabbler Snippets Database  menu option. You can get the new version and read the full change log on the project's GitHub release page . Server Problems Resolved (well nearly)

At last the DNS record problem has been resolved (I hope). The problem was with my misreading some help on my domain provider's site and configuring the nameservers incorrectly. The correct nameservers have now been configured and are steadily replacing the incorrect ones around the world - we're getting about 85% coverage as I write this. Thanks are due to,  hostworld  tech support. Similarly the correct "A" records pointing to GitHub's servers are spreading at around the same rate, so hopefully by the end of today everything should be working normally. Changes with new server The primary, canonical, domain for the site is now . Unlike on the old server, https is enforced. Any URLs using the http protocol will automatically be rewritten to https . Further, the www sub-domain, while still supported, is rewritten without the www prefix before being resolved. Consequently the following addresses, will be rewritten as https ://delphida

Problems with server: 2021/12/12 update - Not For Sale!

UPDATE: This post has been superseded by this 2021/12/13 post . Difficulties with getting back on line are getting worse. Now,  you may be seeing this page if you try to access either or Firstly, I've not  surrended the domain name, and I haven't forgotten to pay the bills! I still own it. This problem affects because I've changed it to map to . The problem is therefore with the domain and could be one of two issues: The change I made to the nameservers to reference GitHub Pages seems to be propagating very slowly  or There's a problem at my domain hosting company - there's a DNS error being reported that I don't understand and that I'm trying to get tech support to address. Unfortunately it looks like the site won't be available for at least another 24 to 48 hrs. Could even be worse if the suspected DNS problem is real and can'

Problems with server: 2021/12/10 update

UPDATE: this post has been superseded by this  2021/12/13 update . Following on from yesterday's post I have decided to move to a new server. Since I develop the website on GitHub, and the site is to all intents and purposes mirrored on GitHub I'm changing my DNS record to use as custom domain for All the content is already there leaving me nothing left to move. While we're waiting for the changes to propagate, & (and their http:// equivalents) could lead you to either the old or new servers. You can tell which because pages served from the old server have a great big yellow warning displayed at the top of each page, while pages served from GitHub Pages don't have the warning (but may have a red cookie message pop up). Help Needed If, by 12:00 UTC tomorrow (2021/12/11) you're still seeing the old server, I would be very grateful if you wo

Problems with server

UPDATE: this post has been superseded by this 2021/12/13 update . I'm experiencing problems at the web server (404 errors where none existed previously, for e.g.) and cannot contact the hosting company to try to resolve it. Until I can sort out a new host, please use the mirror site at I may end up pointing at the GitHub Pages site permanently if I can't resolve this issue. Watch this space.

Things I like about Pascal [part 1]: == ≠ =

One of the things that pleases me no end about Pascal , like Algol before it, is its use of =  to mean = , and  not  as an assignment operator. For that we have := . Dunno if it's my maths background, but I find languages that use the equals sign as an assignment operator to be really, really annoying. Now good old BASIC gets it right, in that it uses  =  to test for equality but combines =  with the  LET  prefix for assignment. As in : LET x = 42 You know, just like you do in maths . Except that many BASIC implementations make LET  optional! But in the curly brace languages (and others), the misuse of =  irritates me beyond reason. Especially so when they then go and define == to mean "is equal to" when there's a perfectly good = sign just begging to be used. I find this ridiculous - and I'm in good company: A notorious example for a bad idea was the choice of the equal sign to denote assignment. It goes back to Fortran in 1957, and has blindly been copied by

404 errors on Articles pages fixed

Last week I noticed that accessing any of the articles on from the Articles menu resulting in a 404 error on the main site, while everything was OK on the GitHub Pages mirror I use for testing. I hate to imagine how long it had been broken. Anyhow a simple tweak to the .htaccess file seems to have fixed things. A forced page refresh may be needed if the error persists.