| View previous topic :: View next topic |
| Author |
Message |
Ron Sawyer Guest
|
Posted: Fri Jun 09, 2006 5:01 am Post subject: __WFILE__ and __LINE__ |
|
|
Is there an equivelent to Visual Studio's __WFILE__ and __LINE__ macro's in
Borland? |
|
| Back to top |
|
 |
Ed Mulroy Guest
|
Posted: Fri Jun 09, 2006 8:10 am Post subject: Re: __WFILE__ and __LINE__ |
|
|
I know about __FILE__ and __LINE__ as they are C and C++ standard items and
are provided by the Borland C/C++ compilers. I have not heard of __WFILE__
but that doesn't mean it isn't available.
.. Ed
| Quote: | Ron Sawyer wrote in message
news:4488ba43$1 (AT) newsgroups (DOT) borland.com...
Is there an equivelent to Visual Studio's __WFILE__ and
__LINE__ macro's in Borland? |
|
|
| Back to top |
|
 |
Ron Sawyer Guest
|
Posted: Fri Jun 09, 2006 6:06 pm Post subject: Re: __WFILE__ and __LINE__ |
|
|
__FILE__ seems to be close enough. I'm not sure what the differences
are, but it works well enough to allow me to move forward.
Thanks
"Ed Mulroy" <dont_email_me (AT) bitbuc (DOT) ket> wrote:
| Quote: | I know about __FILE__ and __LINE__ as they are C and C++ standard items and
are provided by the Borland C/C++ compilers. I have not heard of __WFILE__
but that doesn't mean it isn't available.
. Ed |
|
|
| Back to top |
|
 |
Ron Sawyer Guest
|
Posted: Sat Jun 10, 2006 3:07 am Post subject: Re: __WFILE__ and __LINE__ |
|
|
It turns out that __WFILE__ returns a wchar_t* rather than a char *. That
is the only difference. I had to cast it and it seemed to work fine. (I
have other things to fix before I can test.)
"Ed Mulroy" <dont_email_me (AT) bitbuc (DOT) ket> wrote in message
news:4488e7b3 (AT) newsgroups (DOT) borland.com...
| Quote: | I know about __FILE__ and __LINE__ as they are C and C++ standard items
and
are provided by the Borland C/C++ compilers. I have not heard of
__WFILE__
but that doesn't mean it isn't available.
. Ed |
|
|
| Back to top |
|
 |
Alex Bakaev [TeamB] Guest
|
Posted: Sat Jun 10, 2006 3:25 am Post subject: Re: __WFILE__ and __LINE__ |
|
|
Ron Sawyer wrote:
| Quote: | It turns out that __WFILE__ returns a wchar_t* rather than a char *. That
is the only difference. I had to cast it and it seemed to work fine. (I
have other things to fix before I can test.)
|
You can't just cast between char * and wchar_t.
..a |
|
| Back to top |
|
 |
|