Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror

Comment: Re:And so therefor it follows and I quote (Score 1) 353

by dmbasso (#48229359) Attached to: Italian Supreme Court Bans the 'Microsoft Tax'

Why didn't you just order a hamburger?

Because nobody offers that option. I would gladly request a refund for the Windows 7 that came with my notebook if I could. The only reason I keep its partition is because I paid for that crap, and just "in case I need it"... but it's been 3 years so far without booting it. I guess I'll just wipe it and give more space to my Linux partition whenever I get some time to do it.

Comment: Re:bitcoin (Score 1) 241

by dmbasso (#47948349) Attached to: Putin To Discuss Plans For Disconnecting Russia From the Internet

Double spends for anyone who can connect to both sides of the network. Essentially, there will be two ledgers, an International ledger and a Russian one. If you spend on the Russian ledger, the International ledger will still have your money. When the network rejoins, whatever ledger has the most hashing power behind it will be chosen as the correct one, and all the transactions from the other one will be retried on the new global ledger. If the network saw a new transaction spending a previous transaction's outputs, it would be rejected, as well as any spends referencing that transaction, and so on.

Thank you, that's exactly what I wanted to know.

This happened already.

I guess I've missed the news, any links for my lazy ass?

Bitcoin sounds like a nice investment for dictators willing to further screw their populaces.

Comment: Re:Still... (Score 1) 193

by dmbasso (#47704077) Attached to: C++14 Is Set In Stone

E.g., would you rather try to see which bit is set in a string like "0b001011010011011101011100" or have it broken up like "0b0010_1101_0011_0111_0101_1100" or "0b00101101_00110111_01011100". If it's a bit field, you may even want "0b001011_010011011_01_0_111_0_0" if breaking it into fields has meaning.

Such a small change to help readability...

If you're really interested in readability you would probably define those bits, like:

#define HIGHSTUFF (0b001011 << 17)
#define NOTSOHIGHSTUFF (0b010011011 << 8)

and then or them together.

Alternatively you could define a macro for your bit field, like:

#include
#define bitfield(a,b,c,d) 0x##a##b##c##d
int main() {
        printf("%x", bitfield(f,f,f,f));
}

It isn't easy being the parent of a six-year-old. However, it's a pretty small price to pay for having somebody around the house who understands computers.

Working...