Except that then we're back to these silly case-insensitive filesystems. Jim Starkey wrote: > Brian Aker wrote: >> Hi! >> >> What happens though when it is a class that you then decide to expose >> for folks extending the server? Do we rename classes then? >> >> Personally I prefer to keep naming conventions such that if we change >> our minds in the future, we don't have to go around renaming everything. >> > > If you were to adopt the convention of starting class names with capital > letters and using the class name as the file name for the declaration, > virtually all potential conflicts would disappear, at least on Unix and > Linux. That leaves the relatively small subset of system include files > that are common to Posix and Windows, which is manageable; Hint: Don't > name classes "File", "IO", or "String" (OK, I've done two out of these > three). > Upper case class names also makes the code more readable. The downside > is that somebody might think you had ever used Java. >
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
