Re: getting around lack of bool type support
- From: SM Ryan <wyrmwif@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 02 Jan 2008 07:25:06 -0000
Here's a clue for you.
Open a browser window to http://groups.google.com/
Click advanced search
Enter AtGdnXe7m7J9v-banZ2dnUVZ_rPinZ2d@xxxxxxxxxxxxxxxxxxxxx
as the message-id box.
Click Look Up Message.
Click on the subject line link.
Google will show you a tree of who followed whom. When. Where.
God knows why.
Click on a user name on the left and the message will appear
on the right.
Computers are marvelous. They can do all kinds of neat things
for you so you don't have to fight over 'he snipped my name'
'did not' 'did so' 'did not' with all the wit and wisdom
normally seen in a kindergarten playground.
You know with some advanced programming techniques you can
probably write a little tool that can do all the google
transactions, cookies, etc, so you can have an application
you drop a message id on, and it shows you the discussion
in google for you.
Golden California Girls <GldnCAGrls@xxxxxxxxxxx> wrote:
# Army1987 wrote:
# > Golden California Girls wrote:
# >
# >> Army1987 wrote:
# >>> Golden California Girls wrote:
# >>>
# >>>> Army1987 wrote:
# >>>>> Malcolm McLean wrote:
# >>>>>>> #define TRUE -1 is also very neat.
# >>>>> Why did you precede that line by >? it was not in the post you were
# >>>> Your newsreader must have missed a message
# >>> Even if it has, someone used a wrong number of > signs.
# >>> The lines " #define TRUE 1 #define YES 1" and "#define TRUE -1 is ..."
# >>> appear to be both by user923005, whose message I have, but the latter line
# >>> doesn't appear there.
# >> It appears as if Malcolm started his response with a ">" character. Likely was
# >> on the wrong line when he typed it. My newsreader does have a blank line
# >> between his response and the quoted material above.
# >
# > And what I asked to Malcom was exactly why did he add a > at the beginning
# > of the line.
# >
#
# My threading says you asked Keith, but not the quoting.
#
# Not important.
#
#
--
SM Ryan http://www.rawbw.com/~wyrmwif/
The whole world's against us.
.
- Follow-Ups:
- Re: getting around lack of bool type support
- From: Walter Roberson
- Re: getting around lack of bool type support
- References:
- Re: getting around lack of bool type support
- From: Golden California Girls
- Re: getting around lack of bool type support
- Prev by Date: Problem with fork inside a thread and execv()
- Next by Date: Re: Definition of expression and statement.
- Previous by thread: Re: getting around lack of bool type support
- Next by thread: Re: getting around lack of bool type support
- Index(es):
Relevant Pages
|
