[Swift-devel] Naming convention discussion [VOTE]

[Justin M Wozniak]

I tried to use underscores in Swift/T because I thought it promotes 
memorable function groups, (file_*, string_*, blob_*), and also appeals 
to the C and Fortran users we want to work with. I like using 
category_verb_modifier(), which is in a lot of the Swift/T internal 
code.  But I am fine with camelCase too and look forward to contributing 
to the design document.

I think we can keep the old names for compatibility.

On 01/13/2015 12:20 PM, Tim Armstrong wrote:
> I vote for camel case, based on the Swift/K precedent.
>
> Side issue: in cases where the function follows the old naming scheme, 
> do we change nothing, or switch to the new naming scheme while keeping 
> the old one around for compatibility?
>
> - Tim
>
> On Mon, Jan 12, 2015 at 10:25 PM, Mihael Hategan <hategan at mcs.anl.gov 
> <mailto:hategan at mcs.anl.gov>> wrote:
>
>
>     Allright, unless anybody else has anything to say, let's do an
>     informal
>     vote and see what happens.
>
>     We're voting on whether the naming convention for functions should be
>     camel case or underscores. This applies to future names when
>     otherwise a
>     choice would exist and does not preclude exceptions when there is
>     a good
>     reason to have them.
>
>     This should also apply to the convention we use for future
>     documentation.
>
>     Mihael
>
>
>     _______________________________________________
>     Swift-devel mailing list
>     Swift-devel at ci.uchicago.edu <mailto:Swift-devel at ci.uchicago.edu>
>     https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
>
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel


-- 
Justin M Wozniak

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20150113/61c99b3b/attachment.html>