You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Ryan Bloom <rb...@raleigh.ibm.com> on 1999/10/12 13:19:29 UTC

Re: cvs commit: apache-2.0/src/lib/apr/threadproc/win32 proc.c


Why wuld ap_set_procdata be obsolete?  We haven't used it anywhere yet,
but it's purpose is still valid.  Just like all the other set_foodata
functions, it's purpose is to allow programmers to easily add their own
data to APR types.  This was a requested ability, and it should be left in
the APR types.

Ryan

>   Log:
>   I think this is an obsolete function...
>   
>   Revision  Changes    Path
>   1.3       +1 -1      apache-2.0/src/lib/apr/aprlib.def
>   
>   Index: aprlib.def
>   ===================================================================
>   RCS file: /home/cvs/apache-2.0/src/lib/apr/aprlib.def,v
>   retrieving revision 1.2
>   retrieving revision 1.3
>   diff -u -r1.2 -r1.3
>   --- aprlib.def	1999/10/11 15:47:46	1.2
>   +++ aprlib.def	1999/10/12 01:09:54	1.3
>   @@ -113,7 +113,7 @@
>    	ap_get_threadkeydata    @105
>    	ap_set_threadkeydata    @106
>    	ap_get_procdata    @107
>   -	ap_set_procdata    @108
>   +;	ap_set_procdata    @108
>    	ap_get_os_proc   @109
>    	ap_get_os_thread   @110
>    	ap_get_os_threadkey   @111

_______________________________________________________________________
Ryan Bloom		rbb@raleigh.ibm.com
4205 S Miami Blvd	
RTP, NC 27709		It's a beautiful sight to see good dancers 
			doing simple steps.  It's a painful sight to
			see beginners doing complicated patterns.	


Re: cvs commit: apache-2.0/src/lib/apr/threadproc/win32 proc.c

Posted by Bill Stoddard <st...@raleigh.ibm.com>.
> Why wuld ap_set_procdata be obsolete?  We haven't used it anywhere yet,
> but it's purpose is still valid.  Just like all the other set_foodata
> functions, it's purpose is to allow programmers to easily add their own
> data to APR types.  This was a requested ability, and it should be left in
> the APR types.
Ahh, okay.  I didn't see it in the unix/proc.c file and made an assumption.
I see now it is in unix/procsup.c rather than in proc.c.