ok, one more question, if i may. i got some feedback that this code is wrong entirely, but i'm not sure what i think of it because this code has a chance of sort of being understood by non-cody people, whereas the new suggestion doesn't, i think.
BUT. if this one is really that wrong then i should find some good balance between the 2.
SELECT a.*, b.* FROM persons AS a INNER JOIN persons AS b ON a.heart + b.heart = 1
Re: I put work into this, LOVE it. =)superjillDecember 1 2006, 00:05:09 UTC
<3 <3 <3 <3 <3 <3 <3 <3 <3 <3 <3 <3 <3 <3
*LOVE*
You should add this to your poem repertoire. Really.
This reminds me of when we were working on my geek poerm at your house in August.
I still have the similar logic love poem you wrote in my book.
(∃x)(Fx) -> (∃y)(Lyj)
Kylie, we should run away together and have artsy fartsy logic babies. The world will thank us for our powerful contribution(s) to society, in the form of demented little genius beings.
Comments 17
while(u & i > 0) {
fun++;
}
Reply
does that mean that the code that's already there is in good form?
Reply
while(u *look = &i[smile]) {
heart++;
difference[you][me]--;
}
also, you may find join syntax differs depending on the flavour of SQL. loosely,
select a.name,b.name from person a,person b
where a.heart + b.heart = 1;
Reply
I'd get tsked for not putting the i.heart++ i { } s, though.
while (u.breathing == true ){
i.heart++
}
Also, to avoid the chance of a typo type bug,
you should do it as
while( true == u.breathing ){
i.heart++
}
Reply
Reply
so unless people who have been geeks more currently than us speak up....
got thoughts on if/how i can include the pointer? it's kinda humorous but i don't know if i can fit it in.
Reply
Personally, I preferred the original, simpler code. Or even this simpler version.
while (u.breathing)
i.heart++;
Reply
SELECT a, b FROM persons WHERE (a.heart + b.heart) = 1
(only one = )
that would involve objects being stored in the database, which I'm not familiar with.
Maybe something like
SELECT a.name, b.name
FROM persons a
, persons b
WHERE a.heart + b.heart = 1
although to that you should add
AND a.heart > 0
AND b.heart > 0
because you wouldn't want one of those people to be heartless now would you?
I'm not sure what attribute of the persons table you would want to select... maybe this should be the select clause
SELECT a.name || ' & ' || b.name || ' 2gether 4ever'
Reply
i'm digging the middle section suggestion.
is there a reason for the tables to be listed on separate lines?
the heartless thing made me *laugh*.
if i add those, they should be appended at the end?
if no one is answering about my pointer question fer the c++ code, does that mean i should drop it? no pointer?
Reply
SELECT a.name, b.name
FROM persons a
, persons b
WHERE a.heart + b.heart = 1
AND a.heart > 0
AND b.heart > 0
and yes, each of the persons on different lines is style, the following is completely acceptable and works
SELECT a.name, b.name
FROM persons a, persons b
WHERE a.heart + b.heart = 1
AND a.heart > 0
AND b.heart > 0
Reply
i got some feedback that this code is wrong entirely, but i'm not sure what i think of it because this code has a chance of sort of being understood by non-cody people, whereas the new suggestion doesn't, i think.
BUT. if this one is really that wrong then i should find some good balance between the 2.
SELECT a.*,
b.*
FROM persons AS a
INNER JOIN persons AS b ON a.heart + b.heart = 1
Reply
(The comment has been removed)
<3 <3 <3 <3 <3 <3 <3
*LOVE*
You should add this to your poem repertoire. Really.
This reminds me of when we were working on my geek poerm at your house in August.
I still have the similar logic love poem you wrote in my book.
(∃x)(Fx) -> (∃y)(Lyj)
Kylie, we should run away together and have artsy fartsy logic babies. The world will thank us for our powerful contribution(s) to society, in the form of demented little genius beings.
Reply
Leave a comment