01-08-2015
Quote:
Originally Posted by
shamrock
@achenle:
Embedded spaces in preprocessor #defines are always a cause of confusion and error...however the issue with the OP is one of supplying a compiler statement to a preprocessor...
That was a simple off-the-cuff example to demonstrate the semantic and syntax differences between "typedef" and "#define".
The fact that whitespace is treated completely differently in typedef and #define code is another reason to never replace typedef's with #define's.
If you read the link the OP provided, you'd see his problem is compiling. He's not feeding code to a preprocessor except as part of compiling. And I'd love to see a preprocessor so lame it couldn't handle typedef's, which are part of the language spec.
"Find out what's broken and fix it" is much better than "change this and hope it works".
This User Gave Thanks to achenle For This Post:
9 More Discussions You Might Find Interesting
1. Solaris
I am using gcc3.3.5 on solaris2.7. Its a 64 bit compilation
I am compiling a file 'plugin.cpp'. It includes mach.h and the complation gives the following error.
-----------------------------------------------------------------
mach.h error: conflicting
types for `typedef vx_u32_t... (0 Replies)
Discussion started by: amitc
0 Replies
2. Programming
I want to declare
char ch as ch_9 with the help of the typedef statement.
Thanks (1 Reply)
Discussion started by: krishna_sicsr
1 Replies
3. Programming
I've google a bit about this and couldn't find an answer. Actually I read that it can't be done.
Basically I've defined the following structure and typedef it as follows.
stuct Name {
};
typdef struct Name Name.
and right after it, defined some API that use it.
void blabla(Name*... (6 Replies)
Discussion started by: emitrax
6 Replies
4. UNIX for Dummies Questions & Answers
Preparing to get my first home PC via custom-build shop. It will have three hard disk drives...one to be used only for trial of various OSs. Was hoping to test out Haiku, but according to 'supported architectures' table at Wikipedia ("Comparison of open source operating systems"), it only works on... (3 Replies)
Discussion started by: Varsel
3 Replies
5. Programming
Hi!
This is part of my my code :
typedef struct{
int x;
char na;
char sur;
} Stu;
typedef struct{
Stu *arr;
int size;
int sort;
} Stus;
I want to ask how can i free() the matrix arr.
I tried free(arr), free(Stus.arr) and i get errors with gcc.
My problem, in... (3 Replies)
Discussion started by: giampoul
3 Replies
6. Shell Programming and Scripting
Hi ,
I am planning for the interview . I am having one question here , I worked on unix and shellscripting for 2 years
Done-
Ø Coding and testing of Server Monitoring ShellScripts
Ø Deployment on UNIX production environment
I have written so many shellscripts for monitoring... (5 Replies)
Discussion started by: aish11
5 Replies
7. Programming
I am getting confused compiling a program that gives me the following error
../../../tomso/algeb/vector.hpp:19:9: error: ‘Vector' does not name a type
typedef Vector<float> Vecflt; (1 Reply)
Discussion started by: kristinu
1 Replies
8. Programming
Sorry for the “word salad” subject, but I wanted to cast a wide net for help.
I've created an IP (Internet Protocol) server which serves HTTP, SMTP, and FTP requests.
As you probably know, they all require creating a socket, listening on it, accepting connections, and then having a short... (3 Replies)
Discussion started by: John S.
3 Replies
9. Programming
Working on some source I've found some strange declaration in included header file.
I am looking for someone's help to understand me that syntax's, as it is fine (it is compiled without any complain,) but for me it seems out of any sense!
Acctually, it warning by CC compiler: " Warning: Implicit... (1 Reply)
Discussion started by: alex_5161
1 Replies
LEARN ABOUT DEBIAN
omnicpp
OMNICPP(1) General Commands Manual OMNICPP(1)
NAME
omnicpp - OmniORB cpp preprocessor for IDL compiler
SYNOPSIS
omnicpp [options]
DESCRIPTION
This manual page documents briefly the omnicpp command.
omniidl is omniORBs IDL compiler and uses omnicpp as it's C preprocessor. omnicpp is really just the GNU C preprocessor under a different
name. Normally you should not need to invoke this directly but should use omniidl instead.
OPTIONS
As this is just the GNU C preprocessor cpp you can see that program for the full options. Normally you should not be invoking this
directly but should use omniidl instead. The options listed here should really be given to omniidl, but they are passed straight to
omnicpp.
-D name
Define name for the preprocessor.
-U name
Undefine name for the preprocessor.
-I dir Include dir in the preprocessor search path. Note that the current directory is not on the include search path by default. Use -I.
for that.
SEE ALSO
omniidl(1).
The programs are documented fully by the HTML documentation in the omniorb4-doc package.
AUTHOR
omnicpp was written by Duncan Grisby <duncan@grisby.org>
This manual page was written by Floris Bruynooghe <floris.bruynooghe@gmail.com>, for the Debian project (but may be used by others).
30 Apr 2007 OMNICPP(1)