Not so much idiomatic as stinky syntax. Idiomatic would be to cast the boolean into cannonical form and use that as subscript for an explicit array. Something like (with corrected syntax): skyColour = {blue,black}[daytime];
C: skyColour = daytime ? blue : black;
Algol68: *two* syntaxes for same thing. skyColour:= if daytime then blue else black fi; skyColour:= (daytime|blue|black);
Lisp: something like (setq skyColour (cond (daytime blue) (t black)))
Taken literally, it would mean a mouse, keyboard and/or monitor plugged into a laptop. Pretty soon it will be illegal to use a Microsoft controlled machine to actually do anything.
Are you trying to claim that an OEM license is automatically consumed by the computer and is therefore not actually a license? This is ludicrous. This is ludicrous. This is Microsoft. One degree of separation
IIRC at one time Windows could be run in three modes, real mode, 286-protected mode, 386-enhanced mode. You could also run multiple instances of 286-mode windows under Quarterdeck and possibly Novell's DOS.
Article 6 would seem to allow them to regain their rights by receiving a new copy of the code. That allows them to re-derive something (else?) from the new copy. What is questionable is the status of what was derived from the old copy. Who if anyone owns it (or even can own it).
No, you don't get to take three years to deliver the source. It's a three year duration after delivery of the binary where the source must be available even if everybody has lost interest.
Which side of the road you drive on is arbritrary. Things just work a lot better if everybody agrees on the *same* arbritrary. The existing dominant processors are the IBM and Sun big iron. Maybe you like reading the hex value 12345678 as 78 56 34 12, but I don't.
How big can it be? What happens when it *is* bigger than expected? 32767 + 1 yields -32768 99 + 1 gives 00 (or:0 or...) What happens if the string is bigger than the string datatype can hold? At least the prof put the critical assumption up front.
Anyone remember the 8-track tape players? This is looking more and more like expensive sucker-bait. People do not buy expensive toys to be hassled and made to look foolish. Look at it. See it for what it is. Snicker politely, and leave.
Say you have a value 12345678 in hex Little Endian : addressed by least-significant byte 78 56 34 12 Big Endian : addressed by most-significant byte 12 34 56 78
You have a value 00000001 in hex stored at location 1000 32-bit value at location 1000 both endians. 16-bit value at location 1000 little endian. 8-bit value at location 1000 little endian. 16-bit value at location 1002 big endian. 8-bit value at location 1003 big endian.
Big Endian: Numeric order corresponds to character order.
Little Endian: Numeric order unrelated to character order.
run multiple/different/ OSes Debugging the OS while the machine is being used for production. Console debugging is very expensive if you have to do it on the bare iron.
Imagine a Chinese who doesn't really understand English with a prompt to enter and reenter his root password. To be fair, he should have installed it in Chinese and tried to guess what it was asking. The English install is recent and probably hasn't had the bugs worked out yet.
Red Flag 1.something was essentially same as Red Hat 6.1 with some but not all the references to Red Hat changed to Red Flag. There was something that attempted to be a Simplified Chinese desktop. Red Flag 2.0 had 2.2.16 kernel and a decent Simplified Chinese desktop with enough departure from the stock Red Hat install that I wasn't sure what was going on (I don't read Chinese). The Simplified Chinese KDE desktop/language support in Red Hat 7.2 likely came from Red Flag. I'm sure somebody will do a security audit, but I wouldn't expect anything stranger than would be in Red Hat, Mandrake, or SuSE. I would expect them to be pushing the edge to smoothly handle double-byte characters on the desktop.
Once we destabalise it, the environment just finds a different point of stability, just like its been doing for the last few billion years. The problem with messing with the environment is that you tend to keep the cockroaches and rats but lose the Birds of Paradise. Things like the TseTse fly, the environment is almost certainly better without.
Slashdot Mirror
Not so much idiomatic as stinky syntax.
:= if daytime then blue else black fi; := (daytime|blue|black);
Idiomatic would be to cast the boolean into cannonical form and use that as subscript for an explicit array. Something like (with corrected syntax):
skyColour = {blue,black}[daytime];
C:
skyColour = daytime ? blue : black;
Algol68: *two* syntaxes for same thing.
skyColour
skyColour
Lisp: something like
(setq skyColour (cond (daytime blue) (t black)))
A sentence written out this way
is
better
than
one
written
this
way.
The concept should not be that unfamiliar. Ever read something where the author took lots of words to say very little?
Taken literally, it would mean a mouse, keyboard and/or monitor plugged into a laptop. Pretty soon it will be illegal to use a Microsoft controlled machine to actually do anything.
Are you trying to claim that an OEM license is automatically consumed by the computer and is therefore not actually a license? This is ludicrous.
This is ludicrous.
This is Microsoft.
One degree of separation
I don't know if that was intentional, but it does convey some of the sense of blithely ignoring the consequences of what we do.
IIRC at one time Windows could be run in three modes, real mode, 286-protected mode, 386-enhanced mode. You could also run multiple instances of 286-mode windows under Quarterdeck and possibly Novell's DOS.
I dunno. IBM is selling "Linux-Only" mainframes.
Linux-Only. Sounds on-spec and not to a Microsoft-broken spec, either.
The old DOSSHELL
DOSS with 2 esses.
HELL with 2 ells.
Seems like there's not a lot of "near" up there.
Think of Saskatchewan as northern Kansas. Very northern Kansas.
... cruel and unusual punishment on anyone trying to use a Microsoft OS.
Article 6 would seem to allow them to regain their rights by receiving a new copy of the code.
That allows them to re-derive something (else?) from the new copy.
What is questionable is the status of what was derived from the old copy. Who if anyone owns it (or even can own it).
No, you don't get to take three years to deliver the source. It's a three year duration after delivery of the binary where the source must be available even if everybody has lost interest.
When Windows and Hammer get together.......
And yes, I thought your pun was funny.
Watch as the closed source world makes an even bigger technology gap ...
New and better worms?
Which side of the road you drive on is arbritrary. Things just work a lot better if everybody agrees on the *same* arbritrary.
The existing dominant processors are the IBM and Sun big iron.
Maybe you like reading the hex value 12345678 as 78 56 34 12, but I don't.
How big can it be? :0 or ...)
What happens when it *is* bigger than expected?
32767 + 1 yields -32768
99 + 1 gives 00 (or
What happens if the string is bigger than the string datatype can hold?
At least the prof put the critical assumption up front.
Anyone remember the 8-track tape players?
This is looking more and more like expensive sucker-bait. People do not buy expensive toys to be hassled and made to look foolish.
Look at it. See it for what it is. Snicker politely, and leave.
Making the world safe for Microsoft Worms.
Used to be you could kill the Viral Basic script engines.
Now when you kill them, they just come back.
Say you have a value 12345678 in hex
Little Endian : addressed by least-significant byte
78 56 34 12
Big Endian : addressed by most-significant byte
12 34 56 78
You have a value 00000001 in hex stored at location 1000
32-bit value at location 1000 both endians.
16-bit value at location 1000 little endian.
8-bit value at location 1000 little endian.
16-bit value at location 1002 big endian.
8-bit value at location 1003 big endian.
Big Endian:
Numeric order corresponds to character order.
Little Endian:
Numeric order unrelated to character order.
Can you essentially/actually/theoretically run different OSes on each of those "virtual computers"?
Yes. Very yes.
Including running VM on top of VM.
run multiple /different/ OSes
Debugging the OS while the machine is being used for production.
Console debugging is very expensive if you have to do it on the bare iron.
Imagine a Chinese who doesn't really understand English with a prompt to enter and reenter his root password. To be fair, he should have installed it in Chinese and tried to guess what it was asking.
The English install is recent and probably hasn't had the bugs worked out yet.
Red Flag 1.something was essentially same as Red Hat 6.1 with some but not all the references to Red Hat changed to Red Flag. There was something that attempted to be a Simplified Chinese desktop.
Red Flag 2.0 had 2.2.16 kernel and a decent Simplified Chinese desktop with enough departure from the stock Red Hat install that I wasn't sure what was going on (I don't read Chinese).
The Simplified Chinese KDE desktop/language support in Red Hat 7.2 likely came from Red Flag.
I'm sure somebody will do a security audit, but I wouldn't expect anything stranger than would be in Red Hat, Mandrake, or SuSE. I would expect them to be pushing the edge to smoothly handle double-byte characters on the desktop.
Once we destabalise it, the environment just finds a different point of stability, just like its been doing for the last few billion years.
The problem with messing with the environment is that you tend to keep the cockroaches and rats but lose the Birds of Paradise.
Things like the TseTse fly, the environment is almost certainly better without.