The Shape of Code

This week I was on a virtual meeting of IST/5, the BSI committee responsible for programming language standards in the UK. It’s been three years since I last reported on the programming language standards’ world, what has been going on?

tl;dr: Business as usual, with a handful of active committees.

I have been meeting secretary for the last few years, and sometimes struggle to write something in the minutes, other than: “The document was noted”, or “No action”. IST/5 is a management committee whose job is to check that the various programming language panels/committees (who do the technical work) follow the procedures. When experienced people are chairing the technical work, procedures are followed, and IST/5 get to tick a box.

The latest revision of C was intended to be published in 2023, hence the commonly used name C23, but slipped to 2024, and there are people who refer to it as C24. The plan is for the next revision to be published in 2028. Over the last few years there has been a significant increase in proposals for new languages features. C has started to follow in the footsteps of C++ (the committee is currently an order of magnitude smaller), attracting bored consultants looking for a creative outlet.

The ISO C++ committee acquired a new chief sheep herder, who has been restructuring the organization of the committee, which had outgrown its previous way of working.

The C++26 document is out for balloting by SC22‘s 28 P-member countries. It’s possible that this vote will fail (people in various National bodies are canvassing for No votes). The sticking point is contracts, which was removed from the C++20 draft to enable it to progress, and did not make it into C++23. Stroustrup, voted against the proposal, and has said (53 minute mark) “…it’s claimed to be a minimal viable product. It’s not minimal, it’s not viable.” The ballot closes on 27 September.

BSI is active on the climate bandwagon, and is constantly reminding its committees about the London Declaration (net-zero, etc). What can a programming language standards’ committee do to reduce emissions and cut electricity use? There have been various studies comparing the electricity consumed by different language constructs. I have not written about them on this blog because they were either poorly run, or the results were essentially noise. Interpreted languages obviously consume more electricity than compiled languages. However, none of the three languages within SC22 that are commonly interpreted (WG8 BASIC, WG16 ISLISP, and WG17 Prolog) are actively being worked on.

Programming language standards were among the first to support the non-8-bit character sets (SC2 Coded Character Sets). Andrew West was an active member of SC2 and attended IST/5 meetings to report what was going on. Andrew died towards the end of last year, and has an obituary in The Guardian.

At the start of the year BSI moved to new headquarters in Covent Garden, about 100 yards up the road from the Royal Opera House/Royal Ballet. A rather different ambience than an office block above Gunnersbury underground station (which is being converted to flats). This week’s IST/5 meeting was intended to be hybrid, to have a chance to meet new faces (and check out the plush new offices). However, BSI’s net-zero rules restrict us to online only; no BSI tea and biscuits for us 🙁 I walked past the building one evening a few weeks ago, and pressed by nose against the door, but could not see any BSI signage through the tinted glass.

UK based readers can apply to join a panel. Existing panel members are emailed the CV of applicants, and asked if “… applicant’s knowledge would be beneficial to the work programme and panel…”. Anybody can join the US Standards body, INCITS, by paying an annual fee for membership of a language committee ($1,530/$2,703).

INCITS recently introduced a new rule which prevents its members being a member of any corresponding National committee: “However, Individuals who are participating as members of other National Bodies (NBs) for an International Technical Committee (TC) or Subcommittee (SC) are not permitted to participate in INCITS IOEs responsible for the same international standards activities. This is to ensure the confidentiality of the USNB discussions and positions and to avoid conflict of interests.”