guile-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: To gh_ or not to gh_?


From: John Fitzgerald
Subject: RE: To gh_ or not to gh_?
Date: Fri, 11 May 2001 16:14:54 +1200

Or elevating the public scm_ functions into gh_ ?

> -----Original Message-----
> From: Evan Prodromou [SMTP:address@hidden
> Sent: May 11, 2001 08:14
> To:   John Fitzgerald
> Subject:      Re: To gh_ or not to gh_?
> 
> >>>>> "RB" == Rob Browning <address@hidden> writes:
> 
>     RB> One thing that we've been discussing on guile-devel is, at a
>     RB> minimum, starting to hide all the scm_ functions that are
>     RB> considered "private" by default, either with private headers,
>     RB> or more likely with a #define SCM_INTERNAL or similar.  This
>     RB> would help make it clear which of the scm_ functions are
>     RB> intended for public consumption.
> 
> Another possibility is renaming -- e.g., "scmi_" for "scm internal".
> 
> ~ESP
> 
> -- 
> Evan Prodromou
> address@hidden
> 
> _______________________________________________
> Guile-user mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/guile-user
> 
> 
> 
NOTICE: The information contained in this electronic mail message and any
attachments is confidential to Pavilion Technologies, Inc. or one of its
subsidiaries and may contain proprietary information or be legally
privileged. This message and any attachments are intended only for the
personal and confidential use of the designated recipient(s). If you are not
the intended recipient or an agent responsible for delivering it to the
intended recipient, you are hereby notified that you have recieved this
message in error, and that any review, dissemination, distribution or
copying of this message and any attachments is unauthorized and strictly
prohibited. If you have received this message in error, please notify me
immediately by telephone and electronic mail, and delete this message, any
attachments, and all copies thereof. Thank you very much  





reply via email to

[Prev in Thread] Current Thread [Next in Thread]