Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

FIOC mixed caps

Name: Anonymous 2009-12-25 0:49

FIOC stdlib should stick to underscore_naming, instead of this disgusting mixedCaps shit. People shouldn't be able to commit to stdlib unless all methods are underscored_named. I refuse to use the unittest module until the test methods are underscore_named. Real languages shouldn't allow disgusting stuff like this to occur. That is all.

Name: Anonymous 2009-12-25 0:54

superior-naming-convention-p

Name: Anonymous 2009-12-25 0:54

Only faggots and jews use underscores.  Request denied.

Name: Anonymous 2009-12-25 1:05

I don't know FIOC well, but is there any place in the syntax where multiple non-keyword words can be used with no intervening keywords or operators?  If not, just allow symbols to contain whitespace, collapsing each whitespace run into a single space character.  Problem solved.

Name: Anonymous 2009-12-25 1:08

>>2
t

Best naming convention is to allow spaces in names though.

Name: Anonymous 2009-12-25 1:08

>>2
Abelson and Sussman are rolling in their graves.

Name: Xarn 2009-12-25 1:28

Xarn approves of this thread.

Name: Anonymous 2009-12-25 1:42

>>4,5
Not you again

>>6
;_;

Name: Anonymous 2009-12-25 1:53

>>8
Yes, me again. >>4 isn't me, though.

Name: Anonymous 2009-12-25 6:25

IHBT

Name: Anonymous 2009-12-25 11:15

>>6
I would ask you not to speak about the living in that manner.

Name: Anonymous 2009-12-25 12:13

>>1
Real languages prevent using camelCase? How? By disallowing capital letters? No language that I'm aware of disallows capital letters.

Name: Anonymous 2009-12-25 12:34

>>12
This may be added to the implementation of Trollgol I will start implementing it in the new year, promise ;)

Name: Anonymous 2009-12-26 7:12

>>1
import custom_unittest[code]

[m]custom_unittest.py[/m]
[code]import unittest
class test_case(unittest.TestCase):
    def set_up(*args):
        setUp(args)


Etc.

Name: Anonymous 2009-12-26 12:31

>>13
Implement my HASKAL

Name: Anonymous 2009-12-26 12:49

quick count_the_under scores in_this piece_of text

Name: Anonymous 2009-12-26 13:58

>>16
4.

Name: Anonymous 2009-12-26 14:00

Really both should be allwoed and a compiler/intepreter should be celver enough to go foo_bar_fuck_cheese is equivalent to fooBarFuckCheese or whatever based on various rules.. and then the caller of the function can use which ever he preferes

Name: Anonymous 2009-12-26 14:10

>>18
Wow. That sounds fucked up.

Trollgol material almost.

Name: Anonymous 2009-12-26 14:22

>>19
Trollgol
Incorporate it into the standard.

Also, deliberately add functions which use both naming conventions into the stdlib, so that there would be some collisions; later on add some sort of underline_named<<functionName>> syntax to specify which one you want to call.

Name: Anonymous 2009-12-26 17:01

The most elegant case for mixed capitalization schemes, where one is used for singular forms, and the other for plural forms, occurs in Rails, a great inspiration for Python's most popular web framework, Django.

Name: Anonymous 2009-12-27 1:02

>>1
I refuse to use the unittest module because it's for fucking unit tests.

In all honesty though, whereas my code style is very rigid in any other language, I find that the lack of consistency in FIOC+Django naming conventions is amplified 10-fold in my projects that use it. The resulting code looks like shit, and I hate it.

Name: Anonymous 2009-12-27 7:24

>>13
Damn, I wanted to do that, but had no time so far.

Name: Anonymous 2009-12-27 12:54

>>23
We should both do it, and then compete on /prog/ for users. This time next year we will start a steering committee and incorporate features from each other in a manner befitting of C++.

Name: ​​​​​​​​​​ 2010-09-07 18:46

Name: ​​​​​​​​​​ 2010-10-26 6:00

Name: Anonymous 2010-11-15 16:37

Name: Anonymous 2011-02-03 8:33

Name: Anonymous 2011-02-04 18:21


Don't change these.
Name: Email:
Entire Thread Thread List