Mundane C tricks ...

[revelator]

Mostly i would agree but in the case i had it was something that translated to {const char,const char, const char, huge cast to null terminate this array of strings} in turn it would translate to {const char, const char, const char, 0} so i was wondering why not just use the null string '\0' instead of the huge cast since its an array of strings wouldnt that be more correct ? or am i missing something. Ofc i would newer use the null string for a non char pointer that would be silly.

[taniwha]

95% of the time, I couldn't care less what a variable's type is, which is a large part of the reason I despise Hungarian notation (*twitch*, *twitch*, *bleh*, I feel dirty just saying it ).

I don't know, maybe it's just something that comes with programming for 30 years (20 of which in C or C++), in a variety of fields (2d and 3d graphics, 2d and 3d physics, compilers, networking). After a while, beyond telling the compiler how the data is to be handled (eg, int vs float), type becomes meaningless. I don't think in terms of pointers and structs, I think in terms of "I've got this thing here, with these named features". Might be part of why I always get my . and -> mixed up (another part is python and qfcc (I didn't bother with ->, though I might add it as an option)).

Having to think about type ('\0' for char, 0 for int, 0.0 for float, NULL for pointers) would only get in the way (ouch, my head hurt just filling in the examples), just like having to get . and -> right does (and I read somewhere that either Kernighan or Ritchie (don't remember) regrets ->). I am very grateful that C always treats 0 of any type as false and non-zero of any type as true, and that just a bare 0 works for any non-aggregate type. The compiler gets out of the way and lets the programmer concentrate on the problem the code is to solve rather than futzing with trivial details.

Actually, I have a good argument against using '\0': it can be visually confused with '0', or worse, '10' (sure, gcc will warn about that one, but...). I think I read that somewhere in some style guide. Oh, and a second one: what is '\013'?

[Baker]

[revelator]

Heh true it can be a bit confusing atleast 0 is allways equal to none and doing things with an escaped string type might be rather hard to compute. Im not 100% on it but i think \013 would translate to 0.13 but is it a positive value ??? hmm probably though im not sure how to do a negative value with a string type like that unless char > '\stringvalue' or does it accept a - ? hmm. In that case i would probably prefer just using plain 0.13

I guess my style comes from not having learned neither C nor C++ professionally its just things i picked up over the years and theres a lot of holes still to be filled but mostly i can get things working though if i had to do it for a living i would probably starve to death im not exatly fast but i do the best with what i got. Only language i actually invested heavily in was basic back when the spectrum zx80 and amigas where the thing today i can remember two things from all that (jack and shit) i guess when you dont use use a skill everyday it tends to go blank hehe.

[revelator]

Totally agree baker if someone can use my ideas who am i to argue when i got so much in return i feel obliged to atleast leave a footprint of what i learned from all of it and if it benefits others all the better.

[szo]

[taniwha]

[revelator]

hehe ok no hungarian notations noted.
is'nt hex octal by nature ? though a hex number as a string terminator would probably make my head explode be gentle on the old hobby programmer here hehe.

[taniwha]

[Baker]

[taniwha]

Yeah, well, strong claims need strong support, to paraphrase the quote about proof.

However, I'm not so much about convincing someone I'm right as I am about getting the person to understand my claims and why I make them, giving them an opportunity to point out where I'm wrong (if I am, which is not guaranteed). Unfortunately, not many people see it that way .

[Baker]

I've started getting rather heavy into linked-lists. And to my surprise there, I've discovered that with parent/peer/child structure there are multiple ways you can need to traverse them.

I'm gunning for the oddball ability to save every possible user interface item and entities into the same file. With the ability to have multiple 3D viewports and an interface editor that can work with the data and dragable elements.

I'm also doing something possibly unwise with the display, penetrating through levels of parents/child to be able to calculate real hardware X, Y for "virtual points" in a viewport and setting up windows in such a way that the screen may have the window centered.

At the moment: I am frustrated.

/But isn't that just part of working on complex stuff in programming. If I gave up easily, hahaha ... you can't code stuff at all ... and you don't have this issue with great frequency then one must not be doing anything fun ...

[taniwha]

[Baker]

[Baker]