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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T08:39:58+00:00 2026-05-18T08:39:58+00:00

I’m working with some legacy code that makes extensive use of this kind of

  • 0

I’m working with some legacy code that makes extensive use of this kind of thing:

// Allocate a look-up-table of pointers.
long *pointerLUT = (long *) malloc(sizeof(long) * numPointers);

...


// Populate the array with pointers.
for (int i=0; i<numPointers; i++) {
     pointerLUT[i] = (long) NewFoo();
}

...


// Access the LUT.
Foo *foo = (Foo *) pointerLUT[anIndex];

As you can see, this allocates an array of longs, with the idea of using them generic pointer storage.

Q1. Is this approach safe?

Q2. Style-wise, how could it be improved? Does it need to be? (The typecasting rattles the fear-monkey in me.)

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-05-18T08:39:58+00:00Added an answer on May 18, 2026 at 8:39 am

    EDIT: I missed where he said “generic pointer storage” in the question. This answer is not correct for that case.

    If you are working with pointers to Foo then that’s what your code should say.

    // Allocate a look-up-table of pointers.
    Foo **pointerLUT = (Foo **) malloc(sizeof(Foo *) * numPointers);
    
    // Populate the array with pointers.
    for (int i=0; i<numPointers; i++) {
         pointerLUT[i] = NewFoo(); // NewFoo() should return (Foo *)
    }
    
    // Access the LUT.
    Foo *foo = pointerLUT[anIndex];
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I need to clean up various Word 'smart' characters in user input, including but
i want to parse a xhtml file and display in UITableView. what is the
public static bool CheckLogin(string Username, string Password, bool AutoLogin) { bool LoginSuccessful; // Trim

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.