Thread (1 message) 1 message, 1 author, 2005-03-25

Re: pm_message_t becoming struct

From: Alan Stern <hidden>
Date: 2005-03-25 15:51:08

Possibly related (same subject, not in this thread)

On Fri, 25 Mar 2005, Pavel Machek wrote:
quoted
Are you willing to go halfway?  If we do something more like this:

	typedef struct {
		struct pm_message *m;
	} pm_message_t;

then the code can pass pm_message_t's around with full type-checking and
still retain the benefit of sending a pointer rather than a structure.

Yes, it looks stupid.  But it's a reasonable compromise that won't
I'm afraid it really looks stupid. [It actually has benefit that we
_could_ go over tree in future and change pm_message_t into struct
pm_message *.]

OTOH we would probably be stuck with this stupid-looking-thing
forever, and I'd really prefer to avoid that.
Understandably.  But looking stupid in public is not as bad as bickering 
among ourselves and not getting anything done.  Especially if it smooths 
the path toward making future improvements.

Alan Stern

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help