Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8222001
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 7, 20262026-06-07T14:07:33+00:00 2026-06-07T14:07:33+00:00

%{ #ifdef abc . . . // C declarations . %} . . //

  • 0
%{
#ifdef abc
.
.
. // C declarations
.
%}
.
. //  Yacc Declaration
.
%%
.
. //expected inputs and corresponding actins
.
%%

#endif

Although this code compiles for me even then I strongly feel #ifdef abc is not placed correctly. Is this type of code valid for Yacc.

I have very little experience in YACC.

Thanks

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-07T14:07:34+00:00Added an answer on June 7, 2026 at 2:07 pm

    The code between %{ and %} is put verbatim at the top of the generated C source file, while the code after the rules is also put verbatim but at the end of the generated file.

    So the answer to your question is: Yes, it’s correct in both Yacc and the generated source. However, from a readability point of view, the Yacc-code might be considered dubious.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

This program in C runs and compiles well : #ifdef HAVE_CONFIG_H #include <config.h> #endif
Can someone please explain what #ifdef..#else..#endif does in this piece of code? It's from
Take this code for example: #ifdef THIS_IS_NOT_DEFINED //lots of code here... #endif Say that
I added this in my code: #ifdef DEBUG_MODE printf(i=%d\n,i); fflush(stdout); #endif and my question
#ifdef __cplusplus // C++ code #else // C code #endif The structure is this.
hope someone can answer this. Here is some sample code. namespace std { #ifdef
So I can write code like this: #ifdef [whatever] // do stuff that will
**unmanaged class** this is the unmanaged class declaration #ifdef EXPORT_CLASS #define DLL_EXPORT __declspec(dllexport) #else
Something strange happens. I have in my code in a local function #ifdef abc
#ifdef _cplusplus #include headerfile.h #endif I understand the concept behind this, though I don't

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.