Unique function name. Globally.
-
Someone using that as a function name is certainly no fault of Erlang, but that of a coder who should by up on disciplinary proceedings.
Do what thou wilt shall be the whole of the Law. - Liber AL vel Legis 1:40, Aleister Crowley
Brady Kelly wrote:
Someone using that as a function name is certainly no fault of Erlang, but that of a coder who should be up on disciplinary proceedingshanged by the neck until dead, then hung from the lamppost outside work as a warning to others.
FTFY :)
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
-
'4d568c9e-cb32-4db1-a276-26cb06cc3f6f'(User, SomeVar)
Yep, this is an actual function signature in production code. (Erlang)
I oddly like this. This function is presumably generated and used by some automated code generator and not something a human programmer would have to reference.
-
I oddly like this. This function is presumably generated and used by some automated code generator and not something a human programmer would have to reference.
Yes, but some poor schmuck may have to deal with it. There should be a way to generate a friendly unique name based on the original source construct that caused the name to be generated. If nothing else, it could be based on the source file path and line number, just as an example.
Software Zen:
delete this; -
Someone using that as a function name is certainly no fault of Erlang, but that of a coder who should by up on disciplinary proceedings.
Do what thou wilt shall be the whole of the Law. - Liber AL vel Legis 1:40, Aleister Crowley
Well, it's me who did it. It was approved by all coworkes though. In Erlang we have many single-use one-liner overloads to take advantage of pattern matching. Such code is repeated in so many places that this kind of joke doesn't really hurt anyone. More code:
compute_price('POST', [], User) ->
'4d568c9e-cb32-4db1-a276-26cb06cc3f6f'(User, User:role_atom()).'4d568c9e-cb32-4db1-a276-26cb06cc3f6f'(User, some_atom) ->
{JsonProps, Product} = process_request(Req, User),
RangesFromJson = calendar_lib:json_ranges_to_month_records(proplists:get_value(<<"ranges">>, JsonProps)),
UserClickCounts = [ Range:click_count() || Range <- RangesFromJson],
...This is a very good language to implent any buisness logic or algorithms, but terrible if you try to interact with a front-end in web development
-
Just reading the title of the reference book[^] confirms that I would want nothing to do with that!
Never underestimate the power of human stupidity RAH
I'm sure Yoda will understand that.
I may not last forever but the mess I leave behind certainly will.
-
I oddly like this. This function is presumably generated and used by some automated code generator and not something a human programmer would have to reference.
-
Just reading the title of the reference book[^] confirms that I would want nothing to do with that!
Never underestimate the power of human stupidity RAH
-
'4d568c9e-cb32-4db1-a276-26cb06cc3f6f'(User, SomeVar)
Yep, this is an actual function signature in production code. (Erlang)
Not only that; there are three other functions, within the same file, with names:
4d568c9e-cb32-4db1-a276-26cb06cc3f6**g(User, SomeVar),
4d568c9e-cb32-4db1-a276-26cb06cc3f6h(User, SomeVar),
4d568c9e-cb32-4db1-a276-26cb06cc3f6j**(User, SomeVar),Maybe they should add this functionality to Intellisense: string matching from the trailing end :-)
-
Makes more sense than some of the COBOL procedure and variable names I used to be faced with
FORTRAN was always good too: six character variable and subroutine names...got a little cryptic in large projects. :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
FORTRAN was always good too: six character variable and subroutine names...got a little cryptic in large projects. :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
I wrote my first compiler in Fortran IV - that was fun
-
I wrote my first compiler in Fortran IV - that was fun
-
FORTRAN IV... ah, that brings back old memories... not good ones, but old memories nonetheless!
- I would love to change the world, but they won’t give me the source code.
arrays of 16 bit integers to store strings and bit shifting and masking to access individual characters. Always fun
