Thread: concatenate 2 const char * problem

Actually you are mistaken. __FILE__ is a string literal and can be concatenated, as I have done so with __FILE__ and __LINE__ by stringifying __LINE__. __FUNCTION__ aka __func__ is a treated as a variable now in an attempts at standardization and is a string constant and cannot be modified. I am simply trying to take all of this information and representing it as one string, can you help me do this or not? Although __func__ cannot be concatenated onto __FILE__, i merely used it as an example of what I was trying to accomplish.

You cannot change "hello" to "hello world" using strcat:

Code:

strcat( "hello", " world" );

Both are string literals, and it will attempt to modify the first literal--which is undefined behavior. Modifying string literals is not something you should ever try to do, because it is not guaranteed to work, because string literals may be stored in read only memory. You can't modify read only memory. That's why it's called read only.

Do it in two calls to a buffer of your choosing:

Code:

strcat( mybuf, __FILE__ );
strcat( mybuf, __func__ );

Quzah.

Wouldn't something like sprintf(bigBuf, "%s%s", constCharPtr1, constCharPtr2); do what you need?

No, essentially what's going on is this

Code:

main.c
int main()
{
   //call function in external file extern.c
   extern(__FILE__,__LINE__,__func__)
}

extern.c

int extern(const char*file, int line, const char *func)
{
    //print file, line, func
    //print this file's file, line, func
}

The goal is to macro the extern() function call so it only has ONE parameter, not known to the caller for debugging purposes, i.e. extern( char *mssg), but the caller would only need to know extern() to use it. Concatenating __FILE__ and __LINE__ is easy within a macro, but no matter what I try I can't get __func__ to work properly. If i create my own function to concatenate strings, it complains i'm returning a local variable which is a char [], otherwise i must allocate memory for a char * which i guess could work. I'm not sure you guys clearly understand what i'm trying to do, everything is seperate from eachother, everything is modular, but i need to know where a call came from, and where it ended up. This concatenation needs to take place when the original calling functions calls the external code, because this is the first time the __FILE__ __LINE__ and __func__ needs to be grouped together into a single paramter and passed to the external function.

__func__ is not a string literal. It's a "block scoped variable" that supplies the name of the enclosing function.

Originally Posted by C: A Reference Manual, 5th edition, page 51

The C99 identifier __func__ (Section 2.6.1) is similar in purpose to __LINE__, but is actually a block-scope variable, not a macro. It supplies the name of the enclosing function.

Quzah.

Thanks for enlightening me as opposed to helping me, i'll come up with something I guess. Thanks anyways. I mean why is it so difficult to give me a straight answer about grouping all three of __LINE__ __FILE__ __func__ into a single string which is what i've asked a dozen ttimes. I just did it the long, ugly way since nobody felt like helping me out, unfortunately yet again im stuck using a solution i am unhappy with because nobody wants to tell me another way to do it.

Originally Posted by tempster09

Thanks for enlightening me as opposed to helping me, i'll come up with something I guess. Thanks anyways. I mean why is it so difficult to give me a straight answer about grouping all three of __LINE__ __FILE__ __func__ into a single string which is what i've asked a dozen ttimes. I just did it the long, ugly way since nobody felt like helping me out, unfortunately yet again im stuck using a solution i am unhappy with because nobody wants to tell me another way to do it.

Don't be such a baby. We already told you how to do it, two different ways. You can't just concatenate in one lump without doing what we've told you. Read! We've been telling you what you have to do. It's not a macro! It's not a string literal! You cannot modify string literals and have it be portable!

Just because you want something to work some way, doesn't mean it does and will. If you can't understand this, programming isn't for you. Quit now.


Quzah.

It really wouldn't matter if you mentioned that or not. You can't concatenate a string literal and a string without allocating space for the string + literal + nul. You just cant do it, as we've said multiple times. We're not just withholding information from you to be mean. You can't do what you want to do, the way you want to do it.


Quzah.

Originally Posted by tempster09

I would like to avoid the overhead of a function which allocates memory for a string, performs the concatenation, than making me keep track of the memory and cleaning it up. Im used to working with scripting languages, not soo much C

This is not a scripting language. This is C.
C is not like scripting languages. C is made to be a blazing fast, low-level (well, sort of) language. You cannot just do things in C as you can in scripting languages.
Deal with it, or don't use it. The end.