quote:

...the context-sensitive return value of an array...

Bonus posted:

Ultimate variable naming scheme

nebby posted:

nebby posted:

If we had editors that let you have rich symbology, colors, icons, tables, and flow diagrams instead just a static grid of ascii text of course this whole argument we just had would be moot since naming would take a backseat. Fortress doesn't count because you have to run the whole thing through LaTeX, and it's read only.

such a nice boy posted:

Is that a lesbian porn button under the YouTube button? And why is there a Shakespeare button? Is that to solve the "million monkeys at a million typewriters" problem?

Scaevolus posted:

This is sarcasm, right? _please?

Bonus posted:

I never found the appeal of those keyboards because I rarely look at my keyboard and when I need to do stuff quickly I rely on vim's command mode or just on keyboard shortcuts in general while in other applications.

nebby posted:

One thing I think would be really interesting would be the introduction of a kanji-like symbology so the density of information in code could go way up since the cardinality of characters would be much, much higher.

Ryouga Inverse posted:

Do you ever stop masturbating to thoughts of how steeper learning curves could be added to programming?

Triple Tech posted:

These things, as Perl programmer, piss me off:

code:

@stack = ();
for ($i = 0; $i < scalar @elements; $i++) {
  $temporary = do_something_to $elements[$i];

  push @stack, $temporary;
}

It's abundantly clear this person doesn't know about scope, the context-sensitive return value of an array, foreach loops, and map. God drat.

code:

print HANDLE "This one also demonstrates something else.";
print HANDLE "This programmer doesn't know how to use select.";
print HANDLE "Nor does he know what a heredoc is.";
print HANDLE "You get paragraphs of text that look like this.";
print HANDLE "For no reason, really.";

Point is, for you non-Perl folk, is that this poo poo could have been written in a more concise, more native-to-Perl fashion.

Kidane posted:

While I am paid to write Perl, I am by no means an expert. However, I'm of the opinion that there is nothing inherent to Perl which requires overly-concise code.

nebby posted:

Fortress doesn't count because you have to run the whole thing through LaTeX, and it's read only.

Dijkstra posted:

APL is a mistake, carried through to perfection. It is the language of the future for the programming techniques of the past: it creates a new generation of coding bums.

Kidane posted:

code:

my $parse_mail = Email::Simple -> new( $email );
my $sender = $parse_mail -> header( "From" );
my $jira_summary = $parse_mail -> header( "Subject" );
my $jira_description = $parse_mail -> body;

I know of the more Perl-like way to write that, I just don't care.

Triple Tech posted:

code:

print HANDLE "This one also demonstrates something else.";
print HANDLE "This programmer doesn't know how to use select.";
print HANDLE "Nor does he know what a heredoc is.";
print HANDLE "You get paragraphs of text that look like this.";
print HANDLE "For no reason, really.";

quote:

Then you're no friend of mine. There's a difference between being concise and golfing (which Perl folk love to do) and this isn't golfing. The entire field of computer science has been about a power versus concision payoff. And if you can't see that, then you're hopeless.

Triple Tech posted:

Then you're no friend of mine. There's a difference between being concise and golfing (which Perl folk love to do) and this isn't golfing. The entire field of computer science has been about a power versus concision payoff. And if you can't see that, then you're hopeless.

code:

my $parse_mail       = new Email::Simple($email);
my $sender           = $parse_mail->header('From');
my $jira_summary     = $parse_mail->header('Subject');
my $jira_description = $parse_mail->body;

tef posted:

I believe you are looking for APL.

nebby posted:

it doesn't appear APL is considered a universally discarded idea.

nebby posted:

You could project APL in plain text

nebby posted:

A bigger problem though is that Fortress doesn't let you mix domain languages (it's domain is higher mathematics, really) but that's an altogether different problem than the one APL and Fortress are trying to solve with symbology.

tef posted:

I think you're looking for katahdin.

dustgun posted:

Back to crummy code.

code:

int Parser::Find()
{
    int found = -1;
    int i;
	for(i = 0 ; i < BUFFER_SIZE ; i++)
	{
		if (STOPWORD == m[i])
		{
                    found = 1;
		    break;
		} 
	}

	if (found != 1)
	{
		 i = -1;
        } 
	return (i);
}// end function

Khorne posted:

People write code that bad? I hope it was a first year student.

Victor posted:

Clearly, return is a function.

the talent deficit posted:

code:

var e208e29dbee8c7f3994a32f56e0be770=document.createElement('form');

rotor posted:

jesus christ what the hell

Victor posted:

Clearly, return is a function.

Victor posted:

Clearly, return is a function.

dustgun posted:

I should mention, just for the sake of mentioning, that this was written by a coworker of a friend of mine. I changed the method and variable names, but, it's real live code somewhere.

the talent deficit posted:

So then, in the javascript, I find an eyeframe that's loading this (except it goes on for about six pages):

Surge Strip posted:

code:

function Upercase(str : string) : string;
   var
   len : integer;
   count : integer;
   newstring : string;
   begin
   len := length(str);
   count := 0;
   while (count < len) do
      begin
      newstring[count] := str[count] - 32;
      count := count + 1;
      end;
   result := newstring;
   end;

pokeyman posted:

(Did I miss anything?)