auto

请使用0.9以后的版本： 示例代码 Properties props = new Properties(); props.put("bootstrap.servers", "kafka01:9092，kafka02:9092"); props.put("group.id", "test"); props.put("enable.auto.commit", "true"); props.put("auto.commit.interval.ms", "1000"); props.put("key.deserializer", "org.apache.kafka.common.serialization.StringDeserializer"); props.put("value.deserializer", "org.apache.kafka.common.serialization.StringDeserializer"); props.put("auto.offset.reset","earliest"); KafkaConsumer<String, String> consumer = new KafkaConsumer<>(props); consumer.subscribe(Arrays.asList("foo", "bar")); try{ while (true) {

Does C++11 allow declaring non-static data members as 'auto' if they are initialized in the declaration? For example: struct S { auto x = 5; // in place of 'int x = 5;', which is definitely allowed }; GCC 4.7 rejects the above code, while it accepts int x = 5; . Assuming this is not a compiler bug but rather the standard really doesn't allow it, why not? It would be just as useful as declaring local variables auto . The rule for prohibiting non-static members is in 7.1.6.4 clause 4: The auto type-specifier can also be used in declaring a variable in the condition of a selection statement (6.4)

Possible Duplicate: How much is too much with C++0x auto keyword Have we (as a community) had enough experience to determine when and/or whether auto is being abused? What I am really looking for is a best practices guide on when to use auto when it should be avoided Simple rules of thumb that can quickly be followed in 80% of cases. As a context this question is sparked by my response here I think when the type is very well-known amongst the co-programmers who work (or would work) in your project, then auto can be used, such as in the following code: //good : auto increases readability here

class Foo { public: static const char *constant_string; }; auto Foo::constant_string = "foo"; int main(void) { }; Compiled with: gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 like this: gcc -std=c++0x ./foo.cc ./foo.cc:6:11: error: conflicting declaration ‘auto Foo::constant_string’ ./foo.cc:3:22: error: ‘Foo::constant_string’ has a previous declaration as ‘const char* Foo::constant_string’ ./foo.cc:6:11: error: declaration of ‘const char* Foo::constant_string’ outside of class is not definition [-fpermissive] Is this intended behavior of the auto keyword, or a bug in gcc+ Lightness Races in Orbit

Given my variable being a pointer, if I assign it to a variable of "auto" type, do I specify the "*" ? std::vector<MyClass> *getVector(); //returns populated vector //... std::vector<MyClass> *myvector = getVector(); //assume has n items in it auto newvar1 = myvector; // vs: auto *newvar2 = myvector; //goal is to behave like this assignment: std::vector<MyClass> *newvar3 = getVector(); I'm a bit confused on how this auto works in c++11 (this is a new feature to c++11, right?) Update: I revised the above to better clarify how my vector is really populated in a function, and I'm just trying to

Please take a look at the following simple code: class Foo { public: Foo(){} ~Foo(){} Foo(const Foo&){} Foo& operator=(const Foo&) { return *this; } }; static Foo g_temp; const Foo& GetFoo() { return g_temp; } I tried to use auto like this: auto my_foo = GetFoo(); I expected that my_foo will be a constant reference to Foo , which is the return type of the function. However, the type of auto is Foo , not the reference. Furthermore, my_foo is created by copying g_temp . This behavior isn't that obvious to me. In order to get the reference to Foo , I needed to write like this: const auto& my_foo2

检索或设置当对象的内容超过其指定高度及宽度时如何管理内容。 所有对象的默认值是 visible ，除了 textarea 对象和 body 对象的默认值是 auto 。设置 textarea 对象此属性值为 hidden 将隐藏其滚动条。 overflow属性有四个值： visible (默认), hidden , scroll , 和 auto 。 同样有两个overflow的姐妹属性overflow-y 和overflow-x，它们很少被采用。 1、Visible 如果你不设置overflow属性，则默认的overflow属性值就是visible。所以一般而言，并没有什么理由特别的设定overflow的属性为visible除非你想覆盖它在其它地方被设定的值。 这里需要记住的重要的事情是，尽管盒子外面的内容是可见的，内容并不会影响页面的工作流。比如： 一般来说，你至少不用为里面的内容为文字的盒子设置固定的高度，这样就不会遇到这种情况了。 2、Hidden 默认值visible的相反的值就是 hidden 。它会将所有超出盒子的所有内容都给隐藏掉。 这对应付使用动态的内容，而且可能会由于内容溢出而引起 一些布局上的问题 的确很有用。尽管如此，请记住用此方法隐藏的内容将彻底的看不到(除非去查看源代码)。 比如有的用户设置他们的浏览器的默认 字体 比你预期的要大些