<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix"><br>
      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. <br>
      <br>
      I think we can keep the old names for compatibility.<br>
      <br>
      On 01/13/2015 12:20 PM, Tim Armstrong wrote:<br>
    </div>
    <blockquote
cite="mid:CAC0jiV5gk7vZ_Qy200c8d=kHym9DtV6m_c5m_HYcRwtsgQH6Sw@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div dir="ltr">
        <div>I vote for camel case, based on the Swift/K precedent.  <br>
          <br>
          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?<br>
          <br>
        </div>
        - Tim<br>
        <div>
          <div>
            <div class="gmail_extra"><br>
              <div class="gmail_quote">On Mon, Jan 12, 2015 at 10:25 PM,
                Mihael Hategan <span dir="ltr"><<a
                    moz-do-not-send="true"
                    href="mailto:hategan@mcs.anl.gov" target="_blank">hategan@mcs.anl.gov</a>></span>
                wrote:<br>
                <blockquote class="gmail_quote" style="margin:0px 0px
                  0px 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex"><br>
                  Allright, unless anybody else has anything to say,
                  let's do an informal<br>
                  vote and see what happens.<br>
                  <br>
                  We're voting on whether the naming convention for
                  functions should be<br>
                  camel case or underscores. This applies to future
                  names when otherwise a<br>
                  choice would exist and does not preclude exceptions
                  when there is a good<br>
                  reason to have them.<br>
                  <br>
                  This should also apply to the convention we use for
                  future<br>
                  documentation.<br>
                  <br>
                  Mihael<br>
                  <br>
                  <br>
                  _______________________________________________<br>
                  Swift-devel mailing list<br>
                  <a moz-do-not-send="true"
                    href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a><br>
                  <a moz-do-not-send="true"
href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel"
                    target="_blank">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a><br>
                </blockquote>
              </div>
              <br>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Swift-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a>
<a class="moz-txt-link-freetext" href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Justin M Wozniak</pre>
  </body>
</html>