From: Jeff Higgins on
On 5/20/2010 9:13 AM, Lew wrote:
> Jeff Higgins wrote:
>> What's the difference between the phrases "the heck with you", and "to
>> heck with you"?
>
> None in meaning - I've heard both over the years. They're colloquial, so
> variations occur. OTOH, you would utter in astonishment, "The heck you
> say!" but not, "To heck you say!"

I was thinking dismissal and banishment, but either way: Ok.

>
> As for your other post, Jeff, AIUI there are Internet connections in
> heck, but only over dialup. Luckily for Arne and Eric, my powers
> actually to banish someone to heck are protected by a giant mirror and I
> only wind up sending myself there.
>

Whew! Thank goodness all three will still be able to participate.


From: Lew on
Lew wrote:
>> "Cuz" is not a formal word in English. Informally or slangily, its
>> primary meaning is "cousin". It is also listed as "an attempt to
>> represent the lazy pronunciation of because."
>> http://dictionary.reference.com/browse/cuz

ClassCastException wrote:
> Interesting, but I fail to see the relevance to Java programming.

Sometimes in this free-speech forum people bring up secondary points. This
one was relevant only insofar as it addressed how someone chose to communicate
in a post to a Java discussion forum. Had the post been to a C# forum it
would have been less relevant to a Java discussion.

Much as Roedy will encourage people to avoid the lazy and, to him, offensive
use of "wanna" for "want to", I sometimes find lazy, stupid and questionable
English usage grating. This does not apply to those doing their best to
express themselves in a foreign language, but simple things like spelling
"Java" correctly, or spelling "you" instead of "u" or "because" instead of
"cuz" just represent a habit of diligence and completeness that spills over
into code.

If someone is too lazy and illiterate to spell "because" or risk
misunderstanding because "cuz" really abbreviates for "cousin", then perhaps
they are careless with Javadocs, or logging, or unit tests, or covering all
possible inputs to a method. OTOH, in the OP's case I am quite sure it was
not laziness or stupidity, but I thought the facts about the word were
interesting enough to post. Furthermore, I anticipated that mentioning those
facts would stimulate discussion and give me the opportunity to put in a pitch
for professionalism and a habit of diligence.

--
Lew
From: ClassCastException on
On Thu, 20 May 2010 09:22:38 -0400, Lew wrote:

> ClassCastException wrote:
>> Interesting, but I fail to see the relevance to Java programming.
>
> Sometimes in this free-speech forum people bring up secondary points.

Don't get all sanctimonious with me. It looked suspiciously to me like an
off-topic criticism of another poster, and its motive was therefore
probably pretty base.

> I sometimes find lazy, stupid and questionable English usage grating.

Fine. But it's not the topic of this newsgroup, and on at least some
points of English usage, opinions are liable to differ.

> If someone is too lazy and illiterate to spell "because" or risk
> misunderstanding because "cuz" really abbreviates for "cousin", then
> perhaps they are careless with Javadocs, or logging, or unit tests, or
> covering all possible inputs to a method.

This seems like quite a stretch. Fine effort at rationalization, though,
and at trying to shoehorn it in as tangentially on topic. :)

> OTOH, in the OP's case I am quite sure it was not laziness or
> stupidity, but I thought the facts about the word were interesting
> enough to post. Furthermore, I anticipated that mentioning those facts
> would stimulate discussion

Well, that it certainly did -- off-topic discussion. Congratulations on
lowering the SNR of this once-fine newsgroup slightly. :)

Now I shall probably endeavor to avoid making it any worse by dropping
this. Unless of course a particularly egregious response gets posted.
From: Jim Janney on
Jimmy <jimmy_please(a)yahoo.com> writes:

> Below are the example of possible input strings:
>
> myparam1=myvalue1&param1=value2&param3=value3
> &myparam1=myvalue1&param1=value2&param3=value3
> ?myparam1=myvalue1&param1=value2&param3=value3
> "myparam1=myvalue1&param1=value2&param3=value3"
> "&myparam1=myvalue1&param1=value2&param3=value3"
> "?myparam1=myvalue1&param1=value2&param3=value3"
>
> I like to replace value of "param1" with "somevalue". Can it be done
> in 1 expression replacement? Cuz pattern [\"&?]* works for searching,
> but reusing the same pattern will get rid of the first non-alpha
> character.


String input = "&myparam1=myvalue1&param1=value2&param3=value3";
String replaced = input.replaceAll("\\bparam1=\\w+", "param1=somevalue");

--
Jim Janney
From: Daniel Pitts on
On 5/20/2010 10:26 AM, Jim Janney wrote:
> Jimmy<jimmy_please(a)yahoo.com> writes:
>
>> Below are the example of possible input strings:
>>
>> myparam1=myvalue1&param1=value2&param3=value3
>> &myparam1=myvalue1&param1=value2&param3=value3
>> ?myparam1=myvalue1&param1=value2&param3=value3
>> "myparam1=myvalue1&param1=value2&param3=value3"
>> "&myparam1=myvalue1&param1=value2&param3=value3"
>> "?myparam1=myvalue1&param1=value2&param3=value3"
>>
>> I like to replace value of "param1" with "somevalue". Can it be done
>> in 1 expression replacement? Cuz pattern [\"&?]* works for searching,
>> but reusing the same pattern will get rid of the first non-alpha
>> character.
>
>
> String input = "&myparam1=myvalue1&param1=value2&param3=value3";
> String replaced = input.replaceAll("\\bparam1=\\w+", "param1=somevalue");
>
Sounds good unless value2 is actually "abc%2C123", in which case \\w+
won't properly match.

Like I've said elsewhere, the least fragile approach is to actually
parse the string and re-create it. Regex hacks might work, but they
might fail in unexpected ways.

--
Daniel Pitts' Tech Blog: <http://virtualinfinity.net/wordpress/>