The Script Meridian globe mark Script Meridian A community of Frontier
and Radio users
Community

The list is still open

Quieter than 2002 — a few dozen messages a month — but the people answering are the people who wrote the tools. Read before you post; nobody minds a beginner, everybody minds a vague one.

Today’s messages

operations · André Radke · 4 hours ago

Agents that fire twice after a clock change

Daylight saving moved and two nightly agents ran again at 01:30. Is anyone normalising to UTC before scheduling, or is there a cleaner idiom?

migration · Marta Lenz · Yesterday

Reading a 2003 ODB on a modern machine

Inherited a database from a retired colleague. It opens, but half the outlines render as one long line. Encoding, or something structural?

performance · Seth Dillingham · 3 days ago

in-place append: does it still apply?

Short answer, yes, and the measurements are in the new article. Longer answer in the thread.

How a thread reads

performance · Seth Dillingham · 3 days ago

in-place append: does it still apply?

Yes. The optimisation is a property of how the runtime handles a string that has exactly one reference, and that has not changed. What has changed is that machines are fast enough to hide the problem until your input grows.

Concatenating 40,000 short lines the naive way moved 3.1 GB through memory. The in-place form moved 41 MB.— measured on the same machine, same build

The full write-up, with the measurement harness, is in Optimal String Concatenation in UserTalk.


reply · Marta Lenz · 2 days ago

Confirmed on our export job. Twelve minutes down to nineteen seconds, and the change was four lines.

Start a thread

Posting is open to members. The preview below updates as you type — the list is plain text, so what you see is what everyone gets.

Never shown on the list; used only to confirm the post.
0 / 4000 characters
Plain-text preview

House rules

  1. Say what you already tried. “It doesn’t work” costs the list three messages before anyone can help.
  2. Include versions. Runtime, operating system, and the release of any suite involved. Behaviour differs across all three.
  3. Paste the actual error. Not a paraphrase, and not a screenshot of text.
  4. One subject per thread. If the conversation forks, start a new one and link back.
  5. Be decent. Disagreement is welcome; condescension is not. The list has beginners on it by design.
  6. No recruiting or promotion outside the monthly open thread.
  7. Post the answer. If you solve it yourself, come back and say how. That is what makes the archive worth searching.

Join the list

Membership is free. Subscribe with the form in the footer, or write to the editors and we will add you by hand. You can leave at any time with a single email, and the privacy policy explains exactly what we hold.

Write to the editors Browse the catalogue first