Raoul Gough <RaoulGough@[...].uk>  writes:

>  David Abrahams <dave@[...].com> writes:
> 
> > Raoul Gough <RaoulGough@[...].uk> writes:
> >
> >> David Abrahams <dave@[...].com> writes:
>  [snip]
> >>> Well, my point was that I thought it was more useful and safer to
> >>> encode the acquisition method in the type.
> >>>
> >>> Could be wrong, though.
> >>
> >> It also seems safer to me, since the base class constructor is
> >> protected. On the other hand, maybe removing the plain pointer
> >> overload for handle<>::handle() would be just as good?
> >
> > Can't do that without providing a new_reference(...) wrapper.
> 
>  That's more or less what I was thinking, too. Is this a bad idea?
> 
> >
> >> -- 
> >> Raoul Gough.
> >> (setq dabbrev-case-fold-search nil)
> >
> > Interesting sig.  Do you want me to `C-x C-e' it?
> 
>  Well, sure. Unless you think it's a Trojan horse :-) I was trying to
>  think of a handy Emacs feature from my .emacs to publicize, but
>  dabbrev was all I came up with. Maybe I should move on to

What's handy about that?  The emacs help for it doesn't really tell
me why I'd want to use it.

>  (add-to-list 'auto-mode-alist '("\\.py\\'" . python-mode))

That one *is* a trojan. I'm not sure python-mode is standard in many
emacs installations. ;-)

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com


_______________________________________________
C++-sig mailing list
C++-sig@[...].org
http://mail.python.org/mailman/listinfo/c++-sig