deanyourfriendinky

Since I ve updated Firefox to version 57 (a.k.a. Quantum), I no longer get the category menu on the left-hand side of the Yahoo! Answers front page.

What must I do to get the category menu back? Or, how can I access the category list a different way? Either answer would be acceptable to me.

https://www.yahoo.com/news/dad-sentenced-life-pris...

Learning C++ from a book.

I set a value for an unsigned long int called red:

unsigned long int red = 0xFF0000UL;

The hexadecimal output of red is: 0x00FF0000

Which is what I expected.

However, the output for ~red is:

FFFFFFFFFF00FFFF

Which is definitely not what I expected.

I expected FF00FFFF

I'd like to know whether Yahoo! has fixed its Heartbleed vulnerability and gotten "new cryptographic locks"?

I'm so glad that I don't do anything really important through Yahoo!

I've noticed that a number of folks who ask and/or answer questions have the code "'" where apostrophes should be.

Why don't their apostrophes show up explicitly, rather than showing up as numeric codes?

I'm using Firefox 27.0. I've tried the code-pages Windows-1252, ISO-8859-1, ISO-8859-15, and UTF-8. No matter which code-page I define for Firefox, those answers where an apostrophe should be (but where &#x27 appears instead) remain the same.

I'm curious as to what specific knowledge about Website technologies that Kathleen Sebelius has. Is she privy to HTML, CSS, JavaScript, Java, Flash, and/or database technologies? Is she knowledgeable enough about any of these technologies (1) to bear the blame for the glitches from which healthcare.gov suffers and/or (2) to assist in the repair of those glitches?

I've been looking for such information via Google, but so far all I've found is political and social commentary (except for her bio on wikipedia.org, which seems to have no information about her technical education).

None of the ndiswrapper solutions anywhere on the Internet will work for the WNDA3100v2 USB Wi-Fi adapter. I have tried all of the solutions I can find. They ALL fail.

Will the WNDA3100v2 ever work on any GNU/Linux-based distro using kernel 3.x or later?

I'd ask in a forum, but since all of the solutions that I've found in Linux forums for this issue fail, I thought it would be fun to see what kind of answers turn up here.

I'm a beginner at C++

Short version of my problem:

Why would cout << tolower(user_input) result in a three-digit numeric value being output to the screen when user_input has been declared/defined as char user_input = 0; ?

Long version of my problem:

I had an assignment to create a program that prompts the user for a letter, determines whether the letter is a vowel or a consonant, determines whether it is uppercase or lowercase, and outputs the lowercase form as well as the binary value of the user's input. So I coded the program, but I had a little snafu with the second to the last section of it, the section titled "OUTPUT THE LOWERCASE VALUE OF THE LETTER IN ITS EXPLICIT FORM"

#include <iostream>

#include <cctype>

using std::cin;

using std::cout;

using std::endl;

using std::isalpha;

using std::islower;

using std::tolower;

int main() {

// EXPLAIN THE PROGRAM TO THE USER

cout << "\n\tThis program solicits a letter from you, determines whether the letter is"

<< "\n\ta vowel or a consonant, determines whether it is lowercase or uppercase,"

<< "\n\toutputs thelowercase form of the letter, and outputs the binary value of

<< "\n\tthe letter."

<< endl;

// DECLARE/DEFINE VARIABLE IN WHICH TO STORE USER'S INPUT

char user_input = 0;

// SOLICIT USER'S INPUT

cout << "\n\tPlease enter a letter:\t";

cin >> user_input;

// DETERMINE WHETHER THE LETTER IS A VOWEL

if(isalpha(user_input)) {

switch(user_input) {

case 'a': case 'e': case 'i': case 'o': case 'u':

case 'A': case 'E': case 'I': case 'O': case 'U':

cout << "\n\tThe letter you entered is a vowel.";

}

// DETERMINE WHETHER THE LETTER IS A CONSONANT

switch(tolower(user_input)) {

case 'b': case 'c': case 'd': case 'f': case 'g': case 'h': case 'j':

case 'k': case 'l': case 'm': case 'n': case 'p': case 'q': case 'r':

case 's': case 't': case 'v': case 'w': case 'x': case 'y': case 'z':

cout << "\n\tThe letter you entered is a consonant.";

}

// DETERMINE WHETHER THE LETTER IS IN ITS LOWERCASE FORM OR ITS UPPERCASE FORM

if(isupper(user_input)) {

cout << "\n\tYou entered the uppercase form of the letter.";

} else {

cout << "\n\tYou entered the lowercase form of the letter.";

}

// OUTPUT THE LOWERCASE VALUE OF THE LETTER IN ITS EXPLICIT FORM

if(isalpha(user_input)) {

char glitch = tolower(user_input);

cout << "\n\tThe lowercase form of the letter is:\t"

<< glitch;

}

// My original layout of the preceding section, which is where I had a problem,

// follows the 'return' statement below.

// OUTPUT THE BINARY VALUE OF THE LETTER

if(isalpha(user_input)) {

cout << "\n\tThe binary code for the letter \'" << user_input << "\' is:\t"

<< ((user_input & 0x80) ? 1 : 0) << ((use r_input & 0x40) ? 1 : 0)

<< ((user_input & 0x20) ? 1 : 0) << ((user_input & 0x10) ? 1 : 0)

<< ((user_input & 0x08) ? 1 : 0) << ((user_input & 0x04) ? 1 : 0)

<< ((user_input & 0x02) ? 1 : 0) << ((user_input & 0x01) ? 1 : 0);

}

} else {

cout << "\n\tThe character you entered is not a letter!";

}

cout << endl << endl;

return 0;

}

*/

* The original version of the problematic section was:

*

* // OUTPUT THE LOWERCASE VALUE OF THE LETTER IN ITS EXPLICIT FORM

* if(isalpha(user_input)) {

* cout << "\n\tThe lowercase form of the letter is:\t"

* << tolower(user_input);;

* }

*

* But this version kept outputting a three-digit numeric value, rather than an explicit

* alphabetic character. I resorted to creating a new variable of the data type 'char'

* and assigning to it the value of the original user-input value of 'user_input'

* because it was the only way I could get the original user-input character to appear

* on the screen.

*

* All the rest of the program did as I expected, and the only compile-time problems that

* I had were forgotten semicolons and parentheses, which I fixed in accordance with the

* compiler's error notifications.

*/

For the record, I used the text-editor Kate to code the program and I used the g++ front-end of the GCC 4.5.2 to compile it --- using a terminal (command prompt, if you prefer).

How can I fix the following mess? Sprint has committed fraud against me!

In 2005 I bought a Sprint cellphone from the Wal-Mart cellphone kiosk in the electronics department. The contract was for 1 year. A few days before the contract was due to expire in 2006, I called Sprint to make sure that everything was in order for the contract to expire.

The agent with whom I spoke said that the contract was for two years. I have the original contract which clearly states that the contract was for one year.

Sprint unilaterally declared my original 1-year contract as a 2-year contract (even though I had the Wal-Mart cellphone kiosk person call them to verify that the contract is for 1 year). The Sprint person implied that the Wal-Mart cellphone kiosk agent and I were both liars.

Sprint has turned my contract over to a collection agency because I have refused to submit to Sprint's fraudulent claim that my contract with them is for two years.