one thing i noticed in those pics was a BGA chip. BGA chips have a HUGE connection density BUT afaict they have to be mounted on top of a grid of vias preventing anything being placed on the other side of the board opposite them.
i wonder if this was why they wen't for the two board structure
The funny thing is: C++ has no real core market. Most embedded stuff where C++ is used, the programmers only write C... because they fear "to lsoe" something if they use C++.... C++ is a very complex language so on platforms where you are forced to use the manufacturers compiler there is more chance they will have screwed up the C++ compiler than the C compiler.
and how many abi breaks have we seen in gnu C++ over the last few years because they screwed up some feature of the C++ standard? loads!
last i checked the free software foundations definition of free software and the opensource definition from the OSI said essentially the same things although they had different reasoning behind saying them.
This is more difficult to implement with AC power distribution more difficult sure but certainly possible and i'm sure some electric locomotives do it.
hmm i belive electric locomotives often actually have regenerative breaking and re-inject the power into the supply system where other locomotives can use it (though i belive they also have resistive units to dump the power in case they can't re-inject it).
deisel locomotives can't really do this though because they don't have any way to store electricity.
i'd imagine you could get a few more in if you used ics directly mounted on the board rather than large surface mount packages. you could also possiblly have two pcbs stacked especially if you considered a fairly fat stick acceptable.
sectors have been 512 bytes (half a binary kilobyte) for a very very long time on nearly all disk like media (some types of cd and possiblly dvd being exceptions). and nearly all filesystems are built arround this assumption (generally using some sort of cluster which contains a power of two greater than 512 number of bytes and is fixed in size for any given partition)
does it miss features that home/pro have? does it cost a lot to license? (compared to what white box vendors pay for oem versions of home/pro) can licenses only be bought in bulk?
does that £6 a film you quote include printing though? (i suspect it does) digital is great if you take lots of photos but only ever print a few but it can get more expensive than film if you wan't prints of most of your photos.
that statement is commonly quoted but highly misleading. the important factors are tissue current, duration, route through the body (heart is generally nasty) and frequency.
tissue current is determined by applied voltage and resistance of the path.
static shocks have a very high voltage and hence initially a very high tissue current but since you are essentially draining a very low value capacitor that voltage and current tails off extremely quickly. I belive the shocks from tazers and the like are probablly similar but with more capacitance behind them so they actually incapacitage rather than just shock.
shocks off any power system mean you get the full transmission voltage accross you for a potentially LONG time (especially if there is no earth fault detection system in place) and so have a tendancy to be responsible for deaths in quite a lot of cases. the rated current of the transmission line is largely unimportant.
things like phone lines although they can reach quite nasty voltages when ringing are a high impedance source so once any parasitic capacitance is discharced the voltage and tissue current will drop down to something thats very unlikely to injure.
DC is particuarlly nasty because it can clamp you to the transmission line. RF can also be very nasty as it can apparantely do severe tissue damage without any warning.
afaict thats a risk. Sometimes people get away with it and get a very secure job, other times the company decides to take the hit of sorting it out before the person does more damage.
if you don't have explicit declarations how can the language tell if the assignement to couner is a deliberate attempt to create a new variable or a typo?
note: explicit declarations and dynmaic typing can be seperate but they usually seem to be seen together.
suppose you do (and this is just to make a point its not intended to be any particualr language)
counter = 1 while counter 10 {
do something..............
couner = counter +1 } in a statically typed language that is picked up at compile time. in a dynamically typed language you won't notice it until your app hangs at runtime and you'd better hope your in a situation where you can easilly attatch a debugger.
and if its in a rarely called branch of an if and your testsuite sucks or perhaps the count is a sanity check and the loop usually exits early you may not notice the error for a while.
forcing variable declaration converts a whole class of bugs to compile time errors. this is a very good thing!
You can do it in Windows just as well -- as long as you're running a version older than 2k or XP. See, the limitation *is* completely artificial.
there is no version of the NT line older than 2K that supports fat32.
98 (and i presume ME but i don't have access to check) will format larger fat32 paritions but it wouldn't at all surprise me if the formatters were seperate codebases.
i've seen several people reporting issues with theese drivers above. do you know if any form of comparative stress testing has been performed on theese drivers?
5. Say it won't be fixed. Bugzilla has a "WONTFIX" status which is used quite often. as apposed to propietry vendors who won't even admit it exists in the first place.
one big big problem is its nearly impossible to debug what you can't eaasilly reproduce. i've had 100% cpu bugs that took weeks of real life usage to appear for some users and that we never managed to reproduce under controlled conditions. we added (a LOT) more checking to the code and also moved to a more recent freepascal (freepascal 1.0.x used some very old legacy linux syscalls iirc that are probablly not well tested any more) and reports of the bug have since dried up but we NEVER nailed exactly what caused it.
hmm i've noticed that flash sticks usually appear as removable drives but my external hard drives in caddies appear as hard drives (both in my computer and in disk management).
does the mass storage class have some system for identifying if a drive is a removable drive or not?
Slashdot Mirror
all sounds nice but that still leaves two questions.
is XPe expensive and/or only purchaseable in large bulk (and therefore only an option for large manufaturers).
if you pick everything on XPe do you end up with everything that home has? everything that pro has? less than either? more than either?
one thing i noticed in those pics was a BGA chip. BGA chips have a HUGE connection density BUT afaict they have to be mounted on top of a grid of vias preventing anything being placed on the other side of the board opposite them.
i wonder if this was why they wen't for the two board structure
The funny thing is: C++ has no real core market. Most embedded stuff where C++ is used, the programmers only write C ... because they fear "to lsoe" something if they use C++ ....
C++ is a very complex language so on platforms where you are forced to use the manufacturers compiler there is more chance they will have screwed up the C++ compiler than the C compiler.
and how many abi breaks have we seen in gnu C++ over the last few years because they screwed up some feature of the C++ standard? loads!
last i checked the free software foundations definition of free software and the opensource definition from the OSI said essentially the same things although they had different reasoning behind saying them.
This is more difficult to implement with AC power distribution
more difficult sure but certainly possible and i'm sure some electric locomotives do it.
hmm i belive electric locomotives often actually have regenerative breaking and re-inject the power into the supply system where other locomotives can use it (though i belive they also have resistive units to dump the power in case they can't re-inject it).
deisel locomotives can't really do this though because they don't have any way to store electricity.
i'd imagine you could get a few more in if you used ics directly mounted on the board rather than large surface mount packages. you could also possiblly have two pcbs stacked especially if you considered a fairly fat stick acceptable.
sectors have been 512 bytes (half a binary kilobyte) for a very very long time on nearly all disk like media (some types of cd and possiblly dvd being exceptions). and nearly all filesystems are built arround this assumption (generally using some sort of cluster which contains a power of two greater than 512 number of bytes and is fixed in size for any given partition)
does it miss features that home/pro have?
does it cost a lot to license? (compared to what white box vendors pay for oem versions of home/pro)
can licenses only be bought in bulk?
afaict pretty much all disk like flash does wear leveling in hardware below the filesystem anyway so doesn't require special filesystems.
ROFL
p.s. for non brits its a fag packet related joke.
strange its just reappeared and now it has a bid on it! go figure.
the link gives ebays typical item not found error.
does that £6 a film you quote include printing though? (i suspect it does) digital is great if you take lots of photos but only ever print a few but it can get more expensive than film if you wan't prints of most of your photos.
it's not the volts that kill you, it's the amps
that statement is commonly quoted but highly misleading. the important factors are tissue current, duration, route through the body (heart is generally nasty) and frequency.
tissue current is determined by applied voltage and resistance of the path.
static shocks have a very high voltage and hence initially a very high tissue current but since you are essentially draining a very low value capacitor that voltage and current tails off extremely quickly. I belive the shocks from tazers and the like are probablly similar but with more capacitance behind them so they actually incapacitage rather than just shock.
shocks off any power system mean you get the full transmission voltage accross you for a potentially LONG time (especially if there is no earth fault detection system in place) and so have a tendancy to be responsible for deaths in quite a lot of cases. the rated current of the transmission line is largely unimportant.
things like phone lines although they can reach quite nasty voltages when ringing are a high impedance source so once any parasitic capacitance is discharced the voltage and tissue current will drop down to something thats very unlikely to injure.
DC is particuarlly nasty because it can clamp you to the transmission line. RF can also be very nasty as it can apparantely do severe tissue damage without any warning.
afaict thats a risk. Sometimes people get away with it and get a very secure job, other times the company decides to take the hit of sorting it out before the person does more damage.
yeah until some of your students mix spaces and tabs............
seriously a language that depends on stuff thats invisible in a normal editor sounds like it would cause the lab demonstrators hell.
if you don't have explicit declarations how can the language tell if the assignement to couner is a deliberate attempt to create a new variable or a typo?
note: explicit declarations and dynmaic typing can be seperate but they usually seem to be seen together.
suppose you do (and this is just to make a point its not intended to be any particualr language)
counter = 1
while counter 10 {
do something..............
couner = counter +1
}
in a statically typed language that is picked up at compile time. in a dynamically typed language you won't notice it until your app hangs at runtime and you'd better hope your in a situation where you can easilly attatch a debugger.
and if its in a rarely called branch of an if and your testsuite sucks or perhaps the count is a sanity check and the loop usually exits early you may not notice the error for a while.
forcing variable declaration converts a whole class of bugs to compile time errors. this is a very good thing!
is pretty damning yeah.
/. should invite the buyer for an interview that would be fun).
i wonder if anyone will actually buy this (if so
You can do it in Windows just as well -- as long as you're running a version older than 2k or XP. See, the limitation *is* completely artificial.
there is no version of the NT line older than 2K that supports fat32.
98 (and i presume ME but i don't have access to check) will format larger fat32 paritions but it wouldn't at all surprise me if the formatters were seperate codebases.
i've seen several people reporting issues with theese drivers above. do you know if any form of comparative stress testing has been performed on theese drivers?
5. Say it won't be fixed. Bugzilla has a "WONTFIX" status which is used quite often.
as apposed to propietry vendors who won't even admit it exists in the first place.
one big big problem is its nearly impossible to debug what you can't eaasilly reproduce. i've had 100% cpu bugs that took weeks of real life usage to appear for some users and that we never managed to reproduce under controlled conditions. we added (a LOT) more checking to the code and also moved to a more recent freepascal (freepascal 1.0.x used some very old legacy linux syscalls iirc that are probablly not well tested any more) and reports of the bug have since dried up but we NEVER nailed exactly what caused it.
hmm i've noticed that flash sticks usually appear as removable drives but my external hard drives in caddies appear as hard drives (both in my computer and in disk management).
does the mass storage class have some system for identifying if a drive is a removable drive or not?
the fact its not in 2K either makes me think its more likely an implementation screwup that they didn't bother fixing.
did drives bigger than that even exist when win2K came out? (over 6 years ago now iirc)