In Word VBA, calling
doc.Paragraphs(idx) to get a paragraph by its index is very slow. Instead, once you have a
Paragraph object, use
para.Previous to navigate, and your code will be much faster! I just refactored an old routine this way and received a dramatic speedup.
doc.Paragraphs() must be iterating through the document starting from the beginning, but I don’t know that for sure. I do know that adding paragraphs before the region my code was working with made the code run perceptibly slower, even though the code was never touching the added paragraphs.
Here are some simple helpers, in case you want to manually check for errors rather than throwing when you run off the end of the document:
Private Function NextParaOrNothing_(p As Paragraph) As Paragraph
Set NextParaOrNothing_ = Nothing
On Error Resume Next
Set NextParaOrNothing_ = p.Next
End Function 'NextParaOrNothing_
Private Function PrevParaOrNothing_(p As Paragraph) As Paragraph
Set PrevParaOrNothing_ = Nothing
On Error Resume Next
Set PrevParaOrNothing_ = p.Previous
End Function 'PrevParaOrNothing_
It’s the reference implementation of the Raku programming language. https://rakudo.org/
The installer ran very quickly and the REPL worked out of the box. Nothing else to report yet, but I’m sure I’ll have more to say in the future.
Updated 1: Rakudo won’t build from source on Cygwin because libuv is still a bit dicey there. However, cascent/neovim-cygwin looks like a promising step forward.
Should I be worried? The three most-disliked programming languages in Stack Overflow’s latest blog post are Perl, Delphi, and VBA. And those three languages all have a special place in my heart. Oops…
Perl I have been enjoying recently and VBA is most of my day-to-day coding (since what they actually pay me for is driving MS Office). Delphi remains the only piece of software I have ever bought based on one marketing presentation. After QBASIC, I moved up to Turbo Pascal 6. When Delphi came out, I only had to see it on screen to be hooked.
Delphi is also what taught me that the magic in a toolchain is really the linker. As I was learning C, I was able to write Windows programs using my DOS version of Turbo C++, linked with the Delphi linker.
Excerpts from Stack Overflow’s analysis follow.
Edit: For the “welcome to Stack Overflow” bookmarklet, go to this jsFiddle, hit Run, and then drag the resulting link to your bookmarks bar.
A custom tea timer for https://smithtea.com/pages/know-your-tea#brewing-instructions:
A message I have found myself typing frequently on Stack Overflow: 🙂
As compressed by https://jscompress.com/; non-minified is:
var qsel = document.querySelector.bind(document);
var edit_link = qsel('.edit-post');
var add_comment = qsel('.js-add-link.comments-link');
var textbox = qsel('textarea[name="comment"]');
"Welcome to the site! Check out the [tour](https://stackoverflow.com/tour) "+
"and the [how-to-ask page](https://stackoverflow.com/help/how-to-ask) for "+
"more about asking questions that will attract quality answers. You can "+
"[edit your question](" + edit_link.href + ") to include more information."
textbox.scrollTop = textbox.scrollHeight;
These are the first two I have written. I hope they are useful to you, or serve as helpful examples if you are writing your own bookmarklets!
This handy file-renaming script at Perl Monks has source code with red “+” marks marking wrapped lines. I pasted it into Vim and wanted to wrap those lines back to the way they should be. After a bit of fiddling, I got:
:g/^+/execute "norm 0x" | .-1,.j!
The `g/^+/’ finds the lines beginning with a “+”. Then the `execute “norm 0x”‘ deletes the “+” (“0” moves to beginning of line; “x” deletes), “|” marks the next command, and `.-1,.j!’ joins (“j”) the current line (“.”) with the previous line (“.-1”) without whitespace (“!”) added between the lines.
I leave it to you whether I have too much time on my hands.
Technology makes our lives better to the extent we don’t have to think about it. Robert Pirsig makes this point in Zen and the Art of Motorcycle Maintenance, and it’s still true: technology that draws attention to itself has failed (except to a very hard-core audience of which I am probably part 😉 ).
For the last two years, I have been using Google Chrome to view PDFs at work. Dozens a day, usually with at least five open at a time. For the last two years, every time I have rotated the view clockwise or counterclockwise, my page has shifted off-screen and I have had to scroll to get back to it. Has that stopped me from doing my job? No. Has it drawn undue attention to the underlying technology? Yes. Very yes.
I cannot express my delight at finding, after a recent Chrome update, that I wasn’t the only one with this problem — and that it has been fixed! I rotated my PDF and reached for the scrollbar, but then I noticed the underlying technology in a good way: I was still looking at the same page I had been. Now each day is a bit smoother, and my job is a bit easier, because the fix has reduced, rather than increased, my mental workload.
My sincere thanks to everyone involved in pdfium bug 116297. Special thanks to thestig at chromium.org for making the fix! If you read this, thestig, please know you have succeeded.
Note to programmers: sometimes small fixes are big wins. It took thestig two lines of code to save me several minutes of wasted effort per work day, every work day, possibly for the rest of my career. Fix the small things — your users will thank you!
Every piece of technology is built to work provided its assumptions hold. Every piece of electronics, for example, assumes it will have power. No power => no function (as famously noted by The IT Crowd). By breaking those assumptions, you can do some amazing things:
In this video (~36 min), scanlime finds exactly the right microsecond to drop the power supply — just enough! — to cause the processor built into a graphics tablet to dump its entire memory over a USB connection. This is not a function the tablet was supposed to provide!
By painstakingly, scientifically defeating the assumption of a stable power supply, the tablet’s firmware control program, intended to be kept within the tablet, becomes available to inspect. And, as scanlime points out at the end of the video, that control program may well open other doors. Analyzing the control program may reveal other assumptions the tablet makes — assumptions that can be broken to change the tablet’s function to what she wants it to be.
Every system is only functional, secure, reliable, or any good at all, as long as its assumptions hold. Whenever you think about the latest gizmo, don’t just ask what it will do for you. Ask what it won’t do for you when you least expect it — when the gizmo assumes wrong.