shmget vs. shm_open

From: bill pursell (bill.pursell_at_gmail.com)
Date: 11/17/05

  • Next message: Larry I Smith: "Re: shmget vs. shm_open" 
    Date: 17 Nov 2005 13:02:10 -0800

    Can anyone point me to a comparison of using sysVr4 shmget() calls
    versus Posix shm_open()? Is there a reason (other than wanting to
    conform to one standard vs. the other) to choose one over the other?
    If my app is only going to be running on Linux, does it matter which
    style of shared memory I choose to use?

  • Next message: Larry I Smith: "Re: shmget vs. shm_open"

    Relevant Pages

    • Which WiFi standards Galaxy S3?
      ... For PCs and routers you are told which 802.11 standard they conform to. ... For some reason the only information I can find for the S3 says that it does WiFi. ...
      (uk.telecom.mobile)
    • Re: kids and their furniture?
      ... I would always honor and respect any house rules I was ... standards that differed significantly from the range of behaviors ... I think it's pretty close to the legal 'reasonable person' standard. ... too much work to reason one's way through every single ...
      (misc.kids)
    • Re: I dont get how the computer arrives at 2^31
      ... > Standard isn't always as careful with the language it uses. ... something that will make its functionality "equivalent" to fprintf(). ... function that created the va_list value passed to vfprintf(). ... The reason is that, unless ...
      (comp.std.c)
    • Re: How do you imagine future Common Lisp standard ?
      ... Scheme doesn't focus on good macro ... Goodness and Badness must be evaluated in a particular design-space ... It's fortunate that this can be done without change to the standard, ... There's no reason to define the old language away, ...
      (comp.lang.lisp)
    • Re: Understanding # and function variables
      ... That's the reason for my statement that I don't care whether a ... >>change is standard compliant or not. ... >>substantial revision of ANSI Common Lisp and would provide equally ... I will find out about an already existing language that is strictly ...
      (comp.lang.lisp)