Hell, developing Windows Mobile apps practically requires Windows, since I believe most of the APIs for using its mobile platform are only available for Windows and work best with Visual Studio (just like Xcode with the iPhone).
1) Microsoft doesnt DEMAND that you ONLY use their API's (alternate API's may supplant, coexist, or even extend)
2) Microsoft doesnt DEMAND that you call their API's DIRECTLY (you are free to use middle-ware)
3) Microsoft doesnt DEMAND that you use particular languages (you are even free to roll your own compiler)
Got anything else?
Do you even write programs? The GNU C++ compiler will give you a warning if you compare a signed variable to an unsigned variable. This should tell you that it is a bad idea if you don't believe me.
It in fact does work correctly which is why its a WARNING instead of an ERROR.
The WARNING is because the compiler knows that it is performing an implicit, UNDEFINED, cast.
The way you are talking, you seem to think that you should also be getting overflow exceptions and other shit that programmers fluent in twos complement also dont want.
FACT: only people that write incorrect (BUGGY SHIT) code have a problem with mixing signed and unsigned.
Others have already explained this to you. I have explained this to you. You seem to think that C compilers are supposed to hold your hand and make sure that you dont produce buggy code. Wrong.
Are you suggesting that a body other than the state legislature has the power to mandate such policies in the venue in which they were mandated?
He might hate gay people, but at least hes up front about it and comes armed with the state constitution to back up his shit. You on the other hand also obviously hate a group of people, but don't seem to have the state constitution to back up your shit.
If you don't like the state constitution... work to change it. Don't be a naked hater all your life.
The most significant bit is 0, so the pattern represents a non-negative (positive) value....The most significant bit is 1, so the value represented is negative...
That doesnt make it a sign bit.. you know that, right?
I call that a sign bit.
Then you use the term incorrectly, and this misuse is the direct result of someone who doesnt understand twos complement.
If you understood two's complement, you would know that the mixing signed with unsigned isnt a problem. You would in fact know that twos complement won out over ones complement precisely because the mixing of signed and unsigned values isnt a problem. In effect, two's complement is beautiful.
Not knowing what type the compiler is currently treating the value as, now thats a real problem. A problem between keyboard and chair.
How can they be stored exactly the same, yet give different ranges of values for the same number of bytes?
The 'range' of values you are referring to are a higher abstraction than the CPU uses. The two's complement CPU see's a string of bits when adding and subtracting, not a value with lower and upper bounds.
The leading bit on signed numbers is the actual sign.
sigh... you realize that in twos complement, there isnt really a 'sign bit', right?
-1 is not the bits of 1 with a "sign bit" also set. In twos complement, the negation of a number is strictly defined as (~x) + 1
The beauty of it is that adding or subtracting integers works regardless of weather or not they are considered signed or not. They can both be signed. They can both be unsigned. One can be signed while the other not signed. In each of these cases the exact same silicon performs the addition in the exact same manner and knows NOTHING about "signs." On two's complement machines, there is only one ADD instruction. There isn't a SignedADD instruction or anything of the like. This is the reason thats two's complement won the complement war.
So now I posit this:
If the hardware is completely oblivious to the "sign" of the values, then how can it be that mixing signed and unsigned causes a problem for you? Well, it can only be that you are the problem. The bits outputted by the machine are the same in all cases.
The problem isnt "windows".. the problem is "x86 computers."
Accurate timing on the modern PC is ridiculously difficult due to the hardware situation. The original IBM PC and its clones came with Intel's 8253 or 8254 Programmable Interval Timer (PIT) chip and back then it was pretty good. This timer chip had an internal frequency matching the CPU's of the time of 4.77mhz, and ticks were evenly distributed between 4 internal counters, so each counter had 1193181.81818181.... ticks per second. Pretty damn good.
Many of the old-school people might be familiar with the 18.2 ticks per second of the DOS clock. This rate was a direct consequence of configuring one of those counters to emit an interrupt every 65536 ticks, the longest possible interrupt interval due to these chips using 16-bit words.
Anyways, over time many manufacturers stopped using Intel's PIT's and started emulating them with other hardware (such as PMT.) None of these emulations can be configured to tick at exactly the same rate as the Intel PIT, and even among these emulated timers there wasn't any consistency.
To counter the serious problem of accurate timing on the PC, Microsoft and a few other large companies moved to define a new standard named HPET. Many new motherboards will have an HPET timer, but not all of them, and there are some problems with some HPET implementations as well (such as appearing to tick backwards sometimes.)
The issue of accurate timing on PC's has considerable effect on multi-player game developers.
Those clocks receive a signal thats transmitted at a ridiculously low rate, like 1 bit per second or some such. I'm going to go ahead and assume that hardware thats designed to receive it isnt designed for low or consistent latency.
In the case of "single-point" setups that could be served by low capability cpu's with a low ram ceiling, is there anything that ARM solves that needs to be solved?
Certainly heat isnt a problem in this scenario on Intel?..and power?
We can't talk about cost so much because we have no idea what the price point for multi-core Arm's will be, but Intel certainly hasnt created a price barrier on its Atom's.
I never said the finder should give the 4G to someone that doesn't own it
...ummm...., but then you immediately do so again:
I suggested that leaving it with bar staff (i.e. leaving it in the area where it was lost) would give a better chance of the 4G getting back to its owner.
yeah, right. And you didn't "suggest" that leaving it with the bar owner would do any such thing. What you did was ask "why" he did not do that, and then pretended that not doing so is evidence of theft.
Its not evidence of theft.
I also note with interest that the "finder" made no attempt to contact the bar afterwards - why not?
And here you are again, using a question as some sort of valid argument. The act of asking the question is not evidence of anything. The lack of a response from the person you would like to answer also isnt evidence of anything.
Your evidence of a crime is you imagining answers or lack of answers to questions. You know that, right?
First of all, the specific objections in the comment I replied to have remained constant. He didn't say anything about the terms change.
Of course he didn't.. YOU however did talk about weather or not the terms have been changing. You claimed that they have not, that he should have know all along what the deal was. I can't believe that you didn't know the truth, therefore.. you lied.
I don't mind so much when people are just plain old wrong.. but when people like you are intentionally deceptive in their pro-active fanboyism.. yeah.. go fuck yourself. Cock cuckers don't always get away with tackle arguments that they cannot refute by lying. Sometimes someone like me comes along and gives you all the civility you deserve. None.
Are you seriously suggesting that people who own Macs, who regularly give THOUSANDS OF DOLLARS to Adobe, wont think twice about reformatting their OSX drive and installing Win7?
I mean.. it might possibly be true IF there were alternatives to Adobe's suite.. BUT THERE ISNT.
The people who but Adobe suite's don't buy them because they happen to run on their Mac, no.. instead they buy Macs because they run happen to run Adobe suites.
Slashdot Mirror
Did you really just say "stability guidelines that can only be met by.. C++ code"
????
Please leave the programming talk to programmers.
Hell, developing Windows Mobile apps practically requires Windows, since I believe most of the APIs for using its mobile platform are only available for Windows and work best with Visual Studio (just like Xcode with the iPhone).
1) Microsoft doesnt DEMAND that you ONLY use their API's (alternate API's may supplant, coexist, or even extend)
2) Microsoft doesnt DEMAND that you call their API's DIRECTLY (you are free to use middle-ware)
3) Microsoft doesnt DEMAND that you use particular languages (you are even free to roll your own compiler)
Got anything else?
Do you even write programs? The GNU C++ compiler will give you a warning if you compare a signed variable to an unsigned variable. This should tell you that it is a bad idea if you don't believe me.
It in fact does work correctly which is why its a WARNING instead of an ERROR.
The WARNING is because the compiler knows that it is performing an implicit, UNDEFINED, cast.
The way you are talking, you seem to think that you should also be getting overflow exceptions and other shit that programmers fluent in twos complement also dont want.
FACT: only people that write incorrect (BUGGY SHIT) code have a problem with mixing signed and unsigned.
Others have already explained this to you. I have explained this to you. You seem to think that C compilers are supposed to hold your hand and make sure that you dont produce buggy code. Wrong.
ARM called and wants to know why you think its #1 status isn't important, and then Intel called and wants to know why its #2 status isn't important.
Who takes out the payroll taxes?
If HP hired a CORPORATION, then there is no fucking way your "common definition" fits.
Are you suggesting that a body other than the state legislature has the power to mandate such policies in the venue in which they were mandated?
He might hate gay people, but at least hes up front about it and comes armed with the state constitution to back up his shit. You on the other hand also obviously hate a group of people, but don't seem to have the state constitution to back up your shit.
If you don't like the state constitution... work to change it. Don't be a naked hater all your life.
in the real world, 64-bit computing is also about more registers and 64-bit integers
1998 called. It wants to know why you havent learned anything since then.
The most significant bit is 0, so the pattern represents a non-negative (positive) value....The most significant bit is 1, so the value represented is negative...
That doesnt make it a sign bit.. you know that, right?
I call that a sign bit.
Then you use the term incorrectly, and this misuse is the direct result of someone who doesnt understand twos complement.
If you understood two's complement, you would know that the mixing signed with unsigned isnt a problem. You would in fact know that twos complement won out over ones complement precisely because the mixing of signed and unsigned values isnt a problem. In effect, two's complement is beautiful.
Not knowing what type the compiler is currently treating the value as, now thats a real problem. A problem between keyboard and chair.
That folder contains 64-bit binaries.
How can they be stored exactly the same, yet give different ranges of values for the same number of bytes?
The 'range' of values you are referring to are a higher abstraction than the CPU uses. The two's complement CPU see's a string of bits when adding and subtracting, not a value with lower and upper bounds.
The leading bit on signed numbers is the actual sign.
sigh... you realize that in twos complement, there isnt really a 'sign bit', right?
-1 is not the bits of 1 with a "sign bit" also set. In twos complement, the negation of a number is strictly defined as (~x) + 1
The beauty of it is that adding or subtracting integers works regardless of weather or not they are considered signed or not. They can both be signed. They can both be unsigned. One can be signed while the other not signed. In each of these cases the exact same silicon performs the addition in the exact same manner and knows NOTHING about "signs." On two's complement machines, there is only one ADD instruction. There isn't a SignedADD instruction or anything of the like. This is the reason thats two's complement won the complement war.
So now I posit this:
If the hardware is completely oblivious to the "sign" of the values, then how can it be that mixing signed and unsigned causes a problem for you? Well, it can only be that you are the problem. The bits outputted by the machine are the same in all cases.
He was modded troll, but hes right.. sort of.
.. the problem is "x86 computers."
The problem isnt "windows"
Accurate timing on the modern PC is ridiculously difficult due to the hardware situation. The original IBM PC and its clones came with Intel's 8253 or 8254 Programmable Interval Timer (PIT) chip and back then it was pretty good. This timer chip had an internal frequency matching the CPU's of the time of 4.77mhz, and ticks were evenly distributed between 4 internal counters, so each counter had 1193181.81818181.... ticks per second. Pretty damn good.
Many of the old-school people might be familiar with the 18.2 ticks per second of the DOS clock. This rate was a direct consequence of configuring one of those counters to emit an interrupt every 65536 ticks, the longest possible interrupt interval due to these chips using 16-bit words.
Anyways, over time many manufacturers stopped using Intel's PIT's and started emulating them with other hardware (such as PMT.) None of these emulations can be configured to tick at exactly the same rate as the Intel PIT, and even among these emulated timers there wasn't any consistency.
To counter the serious problem of accurate timing on the PC, Microsoft and a few other large companies moved to define a new standard named HPET. Many new motherboards will have an HPET timer, but not all of them, and there are some problems with some HPET implementations as well (such as appearing to tick backwards sometimes.)
The issue of accurate timing on PC's has considerable effect on multi-player game developers.
A reference to some of the issues, and some of the attempts to fix them (source code)
Those clocks receive a signal thats transmitted at a ridiculously low rate, like 1 bit per second or some such. I'm going to go ahead and assume that hardware thats designed to receive it isnt designed for low or consistent latency.
uuh... what?
Signed and unsigned integral values are stored in exactly the same way on twos complement machines. Its rather beautiful.
Your problems with mixing them is somewhere between your keyboard and your chair.
Step back and look at your argument.
..and power?
In the case of "single-point" setups that could be served by low capability cpu's with a low ram ceiling, is there anything that ARM solves that needs to be solved?
Certainly heat isnt a problem in this scenario on Intel?
We can't talk about cost so much because we have no idea what the price point for multi-core Arm's will be, but Intel certainly hasnt created a price barrier on its Atom's.
You've got it almost right.
Your encoder is encoding the original 31-bit "words" from right to left, but your decode is decoding the original 31-bit "words" from left to right
People Can't Memorize Computer Industry Acronyms (PCMCIA)
In my world, it still does.
If I am not required to decode the metadata stream, then you can't put the shared metadata in the metadata stream.
And here it is. The reason for container formats. If there are things that you ARE required to do, then they should be part of the format.
I never said the finder should give the 4G to someone that doesn't own it
I suggested that leaving it with bar staff (i.e. leaving it in the area where it was lost) would give a better chance of the 4G getting back to its owner.
yeah, right. And you didn't "suggest" that leaving it with the bar owner would do any such thing. What you did was ask "why" he did not do that, and then pretended that not doing so is evidence of theft.
Its not evidence of theft.
I also note with interest that the "finder" made no attempt to contact the bar afterwards - why not?
And here you are again, using a question as some sort of valid argument. The act of asking the question is not evidence of anything. The lack of a response from the person you would like to answer also isnt evidence of anything.
Your evidence of a crime is you imagining answers or lack of answers to questions. You know that, right?
First of all, the specific objections in the comment I replied to have remained constant. He didn't say anything about the terms change.
Of course he didn't.. YOU however did talk about weather or not the terms have been changing. You claimed that they have not, that he should have know all along what the deal was. I can't believe that you didn't know the truth, therefore.. you lied.
I don't mind so much when people are just plain old wrong.. but when people like you are intentionally deceptive in their pro-active fanboyism.. yeah.. go fuck yourself. Cock cuckers don't always get away with tackle arguments that they cannot refute by lying. Sometimes someone like me comes along and gives you all the civility you deserve. None.
Are you seriously suggesting that people who own Macs, who regularly give THOUSANDS OF DOLLARS to Adobe, wont think twice about reformatting their OSX drive and installing Win7?
I mean.. it might possibly be true IF there were alternatives to Adobe's suite.. BUT THERE ISNT.
The people who but Adobe suite's don't buy them because they happen to run on their Mac, no.. instead they buy Macs because they run happen to run Adobe suites.
It doesnt bring any of the others to a slow crawl, and unlike the iPhone, they multitask.
..even though Safari isnt compliant with web standards at this time, and least of all on the iPhone.