From: Alessio Sangalli <alesan@manoweb.com>
To: "linux-fbdev-devel@lists.sourceforge.net"
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: open and close semanthics
Date: Thu, 27 Aug 2009 15:52:37 -0700 [thread overview]
Message-ID: <4A970E35.4000903@manoweb.com> (raw)
In-Reply-To: <4A946A59.20307@manoweb.com>
No indications on this request?
thank you
Alessio
Alessio Sangalli wrote:
> Hi, can somebody give me an authoritative answer:
> what is the semanthics associated to the "open" and "release" (close) calls?
>
> More specifically, "open" and "release" can/must/must not change any
> setting (resolution etc)?
>
> Should those functions keep a "counter" of how many programs opened it?
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
next prev parent reply other threads:[~2009-08-27 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 22:48 open and close semanthics Alessio Sangalli
2009-08-27 22:52 ` Alessio Sangalli [this message]
2009-08-28 9:43 ` Florian Tobias Schandinat
2009-08-28 12:22 ` Ondrej Zajicek
2009-08-28 16:08 ` Alessio Sangalli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A970E35.4000903@manoweb.com \
--to=alesan@manoweb.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.