Hi,
I don't know who generates the c99.tags, but it would be cool if the next release of Geany had the `size_t` symbol in its default tags. I can't get Geany to parse my GNU headers using create_c_tags.sh script (or otherwise), but even just copying the line for `ssize_t` and dropping the first S works well enough to get auto-completion and highlighting of this symbol.
Cheers, Matthew Brush
On 15 September 2011 00:33, Matthew Brush mbrush@codebrainz.ca wrote:
Hi,
I don't know who generates the c99.tags, but it would be cool if the next release of Geany had the `size_t` symbol in its default tags. I can't get Geany to parse my GNU headers using create_c_tags.sh script (or otherwise), but even just copying the line for `ssize_t` and dropping the first S works well enough to get auto-completion and highlighting of this symbol.
Yeah, its rather more useful than ssize_t. Strange, if the tags were generated on a gnu machine then size_t is two lines away from ssize_t although posix puts ssize_t in unistd.h, don't ya just luv standards.
Cheers Lex
On 09/14/2011 05:11 PM, Lex Trotman wrote:
On 15 September 2011 00:33, Matthew Brushmbrush@codebrainz.ca wrote:
Hi,
I don't know who generates the c99.tags, but it would be cool if the next release of Geany had the `size_t` symbol in its default tags. I can't get Geany to parse my GNU headers using create_c_tags.sh script (or otherwise), but even just copying the line for `ssize_t` and dropping the first S works well enough to get auto-completion and highlighting of this symbol.
Yeah, its rather more useful than ssize_t. Strange, if the tags were generated on a gnu machine then size_t is two lines away from ssize_t although posix puts ssize_t in unistd.h, don't ya just luv standards.
What I'd like to know is where is size_t defined? According to what I've read, it's supposed to be in stddef.h but I can't find it anywhere in GNU libc downloaded the other day.
Cheers, Matthew Brush
Am 15.09.2011 02:39, schrieb Matthew Brush:
What I'd like to know is where is size_t defined? According to what I've read, it's supposed to be in stddef.h but I can't find it anywhere in GNU libc downloaded the other day.
Should be (also) in string.h, since that's what strlen() returns.
Best regards.
On 15 September 2011 18:50, Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
Am 15.09.2011 02:39, schrieb Matthew Brush:
What I'd like to know is where is size_t defined? According to what I've read, it's supposed to be in stddef.h but I can't find it anywhere in GNU libc downloaded the other day.
Should be (also) in string.h, since that's what strlen() returns.
Hey Thomas,
On my system string.h includes stddef.h with a comment that it is to get the definitions of size_t and NULL. So it isn't repeated.
Cheers Lex
Best regards. _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Thu, 15 Sep 2011 19:01:55 +1000, Lex wrote:
On 15 September 2011 18:50, Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
Am 15.09.2011 02:39, schrieb Matthew Brush:
What I'd like to know is where is size_t defined? According to what I've read, it's supposed to be in stddef.h but I can't find it anywhere in GNU libc downloaded the other day.
Should be (also) in string.h, since that's what strlen() returns.
Hey Thomas,
On my system string.h includes stddef.h with a comment that it is to get the definitions of size_t and NULL. So it isn't repeated.
But stddef.h defines the type only if __need_size_t is defined. As I previously created the c99.tags, I tried to find out what's going on but it just turns out weird, read I think I don't understand all of what is happening with this stuff. I have a stddef.h in /usr/include/linux but this is mostly empty, it really only defines NULL. Then I have a /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6/include/stddef.h which actually has a definition of size_t as:
#define __SIZE_TYPE__ long unsigned int ... typedef __SIZE_TYPE__ size_t;
But this definition is surrounded by many ifdefs and I guess since Geany does -undef in the preprocessing of the tag generation, some of those ifdef's fails and so the definition of size_t is missing.
I personally don't feel like fiddling with this weird stuff and would prefer a rather pragmatically solution like: a) manually add the size_t definition with some ANSI C default or so
b) don't generate c99.tags automatically at all and rather use the current one and maybe strip unnecessary stuff out. Most of the contents should be rather static as the standard doesn't change that much :)
c) someone else maintains that file :D
Regards, Enr - feeling more and more scared by C - ico
2011/9/15 Enrico Tröger enrico.troeger@uvena.de:
On Thu, 15 Sep 2011 19:01:55 +1000, Lex wrote:
On 15 September 2011 18:50, Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
Am 15.09.2011 02:39, schrieb Matthew Brush:
What I'd like to know is where is size_t defined? According to what I've read, it's supposed to be in stddef.h but I can't find it anywhere in GNU libc downloaded the other day.
Should be (also) in string.h, since that's what strlen() returns.
Hey Thomas,
On my system string.h includes stddef.h with a comment that it is to get the definitions of size_t and NULL. So it isn't repeated.
But stddef.h defines the type only if __need_size_t is defined.
I suspect that this is so most of stddef.h can be used for cross compiles, and only a few peculiar things like size_t need to be defined by the cross compile headers.
[...]
I personally don't feel like fiddling with this weird stuff and would prefer a rather pragmatically solution like: a) manually add the size_t definition with some ANSI C default or so
Thats the pragmatic short term answer, so long as it is known for highlighting purposes.
b) don't generate c99.tags automatically at all and rather use the current one and maybe strip unnecessary stuff out. Most of the contents should be rather static as the standard doesn't change that much :)
Yes for C, but C++ also needs size_t defined, and its moving towards C++11 so things are likely to be changing.
c) someone else maintains that file :D
Regards, Enr - feeling more and more scared by C - ico
Time to learn Lisp, Haskell, ML, etc?? :)
Cheers Lex
On Thu, 15 Sep 2011 19:52:38 +1000, Lex wrote:
2011/9/15 Enrico Tröger enrico.troeger@uvena.de:
On Thu, 15 Sep 2011 19:01:55 +1000, Lex wrote:
On 15 September 2011 18:50, Thomas Martitz thomas.martitz@student.htw-berlin.de wrote:
Am 15.09.2011 02:39, schrieb Matthew Brush:
What I'd like to know is where is size_t defined? According to what I've read, it's supposed to be in stddef.h but I can't find it anywhere in GNU libc downloaded the other day.
Should be (also) in string.h, since that's what strlen() returns.
Hey Thomas,
On my system string.h includes stddef.h with a comment that it is to get the definitions of size_t and NULL. So it isn't repeated.
But stddef.h defines the type only if __need_size_t is defined.
I suspect that this is so most of stddef.h can be used for cross compiles, and only a few peculiar things like size_t need to be defined by the cross compile headers.
[...]
I personally don't feel like fiddling with this weird stuff and would prefer a rather pragmatically solution like: a) manually add the size_t definition with some ANSI C default or so
Thats the pragmatic short term answer, so long as it is known for highlighting purposes.
b) don't generate c99.tags automatically at all and rather use the current one and maybe strip unnecessary stuff out. Most of the contents should be rather static as the standard doesn't change that much :)
Yes for C, but C++ also needs size_t defined, and its moving towards C++11 so things are likely to be changing.
Ah, yeah. I completely ignored C++ again. This is even more scary than C :).
c) someone else maintains that file :D
Regards, Enr - feeling more and more scared by C - ico
Time to learn Lisp, Haskell, ML, etc?? :)
Nah, just continuing writing Python :).
Regards, Enrico
[...]
Yes for C, but C++ also needs size_t defined, and its moving towards C++11 so things are likely to be changing.
Ah, yeah. I completely ignored C++ again. This is even more scary than C :).
Relax, now I check all it does is move the C definition into the namespace std. It is *required* to be the same.
c) someone else maintains that file :D
Regards, Enr - feeling more and more scared by C - ico
Time to learn Lisp, Haskell, ML, etc?? :)
Nah, just continuing writing Python :).
So when Geanypy is finished you can add lots of extra features to Geany :)
Cheers Lex