note that javas standard classes for io (e.g. datainpustream and dataoutpustream) pretty much don't let you write code that will have different results on diffent platforms anyway even if you aren't using serialisation.
personally i belive that file formats should where possible be as independent from the program thats generating and parsing them as possible like html png jpeg etc are.
Re:C++ is cross-platform, dont know what your smok
on
Write Portable Code
·
· Score: 1
reflection is addictive though because unlike interfaces etc it doesn't require the classes to be designed for it.
look at the following code for instance. by using reflection i can make it use any method of the objects to do the conversion to strings thus making it very generic.
public static String[] objectArrayToStringArray(Object[] in,Method conversionmethod) throws InvocationTargetException,IllegalAccessException {
int l = in.length;
String [] out = new String [l];
for (int i=0;il;i++) {
out[i] = (String)conversionmethod.invoke(in[i],(Object[])nu ll);
}
return out;
}
you could generalise this further to make it go from an array of any object to an array of any object (and i might do that if i found a reason to do so).
Re:C++ is cross-platform, dont know what your smok
on
Write Portable Code
·
· Score: 1
is there a way to make reflection work on non-public fields and methods and if not how do degbuggers and serialisation do it?
is there any reason you can't link multiple gameboy players? do they give a reason for reccomending against doing it?
i can see how tilt sensor games would be a pain to play you'd have to tilt the whole gamecube.
i'd think sunlight sensor games would be possible with some care, just because the sensor can see the sun doesn't mean the rest of the kit has to indeed using the gameboy in the sun is pretty horrid in my experiance anyway (imo there are only two ways to make a gba screen decent, carefully directed artificial light and an afterburner)
yeah re-buying can be a pita but thats the console buisness for you:(
btw have you ever tried the gameboy player? it screws to the bottom of your gamecube and lets you play everything an gameboy advance will play (and a very large proportion of nintendos classics have had some form of gameboy port) without having to put up with the tiny screen of a portable device.
rot13 text below is an explanation of the joke for those who don't get it Guvf vf gur vagreangvbany BOSHFPNGRQ P pbqr pbagrkg fb vgf cerggl zhpu n tvira gung gur pbqr jvyy ABG or ernqnoyr
the main reason is that there is a huge ammount of code written in C there are a variety of (good) reaons for writing code in C but one of its downsides is it makes handling variable length data structures a buisness that can only be done safely by taking great care.
Since not all programmers care about security (they may have assumed thier lib would only be used with trusted data) and even those that do are imperfect this leads to lots of buffer overflows in C code.
viruses in the dos days afaict spread in 3 main ways
1: warez (pretty much impossible to avoid viruses) 2: shareways and other legitimagely redistributable software 3: using the same read/write installation media on multiple systems. 4: accidental floppy booting
1 is a risk to any user that uses warez but linux users rarely do
2 and 3 were caused by insecure sources of legitimate software which isn't really an issue for any platform anymore (most legitimate software comes either straight from a trusted source over the network or from read-only optical media)
4 was pretty much unavoidable with the original pcs standard hardware architecture but remained an issue far longer than it had to due to bad bios designs (it would have been avoided if bioses had the hard drive first in the default boot order and encouraged use of an override key to floppy boot).
so out of the 4 only one was really something the platform could have done much about
1: when coding with pointers/unchecked length arrays all it takes is one screwup even if you are trying to be carefull. Higher level structures and/or managed code can prevent this but at a cost in performance bloat and in the case of managed code ease of integration with traditional code.
2: the wmf/emf code is probablly very old from long long before the internet was commonplace. The idea of people deliberately creating image files to bypass security probablly didn't even occour to anyone.
the time i see people using this is if they are hooked on a series and for some reason miss and episode and haven't recorded it (either because they normally watch it when its on or they forgot to set the vcr or thier pvr crashed or whatever)
Streaming TV at broadcast quality requires a lot more bandwidth than most "broadband" ISP customers current get to their homes.
bullshit, digital terrestrial in the uk is iirc about 3 megabit/s and thats using pretty old tech (mpeg2 video mp2 audio). With a modern codec you could probablly halve that possiblly more bringing you WELL into the realm of what DSL can do.
the problem may come if everyone started doing it the links further upstream couldn't cope but that could be mitigated if isps could be persuaded to support IP multicast.
afaict they are releasing an opensource stub that links with a binary driver and the linux kernel.
this doesn't break every version like a full binary driver but is presumablly also extra work for them and it still breaks occasionally (iirc 4k kernel stacks did it).
if you are picking hardware for a linux box (e.g. you aren't just buying shit and hoping it works or trying to install on existing) the biggest problem driver wise seems to be 3D graphics. Its a two horse race and afaict neither really has drivers availible that are both good and opensource.
yeah running installers with custom drivers is a process thats often poorly documented and a pita which is a huge shame imo.
anyone fancy writing a little utility to produce custom bootdisks/driver disks for all the major distros?
you don't nessacerally need to make a full driver disk to the installers specs though just build the driver against the intallation kernel (requires finding headers for it but that shouldn't be too hard) and insmod it manually whilst running the installer.
yeah missing and misplaced breaks (if something has to be brought out of a switch for some reason and is inside a loop) can cause hell its kind of a design issue with the C switch statement that if you don't wan't fallthrough you have to explicitly tell it you don't.
C is an old language that is full of quirks. Its dervivitves have got rid of some but not all of those quirks.
the vast majority of sites use name-based virtual hosting depends, if they are on commercial webhosing probablly but those run on home servers probablly won't unless the user wan'ts to host multiple sites.
i think the key is php is easy to learn incrementally. you can start with a tiny chunk of code, drop it in your webpage and it will actually do something and if you look at tutorials for php they all seem to be geared this way (i found this highly annoying as someone who can program and wanted to change something in a major php program, all the php tutorials i could find were not programmer orientated).
false color indeed has legitimage scientific value (using only greyscale is very wastefull of the eyes abilities) but i bet sometimes the settings are chosen to maximise the wow factor.
Einstein provided mathematical proofs in his groundbreaking articles IIRC
maybe he did but those proofs have to be based on axioms (things that are assumed true) and in the case of trying to predict the real world those have to be guessed. If those assumptions are wrong your mathematical proof is useless.
the aim in science is to find axioms that fit the current knowlage, allow sucessfull predictions to be made, and are no more complex than nessacery to do those two things.
However as our knowlage of the real world improves some of those axioms are going to be found false, thats progress.
humans are humans and provided they have decent fine motor skills should be able to do quite high level tasks in a single step and then report back when they are done.
machines just can't operate at that level yet without a very predictable environment (which the human body isn't really). I'd think the surgon on earth would be giving high level commands (cut this,join that etc) and the astronoughts would be turning those into start cutting stop cutting etc.
Slashdot Mirror
note that javas standard classes for io (e.g. datainpustream and dataoutpustream) pretty much don't let you write code that will have different results on diffent platforms anyway even if you aren't using serialisation.
personally i belive that file formats should where possible be as independent from the program thats generating and parsing them as possible like html png jpeg etc are.
reflection is addictive though because unlike interfaces etc it doesn't require the classes to be designed for it.
u ll);
look at the following code for instance. by using reflection i can make it use any method of the objects to do the conversion to strings thus making it very generic.
public static String[] objectArrayToStringArray(Object[] in,Method conversionmethod) throws InvocationTargetException,IllegalAccessException {
int l = in.length;
String [] out = new String [l];
for (int i=0;il;i++) {
out[i] = (String)conversionmethod.invoke(in[i],(Object[])n
}
return out;
}
you could generalise this further to make it go from an array of any object to an array of any object (and i might do that if i found a reason to do so).
is there a way to make reflection work on non-public fields and methods and if not how do degbuggers and serialisation do it?
find me one that works on pic18 ;)
is there any reason you can't link multiple gameboy players? do they give a reason for reccomending against doing it?
i can see how tilt sensor games would be a pain to play you'd have to tilt the whole gamecube.
i'd think sunlight sensor games would be possible with some care, just because the sensor can see the sun doesn't mean the rest of the kit has to indeed using the gameboy in the sun is pretty horrid in my experiance anyway (imo there are only two ways to make a gba screen decent, carefully directed artificial light and an afterburner)
yeah re-buying can be a pita but thats the console buisness for you :(
btw have you ever tried the gameboy player? it screws to the bottom of your gamecube and lets you play everything an gameboy advance will play (and a very large proportion of nintendos classics have had some form of gameboy port) without having to put up with the tiny screen of a portable device.
hmm a google search for rot13 turns up an encoder/decoder as the first result
ROFL
rot13 text below is an explanation of the joke for those who don't get it
Guvf vf gur vagreangvbany BOSHFPNGRQ P pbqr pbagrkg fb vgf cerggl zhpu n tvira gung gur pbqr jvyy ABG or ernqnoyr
the main reason is that there is a huge ammount of code written in C there are a variety of (good) reaons for writing code in C but one of its downsides is it makes handling variable length data structures a buisness that can only be done safely by taking great care.
Since not all programmers care about security (they may have assumed thier lib would only be used with trusted data) and even those that do are imperfect this leads to lots of buffer overflows in C code.
both have some effect.
viruses in the dos days afaict spread in 3 main ways
1: warez (pretty much impossible to avoid viruses)
2: shareways and other legitimagely redistributable software
3: using the same read/write installation media on multiple systems.
4: accidental floppy booting
1 is a risk to any user that uses warez but linux users rarely do
2 and 3 were caused by insecure sources of legitimate software which isn't really an issue for any platform anymore (most legitimate software comes either straight from a trusted source over the network or from read-only optical media)
4 was pretty much unavoidable with the original pcs standard hardware architecture but remained an issue far longer than it had to due to bad bios designs (it would have been avoided if bioses had the hard drive first in the default boot order and encouraged use of an override key to floppy boot).
so out of the 4 only one was really something the platform could have done much about
imho there are two issues.
1: when coding with pointers/unchecked length arrays all it takes is one screwup even if you are trying to be carefull. Higher level structures and/or managed code can prevent this but at a cost in performance bloat and in the case of managed code ease of integration with traditional code.
2: the wmf/emf code is probablly very old from long long before the internet was commonplace. The idea of people deliberately creating image files to bypass security probablly didn't even occour to anyone.
which it usually isn't for reasons of performance,compatibility with existing systems in the os and the desire not to rewrite code unnessacerally.
.net calls for wmf and emf didn't call directly into the winapi functions for rendering wmf and emf.
i'd be very surprised if the
my understanding was that there would be a 2.7 if/when linus changes large enough were warranted and until then we were staying with 2.6.x versions.
the time i see people using this is if they are hooked on a series and for some reason miss and episode and haven't recorded it (either because they normally watch it when its on or they forgot to set the vcr or thier pvr crashed or whatever)
Streaming TV at broadcast quality requires a lot more bandwidth than most "broadband" ISP customers current get to their homes.
bullshit, digital terrestrial in the uk is iirc about 3 megabit/s and thats using pretty old tech (mpeg2 video mp2 audio). With a modern codec you could probablly halve that possiblly more bringing you WELL into the realm of what DSL can do.
the problem may come if everyone started doing it the links further upstream couldn't cope but that could be mitigated if isps could be persuaded to support IP multicast.
afaict they are releasing an opensource stub that links with a binary driver and the linux kernel.
this doesn't break every version like a full binary driver but is presumablly also extra work for them and it still breaks occasionally (iirc 4k kernel stacks did it).
if you are picking hardware for a linux box (e.g. you aren't just buying shit and hoping it works or trying to install on existing) the biggest problem driver wise seems to be 3D graphics. Its a two horse race and afaict neither really has drivers availible that are both good and opensource.
yeah running installers with custom drivers is a process thats often poorly documented and a pita which is a huge shame imo.
anyone fancy writing a little utility to produce custom bootdisks/driver disks for all the major distros?
you don't nessacerally need to make a full driver disk to the installers specs though just build the driver against the intallation kernel (requires finding headers for it but that shouldn't be too hard) and insmod it manually whilst running the installer.
yeah missing and misplaced breaks (if something has to be brought out of a switch for some reason and is inside a loop) can cause hell its kind of a design issue with the C switch statement that if you don't wan't fallthrough you have to explicitly tell it you don't.
C is an old language that is full of quirks. Its dervivitves have got rid of some but not all of those quirks.
the vast majority of sites use name-based virtual hosting
depends, if they are on commercial webhosing probablly but those run on home servers probablly won't unless the user wan'ts to host multiple sites.
i think the key is php is easy to learn incrementally. you can start with a tiny chunk of code, drop it in your webpage and it will actually do something and if you look at tutorials for php they all seem to be geared this way (i found this highly annoying as someone who can program and wanted to change something in a major php program, all the php tutorials i could find were not programmer orientated).
false color indeed has legitimage scientific value (using only greyscale is very wastefull of the eyes abilities) but i bet sometimes the settings are chosen to maximise the wow factor.
Einstein provided mathematical proofs in his groundbreaking articles IIRC
maybe he did but those proofs have to be based on axioms (things that are assumed true) and in the case of trying to predict the real world those have to be guessed. If those assumptions are wrong your mathematical proof is useless.
the aim in science is to find axioms that fit the current knowlage, allow sucessfull predictions to be made, and are no more complex than nessacery to do those two things.
However as our knowlage of the real world improves some of those axioms are going to be found false, thats progress.
humans are humans and provided they have decent fine motor skills should be able to do quite high level tasks in a single step and then report back when they are done.
machines just can't operate at that level yet without a very predictable environment (which the human body isn't really). I'd think the surgon on earth would be giving high level commands (cut this,join that etc) and the astronoughts would be turning those into start cutting stop cutting etc.
they are close here but they don't seem to be actually overlaping