Sometimes its a lot easier to maintain 30 well-written 10-line methods than to build a complex 300-line structured program.
What? I thought it always is. There is one caveat: 300 lines of structured program easily transfer to 400 to 500 lines of methods (C), or 500 to 1000 lines of classes and methods (Java).
The result probably is a more undestandable and dense main program.
It can and does happen with java, but a mess is easier to achieve with perl. Java doesn't have "use strict", because it is the only way. (And yes, any sensible (perl) programmer has that in his/her mind as the only way).
How is that even the tiniest bit different than what a video camera hooked up to a TV does?
Superficially, it isn't, but imagine that you would want to project to every direction possible direction, or even every probable viewing direction. How do you decide what is probable direction? How do you get the image from every probable directions behind?
Then, to illustrate: How many directions there are in an angle? ir one degree enough to not look jumpy, or do you need radians, minutes or seconds?
I can't see why this kind of setup would require a certain coding style. All that is needed is knowledge of the syntax and a parser. As far as I can see, the parser does not need to fully understand the language, just the basics like blocks, functions (methods), variables (attributes) and of course comments (and inner comment syntax like javaDoc).
I do hope you are not one that complains about bloat too? See, either you co-ordinate the solutions or you bloat the source by providing a separate fix for everything.
And bloat is not the most dangerous thing about it. Without co-ordination you get different behavior in cases that require similar behavior.
To be more specific, the problem is that Mozilla does not cache the result of a posted query. When you view the source, it posts the query again. Now if the server has somekind of unique id to a query or timestamp has gone stale, the result does not match the original.
This really lessens Mozillas usefulness as a test tool for a web project as you are not guaranteed to see the original source. I haven't checked the situatiopn for a while, but I believe the fix is going to be post 1.0.
Hmm, my italian friends explained it a bit differently (or I remember wrong...), but actually this fills in the gap of how the nomination and symbol traveled to england.
How are they gonna pull this 90-day warranty in the european union, where the maker has to give you a reasonable warranty.
In the case of consumer electronics it is usually at least one year, or in the case of washing machines etc. reasonable
warranty is 3 to 5 years.
As I see it, that would be against the idea, the scene is there to make new cool stuff, not to upgrade the old stuff. That way it would die horribly and pretty quick. The cool thing though, would be to hack a generic 486DX/33+GUS emulator to play these in...
I partially agree. In my thinking this only applies with the self-made men. Inherited wealth and accumulating that wealth with the help of paid professionals is another thing.
Yes you could. If you defined a protocol or a strict format for the communicates things. E.g. it could be based on a XML-dtd. If the thing written to fd 3 doesn't follow this format it is not shown.
OTOH you could define the stream to be what ever say 61873 and be fairly sure it is not used in a manner that would conflict with this.
Third way: Lets say all this was in a library called stdinfo.h. We could have a call to some notification function that would check if the env supported STDINFO and if so, then notify the environment about the possibility that this program may use it. The return value could be the stream number that is used for STDINFO in this system (I don't exactly remember how the std pipes are created, so I don't know if this is feasible, but it's an idea anyway). Now subsequent output to that stream would go to env/shell that takes care of the rest.
Dirk Gently's ill-fated couch not withstanding, it is funny to see the fuss that brute-force methods of solving mathematical problems have produced. The question seems to be this: is an 'elegant' proof tomorrow better than an ugly one today?
There is, of course, the possibility of similar but not identical problems
sharing a common solving method coming in the future. Cumulutavely this may
be faster than brute force. (And I'm sure there are people that like to, or
rather, want to, solve 2nd degree polynomial by extrapolation.)
The dual citizenship won't work because Finland doesn't accept that. According to the finnish law, only minors can have dual citizenship.
When a finn over 18(?) years gets another countrys citizenship h[is|er] finnish citizenship expires. If not by announcement from the new country, then finally when entering Finland with that countrys passport. (This IIRC, has happened to one finnish NHL player, maybe Esa Tikkanen. Anyway, he got his finnish citizenship back later by an application.)
As I see it, this would be curing the symptoms not the cause.
Some characters at the beginning of the message seem to have a special meaning for Nokia phones. A friend of mine sent ascii graph chistmas greetings, but most Nokia phone owners didn't see them, because the message begun with asterisk, which seems to indicate that a control sequence begins.
Well, a kind of throw-away phones are on the market here in Finland. Many big supermarkets sell old soap-box Motorolas for 99 FIM (about US$15). Practically at this cost you can throw the thing away when the battery performance dwindles, because a new phone costs less than a new battery (I would not buy the thing, instead I'd buy 2nd hand Ericsson or Nokia for twise the price).
In the US the majority are CDMA. AFAIK most cellphones in the world use TDMA techniques (GSM/DCS, and the japanese 2gen tech). These euro-japanese dominated markets are moving towards a mixture of these, the T-CDMA.
On the topic now for a moment: Will we really be using broadcast radio for long i.e. more that 50 years? I can't see that we will need it for anything apart from communication in unpopulated areas, if even there.
Slashdot Mirror
What? I thought it always is. There is one caveat: 300 lines of structured program easily transfer to 400 to 500 lines of methods (C), or 500 to 1000 lines of classes and methods (Java).
The result probably is a more undestandable and dense main program.
It can and does happen with java, but a mess is easier to achieve with perl. Java doesn't have "use strict", because it is the only way. (And yes, any sensible (perl) programmer has that in his/her mind as the only way).
A Ford is a Ford is a Volvo. Been a few years now.
I seem to recall that the new Thunderbird even shares the chassis (or platform, to be precise) with Volvo S60 (and Jaguar X-type and for Mondeo).
How is that even the tiniest bit different than what a video camera hooked up to a TV does?
Superficially, it isn't, but imagine that you would want to project to every direction possible direction, or even every probable viewing direction. How do you decide what is probable direction? How do you get the image from every probable directions behind?
Then, to illustrate: How many directions there are in an angle? ir one degree enough to not look jumpy, or do you need radians, minutes or seconds?
Switzerland (might depend on the canton)y
Finland
Sweden
Norway
Austria
German
Estonia
New Zealand
Australia
Federal translates to national where not applicable.
Now tell me where you can hang out in the parking lot of fast food diner without getting (rent-a)cops to chase you away?
I can't see why this kind of setup would require a certain coding style. All that is needed is knowledge of the syntax and a parser. As far as I can see, the parser does not need to fully understand the language, just the basics like blocks, functions (methods), variables (attributes) and of course comments (and inner comment syntax like javaDoc).
I do hope you are not one that complains about bloat too? See, either you co-ordinate the solutions or you bloat the source by providing a separate fix for everything.
And bloat is not the most dangerous thing about it. Without co-ordination you get different behavior in cases that require similar behavior.
To be more specific, the problem is that Mozilla does not cache the result of a posted query. When you view the source, it posts the query again. Now if the server has somekind of unique id to a query or timestamp has gone stale, the result does not match the original.
This really lessens Mozillas usefulness as a test tool for a web project as you are not guaranteed to see the original source. I haven't checked the situatiopn for a while, but I believe the fix is going to be post 1.0.
Hmm, my italian friends explained it a bit differently (or I remember wrong...), but actually this fills in the gap of how the nomination and symbol traveled to england.
I was going ask if there has, at some point some where in history, been equivalence with one pound currency and one pound of some matter, but I then did the reseach my self and found that livre was "A money of account formerly used in France and originally worth a pound of silver".
a state they [pound sterling] shared with the Italian lire
This must have something to do with the monetary symbol "£", which of course originally means lire. Wasn't the turkish Lire also very unstable?
Ok, for convenience, we'll change e to be equal to three.
But there are only two of those on a normal person!
How are they gonna pull this 90-day warranty in the european union, where the maker has to give you a reasonable warranty.
In the case of consumer electronics it is usually at least one year, or in the case of washing machines etc. reasonable
warranty is 3 to 5 years.
Yeah, in the worst case it means going to court.
As I see it, that would be against the idea, the scene is there to make new cool stuff, not to upgrade the old stuff. That way it would die horribly and pretty quick.
The cool thing though, would be to hack a generic 486DX/33+GUS emulator to play these in...
bullets aren't steerable and they're still the most commonly used munition :)
Yes, but they aren't that cost-effective against the targets that guided missiles are used for. Say, an aircraft carrier.
Me too. Yes, I'm willing to moderate, but this is getting to be tiring.
I partially agree. In my thinking this only applies with the self-made men. Inherited wealth and accumulating that wealth with the help of paid professionals is another thing.
> You mean you _ever_ would have?
How do you think he knows about the MC smartcards?
Yes you could. If you defined a protocol or a strict format for the communicates things. E.g. it could be based on a XML-dtd. If the thing written to fd 3 doesn't follow this format it is not shown.
OTOH you could define the stream to be what ever say 61873 and be fairly sure it is not used in a manner that would conflict with this.
Third way: Lets say all this was in a library called stdinfo.h. We could have a call to some notification function that would check if the env supported STDINFO and if so, then notify the environment about the possibility that this program may use it. The return value could be the stream number that is used for STDINFO in this system (I don't exactly remember how the std pipes are created, so I don't know if this is feasible, but it's an idea anyway). Now subsequent output to that stream would go to env/shell that takes care of the rest.
No fork, but what about CreateProcess()?
More about differences in process models in here.
(This IIRC, has happened to one finnish NHL player, maybe Esa Tikkanen. Anyway, he got his finnish citizenship back later by an application.)
Some characters at the beginning of the message seem to have a special meaning for Nokia phones. A friend of mine sent ascii graph chistmas greetings, but most Nokia phone owners didn't see them, because the message begun with asterisk, which seems to indicate that a control sequence begins.
Many big supermarkets sell old soap-box Motorolas for 99 FIM (about US$15). Practically at this cost you can throw the thing away when the battery performance dwindles, because a new phone costs less than a new battery (I would not buy the thing, instead I'd buy 2nd hand Ericsson or Nokia for twise the price).
In the US the majority are CDMA. AFAIK most cellphones in the world use TDMA techniques (GSM/DCS, and the japanese 2gen tech). These euro-japanese dominated markets are moving towards a mixture of these, the T-CDMA.
On the topic now for a moment: Will we really be using broadcast radio for long i.e. more that 50 years? I can't see that we will need it for anything apart from communication in unpopulated areas, if even there.