Re: Interface naming standards?
| From: | Stefano F. Rausch | Date: | Thu, 01 Jun 2006 18:36:18 +0000 |
| Subject: | Re: Interface naming standards? | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-42731@lists.php.net to get a copy of this message | ||
Hi,
Is it really necessary to add the tagging word "Interface"?
Take for example:
Spreadsheet_Writer ---> this is the interface
Spreadsheet_Writer_Excel ---> implements the interface ;)
Spreadsheet_Writer_OpenOffice
Same would apply to abstract classes being extended. Positive side-effect: lesser to type and no naming "pollution".
Why make things difficult?
A package should always have API docs in place and (hopefully) a sort of manual, where "everything" is explained.
Your feelings?
-- Stefano
Daniel Convissor wrote:
Heya: On Thu, Jun 01, 2006 at 09:38:20AM -0700, Joe Stump wrote:I'm currently working on a package that I plan on having an interface defined in.Funny you should mention this. I was thinking about a new pacakge with interfaces too, along these lines: Spreadsheet_Writer_Interface Spreadsheet_Writer_Excel Spreadsheet_Writer_OpenOffice Spreadsheet_Writer_Interface_Workbook Spreadsheet_Writer_Excel_Workbook Spreadsheet_Writer_OpenOffice_Workbook Etc... --Dan