Good points.. the question begging an answer, though, is "Do you have to use different cases if you don't want to?" It seems the OP has no place coding anyway, but if the case bothers them, then why use it..?
Problem is that it needs to be overturned.. if memory serves, the NZ patent system is similar to US in that if the PO grants the patent, it's by definition legal and therefore the proof of burden & other fun stuff is on whoever is trying this overthrowing of grant.
If you cared about the people, you'd inconvenience them temporarily by using standards-compliant code only. Hacking to suit the browsers will inconvenience a significant group of people perpetually.
Don't get me wrong, I understand the socio-economical factors here; I'm just saying that long-term, this would be a better choice.
>So what I'm saying is, if all you do when you dream is remember, except it seems real, removing that layer...then you might just remember being concious?
If you don't remember something, did it happen? Remembering is consciousness.
You can be aware in your dreams as well. The 'real' nature of sleep seems to be under investigation still, but lucid dreams (the kind where you know you're asleep and try to conjure Johnny D. or Orlando B. or Natalie P. naked before waking up) are a good example of verified awareness.
The inference was that if everyone wrote standards-compliant code, then the BROWSERS WOULD HAVE TO DISPLAY IT! Better sites and less buggy browsers. Geez.
>Technologies like JavaScript + CSS (=DHTML) are STANDARDS - they are created to use in web browsers. I use them wherever I need to, and code for MSIE and NS6+ (with a focis on the latest Mozilla release).
Interesting contradiction.
I say: do not find out what browser does what; find out what the respective standards say, and code according to that. Someone's browser will display it wrong, but that's mitigated by including the following disclaimer: "Your browser does not fully support the existing website standards, and you may suffer problems on other sites as well. You may continue to viewing the site, or you can download a standard browser here."
If more webdevs understood that, we wouldn't even have to have this discussion.
What I am saying is that it's irrelevant how the function is called. Using =~ instead of rx_replace() does not make a language better or worse suited for string manipulation. The algorithm used for the actual manipulation does. If Perl and PHP use the same algorithms, then they are by definition equally good in string processing.
What the hell does it matter how you *call* the function (aside from the PHP being clearer)? If you want to argue which is better, argue over the *implementation* of the replacing algorithm (which is probably going to be pretty much the same.)
As far as I can recall, the PHP text functionality lies in the compiled C modules, not the top-layer modules written in PHP. I could be wrong.
The GP states that doing E(arly)-L(ate)-E-L-E-L is better than doing L-E-L-E-L-E. However, both contain the 'worse' L-E sequences. Is it just a matter of which you start with (which I find hard to believe) or is this 'wrapping around' something else than just starting a new week?
So you basically create a website with perhaps a little form (fed to a PHP script for XML storage so it can be referred back to) to pick out food and paste this into the IM? Text has its uses; mundane family communication is not one of them.
Wireless controllers? Goddamn Slashdot crowd. Listen, why don't you JUST PUT YOUR DAMN TOYS AWAY when you're done with them instead of leaving them on the floor? Geez.
2) Buy 12 post-it notes (you can get more if you're on a high-end budget. But get a val-u-pak, then.) Also buy a pencil (not a pen -very important!)
3) If you don't have a wall or refrigerator door, get one.
4) For each month, take a post-it note, write the month's name on top. For each month-labeled post-it, write down the *name of company; *domain in question; *registrar used; *logins, passwords etc.; *contact information (which you update when it changes); *day the domain expires; *any other useful info (you can create a code for this so it's easier to store in the small space.)
5) Apply post-its in annual order to the wall or refrigerator door. If you store sensitive data such as the domain password for IBM, you can place the note *inside* the freezer box of the refrigerator. VERY secure.
You say Java is safer. I ask what if I add one of the many garbage collection libraries? One -or many- of the many smart pointer libraries? How about then?:)
> Handling sockets, connecting to databases of all kinds, web development, server-side processing, etc. are elegantly solved in Java.
No, they aren't. They're (elegance arguable) solved in the Java Standard Edition library.
I hate it when people tout Java because of its libraries. Give me a few weeks (and some cash for snacks) and I'll compile you a list of C++ libraries better and more extensive.
Slashdot Mirror
Good points.. the question begging an answer, though, is "Do you have to use different cases if you don't want to?" It seems the OP has no place coding anyway, but if the case bothers them, then why use it..?
I believe the parent referred to heap memory rather than pointers -and in this they are most likely correct.
The second part I agree with..
Etta nain.
Problem is that it needs to be overturned.. if memory serves, the NZ patent system is similar to US in that if the PO grants the patent, it's by definition legal and therefore the proof of burden & other fun stuff is on whoever is trying this overthrowing of grant.
> -- as an IT Pro at a small software company, --
What the hell are the rest of the people doing there, then?
Oh gee, don't anyone mention Hiroshima.
If you cared about the people, you'd inconvenience them temporarily by using standards-compliant code only. Hacking to suit the browsers will inconvenience a significant group of people perpetually.
Don't get me wrong, I understand the socio-economical factors here; I'm just saying that long-term, this would be a better choice.
>So what I'm saying is, if all you do when you dream is remember, except it seems real, removing that layer...then you might just remember being concious?
If you don't remember something, did it happen? Remembering is consciousness.
>(My total knowledge of subliminal messages comes from reading Brave New World. I have no real facts to back this post up.)
This is not true. Everything is al-right. This is not true. Everything is al-right.
You can be aware in your dreams as well. The 'real' nature of sleep seems to be under investigation still, but lucid dreams (the kind where you know you're asleep and try to conjure Johnny D. or Orlando B. or Natalie P. naked before waking up) are a good example of verified awareness.
I shouldn't dismiss it that hastily.
Well, there's the time he spent in the army (like all of us:P). No private showers there.
The inference was that if everyone wrote standards-compliant code, then the BROWSERS WOULD HAVE TO DISPLAY IT! Better sites and less buggy browsers. Geez.
>Technologies like JavaScript + CSS (=DHTML) are STANDARDS - they are created to use in web browsers. I use them wherever I need to, and code for MSIE and NS6+ (with a focis on the latest Mozilla release).
Interesting contradiction.
I say: do not find out what browser does what; find out what the respective standards say, and code according to that. Someone's browser will display it wrong, but that's mitigated by including the following disclaimer: "Your browser does not fully support the existing website standards, and you may suffer problems on other sites as well. You may continue to viewing the site, or you can download a standard browser here."
If more webdevs understood that, we wouldn't even have to have this discussion.
.
*breaks out the blackboard for drawing a picture*
What I am saying is that it's irrelevant how the function is called. Using =~ instead of rx_replace() does not make a language better or worse suited for string manipulation. The algorithm used for the actual manipulation does. If Perl and PHP use the same algorithms, then they are by definition equally good in string processing.
>PHP:
>$data = preg_replace("/hello/", "goodby", $data);
>Perl:
>$data =~ s/hello/goodby/;
What the hell does it matter how you *call* the function (aside from the PHP being clearer)? If you want to argue which is better, argue over the *implementation* of the replacing algorithm (which is probably going to be pretty much the same.)
As far as I can recall, the PHP text functionality lies in the compiled C modules, not the top-layer modules written in PHP. I could be wrong.
That's a good sign the design isn't very good. Mine is :)
> Which means you don't have predictable destruction. Which means you don't have destructors.
... ...
My GC does something like this:
1) Allocate memory, reference count 1
N-1) When ref count reaches 0, we call destroy() on the object
N) Free the memory
The GP states that doing E(arly)-L(ate)-E-L-E-L is better than doing L-E-L-E-L-E. However, both contain the 'worse' L-E sequences. Is it just a matter of which you start with (which I find hard to believe) or is this 'wrapping around' something else than just starting a new week?
That's *real* subtle.
So you basically create a website with perhaps a little form (fed to a PHP script for XML storage so it can be referred back to) to pick out food and paste this into the IM? Text has its uses; mundane family communication is not one of them.
Wireless controllers? Goddamn Slashdot crowd. Listen, why don't you JUST PUT YOUR DAMN TOYS AWAY when you're done with them instead of leaving them on the floor? Geez.
Very true. That's why capitalism will, also, fail. The greedy bastards don't know when to stop.
1) Go to Staples (or OfficeMax)
2) Buy 12 post-it notes (you can get more if you're on a high-end budget. But get a val-u-pak, then.) Also buy a pencil (not a pen -very important!)
3) If you don't have a wall or refrigerator door, get one.
4) For each month, take a post-it note, write the month's name on top. For each month-labeled post-it, write down the *name of company; *domain in question; *registrar used; *logins, passwords etc.; *contact information (which you update when it changes); *day the domain expires; *any other useful info (you can create a code for this so it's easier to store in the small space.)
5) Apply post-its in annual order to the wall or refrigerator door. If you store sensitive data such as the domain password for IBM, you can place the note *inside* the freezer box of the refrigerator. VERY secure.
Hope that helps!
.
I happen to like C++ more :)
:)
You say Java is safer. I ask what if I add one of the many garbage collection libraries? One -or many- of the many smart pointer libraries? How about then?
> Handling sockets, connecting to databases of all kinds, web development, server-side processing, etc. are elegantly solved in Java.
No, they aren't. They're (elegance arguable) solved in the Java Standard Edition library.
I hate it when people tout Java because of its libraries. Give me a few weeks (and some cash for snacks) and I'll compile you a list of C++ libraries better and more extensive.
> So now we have to have dominant and submissive hard drives???
'Top' and 'bottom' have fewer letters and are therefore the correct terminology.