[Swift-devel] camelCase issues
Michael Wilde
wilde at mcs.anl.gov
Thu Mar 1 11:14:24 CST 2012
I got this from a user who was trying the ParameterSweep example:
----- Forwarded Message -----
To run on my MacBook, I had to change @toInt to @toint in you .swift file.
-----
I wrote the code using toInt because I tested on trunk, and wanted to avoid the deprecation message. But I see now that I should have coded to 0.93 standards.
So 2 questions:
- are all built-in functions now accepted in a case-insensitive manner, or just specific ones, in specific cases (like toint and toInt)?
- can we remove the case-related deprecation messages from trunk until we sort out where we are heading on this issue? (In the last thread Mihael suggested we decide for 0.94, which I think is good to do).
Mike
More information about the Swift-devel
mailing list