On Tue, Aug 19, 2008 at 09:52:55PM +0200, Jehan wrote: >> It's historical, and in my opinion a waste of space. Better to call the >> function 'scr_refresh' than 'mrxvt_scr_refresh'. (The prefixing is only >> needed when we write a library that might be used by other >> applications). > > I think it has at least one advantage, even without being used as > library: when you see a call to a function, you directly when this is > an internal function or an external one.
Ah. I have Vim recognise (and highlight) all my Xlib / glibc functions / constants. So I know right away if a function is internal or not. > I don't think it has any real impact on the final executable, Yep. (Plus too much effort to change). > but it is good for readability. Possibly. Though it's primary purpose is probably a nice case of CPT. GI -- The 10 Commandments of DOS: 1. I am thy DOS, thou shall have no OS before me, unless Bill Gates gets a cut of the profits therefrom.
pgpnab9I5g6K0.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Materm-devel mailing list Materm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/materm-devel mrxvt home page: http://materm.sourceforge.net
