That sort of approach works for some very simple instruction encodings, but doesn't really handle:
1) instructions which "bend" the format, like ARM instructions such as STMIA or B which combine multiple fields to make a larger immediate value or mask.
2) recognizing instructions which use special values in fields (like ARM condition = 1111) to represent a special instruction.
3) instruction encodings with split fields, like the split immediate in RISC-V S-type instructions.
4) instruction encodings which have too many instruction-specific quirks to fit into any reasonable schema, like 68000.
parse_url() also had no generate_url() counterpart - sure, it could (sometimes) split a URL into its components, but there was no safe way to modify those components and glue them back into a string. The new URI class solves that.
Not that anyone's even bothered knocking off their current generation products. The majority of Arduino clones are still using AVR or occasionally SAMD processors - Arduino's newer boards were never really accepted by the community. Some makers have even gone another direction entirely - ESP32-based development boards are popular, and there's a compatibility layer for using the Arduino IDE with those.
A quick google will show you that it was. I remember because I was in college at the time and that's how I learned what a Beowulf cluster was. Maybe PS3 was more successful or more popular, but there were definitely PS2 clusters.
Go! wasn't even published as its own project [1] until 2015, well after Go(lang) was available. It previously existed as an unpublished CVS repository in an obscure Sourceforge project [2]; I can't fault the Go developers for ignoring or overlooking it. You can find a circa-2002 version of Go! in the archived CVS repository of the Sourceforge project, but none of the project's release files appear to contain it.
(Ignore the "Last Update: 2013-09-06" on the project page - that's the date that SourceForge performed an automatic migration. Any real activity on the project seems to have petered out around 2002, with one final file released in 2003.)
Due diligence would have revealed the Go! project in a standard literature review.
I can and will fault the developers because even if they had overlooked it, they were explicitly asked, and declined to do so because they determined (themselves) there would be no confusion. So it wasn't that they overlooked it, or ignored it, they decided they were asked directly and responded "we don't care".
If the reasoning boils down to "We can do this because you are small and we are big" I cannot support that.
The most universal thing in C/C++ is vendoring, IMHO.
If you are distributing source, you distribute everything. Then, it only needs a compiler and libc. That vendored package is tested, and it works on your platform, so there's no guesswork.
That might work for small, self-contained dependencies in projects which aren't themselves libraries. But good luck vendoring your deps when one of those deps is something really large like Qt or WebKit, or if you're building a library that other applications need to be able to link against.
> You hear people saying that a trained model can’t be a violation because humans can recite poetry, etc
Also worth noting that, if a person performs a copyrighted work from memory - like a poem, a play, or a piece of music - that can still be a copyright violation. "I didn't copy anything, I just memorized it" isn't the get-out-of-jail-free card some people think it is.
Good guess, but no. The most salient difference in that case is that an abridged children's version of a novel acts as a direct market substitute for the original, whereas a plot summary does not. (A secondary reason is that an abridged edition is likely to represent a much larger portion of the original work than would appear in a summary.)
1) instructions which "bend" the format, like ARM instructions such as STMIA or B which combine multiple fields to make a larger immediate value or mask.
2) recognizing instructions which use special values in fields (like ARM condition = 1111) to represent a special instruction.
3) instruction encodings with split fields, like the split immediate in RISC-V S-type instructions.
4) instruction encodings which have too many instruction-specific quirks to fit into any reasonable schema, like 68000.
reply