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 8776617
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 13, 20262026-06-13T19:06:06+00:00 2026-06-13T19:06:06+00:00

What behaviour is being caused by the ‘const’ in the following code, in particular,

  • 0

What behaviour is being caused by the ‘const’ in the following code, in particular, the cast:

const void *foo()
{
   void *bar = NULL;

   // Assign bar to some address here.

   return (const void *)bar;
}

Is the cast necessary? The compiler gives a warning that the type does not match the return type, unless I perform the cast, but is the resultant behaviour any different?

  • 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-13T19:06:07+00:00Added an answer on June 13, 2026 at 7:06 pm

    The cast is not required and is even useless. C does not require any warning if you don’t cast.

    You can return a char * when a const char * return value is expected.
    This is also true for other types: you can return a T * when a const T * is expected.

    C says that for return statement:

    (C99, 6.8.6.4p3) “If the expression has a type different from the return type of the function in which it appears, the value is converted as if by assignment to an object having the return type of the function.”

    You can assign a char * to a const char * (note that the opposite is not valid).
    C says for pointer assignment:

    (C99, 6.5.16.1p1) “One of the following shall hold: […] both operands are pointers to qualified or unqualified versions of compatible types, and the type pointed to by the left has all the qualifiers of the type pointed to by the right; […]”

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

Sidebar

Related Questions

what behaviour can I expect when I run this code: do while(testA) { //
Possible Duplicate: Behaviour of Sizeof in C Can somebody explain why the following piece
I'm getting strange navigation bar behaviour, for example when I hit back button the
I recently came across a problem with my code that was caused by certain
Being spotted in context of this question this seemingly inconsistent behavior can be reproduced
I have seen behaviour in Perforce that I am unable to explain. I took
The default behaviour in browsers is to select the next form element. I want
I'm testing the behaviour of a Cassandra cluster with different configurations. One of them
I just see strange behaviour in Eclipse . I am developing one android project
I'm seeing inconsistent behaviour when calling setResult() and finish() on some activities that were

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.