|
|
|
Too busy visiting Tulip island: https://photos.app.goo.gl/aEcjbgrkMvV5C3cT6
|
|
|
|
|
Love it. Great wake up!
A little time, a little trouble, your better day! (BF)
|
|
|
|
|
Wordle 308 X/6
⬛⬛🟩⬛🟩
⬛⬛🟩⬛🟩
⬛⬛🟩⬛🟩
⬛⬛🟩⬛🟩
⬛⬛🟩🟩🟩
⬛⬛🟩🟩🟩
You win some, you lose some!
|
|
|
|
|
Looks like you're playing hard mode and a truly nasty word showed up.
|
|
|
|
|
Without setting hard mode on, I play by the rules of hard mode.
After the 4th attempt, I wondered if I should use the strategy of trying to eliminate letters by choosing words that may not have known letters in them but decided against it.
O, live and learn!
|
|
|
|
|
Wordle 308 3/6*
⬜🟨⬜🟨⬜
⬜🟩🟩⬜🟩
🟩🟩🟩🟩🟩
It depends a lot on the first word - I choose a different word every time mostly, but make sure there are either 2 vowels, or, at least 1 vowel and 1 common letter.
Happiness will never come to those who fail to appreciate what they already have. -Anon
|
|
|
|
|
I usually choose different starting words each day. Today, it was SPIRE.
|
|
|
|
|
That's probably a spoiler - and should be labeled as such in the subject?
Personally, I'm glad I didn't see that before I try for myself - it would have annoyed me to have been "given" two letters.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I agree. No clues please. I also had completed before reading, but would have been annoyed by this - and also the original post.
|
|
|
|
|
Wordle 308 4/6*
⬜⬜⬜⬜⬜
⬜⬜🟩⬜⬜
⬜⬜🟩🟨⬜
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 308 4/6
⬜⬜🟩🟨⬜
⬜🟩🟩⬜🟩
⬜🟩🟩⬜🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 308 4/6
⬜⬜🟩⬜🟩
⬜🟨⬜⬜⬜
🟩⬜🟩🟩🟩
🟩🟩🟩🟩🟩
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Three today:
Wordle 308 3/6
⬜🟨⬜🟨⬜
🟩🟩⬜🟨⬜
🟩🟩🟩🟩🟩
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Wordle 308 4/6
⬛⬛⬛⬛🟩
⬛⬛🟩⬛🟩
⬛⬛🟩🟨🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 308 4/6
⬛⬛🟩⬛⬛
⬛🟨🟩⬛⬛
⬛🟩🟩⬛🟩
🟩🟩🟩🟩🟩
Get me coffee and no one gets hurt!
|
|
|
|
|
Wordle 308 4/6
⬜⬜🟩🟨⬜
⬜⬜🟨⬜🟩
⬜🟨🟩🟨🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
I got bored with the game.
I use the same starting words:
lower
quips
ketch
mangy
It covers MOST the letters, leaves me 2 guesses. Catches Common Endings
I have a couple go to words (bifid) to catch b/f/d (love how it lights up for bread)
the hardest words turn out to be doubled letters.
I end up sitting down with a piece of paper for the last 2 if it is not obvious.
But it usually comes to me. Having played a lot of word games, once you get the right letters.
The word usually comes out. Although I have had a couple of times where it's an anagram of 2-3 words. Ouch!
PS: is there a way I can replay THAT game? (forgive the ignorance)
|
|
|
|
|
The prospect scares me, because 99 times out of 100 if something isn't being done in C++ by others it's either because it is and I just wasn't aware of it, or it isn't because it's an anti-pattern.
GFX is basically one big selector.
What it does is take usually two different things at compile time, and based on their on respective capabilities, it will perform the operation you gave it differently. For example, a raw bitmap exposes its memory directly through begin() and end(), but a display device cannot since it's connected over a bus. It however, has ways to do DMA transfers, so it supports methods like copy_from and copy_to potentially which can copy a window of pixels from or to the display. Failing that, there's always reading and writing individual pixels, but that is the last resort.
What happens is this - at compile time
Operation+CompileTimeArguments+DrawDestination(maybe +DrawSource) = Signature
That selects different code paths based on different capabilities of the draw source and destination, the operation, and the arguments. At compile time. In doing so it basically legos code together to make an efficient code path for performing the operation with the given arguments.
The templates to make this happen are a mess, but I don't know how else I can achieve the sort of flexibility and efficiency I enjoy with this technique.
It's amazing. It's also probably incomprehensible if you didn't write it, but thus far I've been able to maintain it for a year as it has grown and evolved. The architecture remains the same.
I don't know what to call this technique "multiplexing code selection?" ack.. no matter what it's a mouthful, but one of the problems with it is it creates an exponentially larger test matrix as you add more compile time variation.
It strikes me as an anti-pattern maybe, but I refuse to accept that absent an alternative to accomplish what GFX does.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Would doing it at run-time be preferable? Sounds like not.
|
|
|
|
|
It's not practical, and in some cases I don't think it's possible? I'd have to think around too many corners right now to be sure of that last bit.
I like the way I'm doing things, but if there's a better alternative I'll take it, particularly where maintenance is concerned. It's hard to even get the compiler to instantiate all of my templates and thus compile all of it, much less test it at run time. I've run into compile errors on versions I've released (early on, but yikes).
To err is human. Fortune favors the monsters.
|
|
|
|
|
Back in the days before the craze of header only libraries, we used to have statically linked libraries and you would use one such library for for your specific hardware.
Frankly, I see no merit in having some humongous headers that could work on 100 devices as long as I'm going to use it with just one display adapter. It seems to me you are forcing your users into un-needed complexity with the dubious benefit that you have a single code base.
Might sound harsh, but it's written with best intentions in mind
Mircea
|
|
|
|
|
You can't export templates from a static library and I can't do what I'm doing without templates.
And the actual display drivers ship separately.
The adaptability that I mentioned in my post prior is so I can use any given display driver as efficiently as it allows for.
Edit: My library contains several headers, but it does things like True Type fonts, and JPGs. I can't practically put that all in one file unless I get the computer to help me merge working files and I don't see the point. It's a lot in there is my point here, but the drivers themselves are relatively simple.
To err is human. Fortune favors the monsters.
modified 23-Apr-22 16:44pm.
|
|
|
|
|
honey the codewitch wrote: It strikes me as an anti-pattern I'm not fond of the phrases "anti-pattern" or "code smell", because all too often they are used to criticize code without knowledge of the constraints and compromises that went into writing it. Fortunately you document very actively.honey the codewitch wrote: The templates to make this happen are a mess, but I don't know how else I can achieve the sort of flexibility and efficiency I enjoy with this technique. My experience with templates (and their predecessor, #define macros) is that their capability needs to be matched by documentation that explains why they are defined and used in a particular way, and how they contribute to the problem solution. This need is far greater than that for ordinary code. It's especially true for templates given that even today compiler diagnostics for them usually have a lot of 'cognitive distance' between the problem and the actual cause in the source.
Software Zen: delete this;
|
|
|
|