Search:

ok so to get 01777777777777777777777 I need 2 do uint64_t x = (uint64_t)-1?

Ok, so what happens here?



int64_t x = (unsigned)-1;


On a 32-bit system? x contains 01777777777777777777777 or 037777777777?

Ok, but is the truncation because of the return type or because of the lack of specifying what type is signed?

Well....



#include <iostream>
#include <new>

int main( int argc, char** argv )
{
try

I do not speak english very well and I was wondering if you guys thing that if I wear green socks today at work I will look more english speaking or if I am smarter just to stick with my normal tan...

Ok, so someone please explain the following to me.



#include <stdint.h>

int64_t a = 0;
uint32_t b = 1;

int32_t main(void)

U r so rite anon you are so much more helpful than anyone else who posts here! Thank you so much.

I fuxed the other code with the currection by CormedBee.



#include <iostream>
#include <stdlib.h>
using namespace std ;

int main( int argc, char* argv[] )
{

They always force things I do not understand on me. Lyk look at std::iterator. What is that for anyway? And all of the algorithm header is greek to me.

The end user of compilers is the developer, correct? But I suppose you are right. That is what makes us the end users and not the developers.

#include <iostream>
#include <stdlib.h>
using namespace std ;

void main( int argc, char* argv[] )
{
int marks[5] ;
int total = 0 ;

for ( int i = 0; i < 5 && i < argc; i++)

Give you a block of memory? calloc() and malloc() (stdlib.h)
Tells you when a character is not a space? isalnum() (ctype.h)
Also you could simply say !isspace() (ctype.h)

Which is why stuff from Boost should stay in boost and stuff from the STL should stay in the STL. Then you have the right to choose whether or not to use it instead of it being thrust upon you.

One of the biggest problems with committees is that they infringe upon the freedom of the end user to decide what stays and what goes. Its rather elitist, do you not concur?

If it were not limited, it would not require the user to input a "guess."

Wut libwewy duz dis ooze?

Interesting. I wonder if any of the members here are part of the standards committee. Then we could know which things will make the cut before the rest of the world :)

I don't see how that is a hugely beneficial addition to the language, but I am sure someone will argue that it is. It opens the door to "We need to have a function that returns 16 values!"

My wife made me go to tuples counseling once. I did not like it. I do not fully understand what a smart pointer is for. Will they completely remove the ability to use normal pointers in C++!?

How much Boost stuff will be added into the STL?

Ok so in other words it is something that someone should probably not learn unless they want to teach C++, right?

struct stacker {
long a
struct stacker *p;
} stack = {0,0};

void push(long a)
{
struct stacker **p;
for(p = &stack->p; *p; *p = (*p)->p) ;
*p = malloc(sizeof(**p));

What is boost for?

I think what he says is a book with othur named Herbie rote a book by the name of "Teach Yourself C"

My idea may not work if the class is polymorphic, which it may be.