I'm sure julia can adopt any gender identification [] prefers, but I frankly doubt [] cares... In the interests of 'truth in confusers' standards, could we please see fewer 'ok' buttons and more 'Take that, human!' messages with "ohno!" bottons?
Anyway, yes, I've found this a very helpful community, & thanks! On Sat, Oct 17, 2015 at 1:12 PM, Tomas Lycken <[email protected]> wrote: > … julia doesn’t like ‘foo ()’ anymore, she now prefers ‘foo()’ … > > In a recent thread I vowed to start helping with enforcing the Julia > Community Standards <http://julialang.org/community/standards/>, so I > guess it’s now time to walk the walk. In the Standards, we can read > > While “Julia” is a female name in many parts of the world, the programming > language is not a person and does not have a gender. > > In other words, don’t say “she” about the Julia language; say “it”. > > On a related note, I’m not sure I’ve seen your name on the list before, > Forrest - welcome to the community! :) > > // T > > On Saturday, October 17, 2015 at 5:26:39 PM UTC+2, Forrest Curo wrote: > > Thanks, all! >> >> Most of my booboos seem to be due to the fact that julia doesn't like >> 'foo ()' >> anymore, she now prefers 'foo()' which I suppose makes the parsing >> simpler. >> And I now know where to find that pesky tk button code... >> >> On Sat, Oct 17, 2015 at 8:00 AM, Kristoffer Carlsson <[email protected]> >> wrote: >> >>> You can start julia with -depwarn=no to turn off deprecation warnings. >>> >>> On a personal note, I think that the time between type deprecation and >>> the release was possibly a bit short. It feels that whatever package I >>> import now I get pages of deprecation warnings. This is particularly >>> inconvenient in IJulia sessions. >> >> >> >
