## Globals:## Regex to match balanced [brackets]. See Friedl's# "Mastering Regular Expressions", 2nd Ed., pp. 328-331.my$g_nested_brackets;$g_nested_brackets=qr{ (?> # Atomic matching [^\[\]]+ # Anything other than brackets | \[ (??{ $g_nested_brackets }) # Recursive set of nested brackets \] )*}x;# Table of hash values for escaped characters:my%g_escape_table;foreachmy$char(split//,'\\`*_{}[]()>#+-.!'){$g_escape_table{$char}=md5_hex($char);}# Global hashes, used by various utility routinesmy%g_urls;my%g_titles;my%g_html_blocks;# Used to track when we're inside an ordered or unordered list# (see _ProcessListItems() for details):my$g_list_level=0;#### Blosxom plug-in interface ########################################### Set $g_blosxom_use_meta to 1 to use Blosxom's meta plug-in to determine# which posts Markdown should process, using a "meta-markup: markdown"# header. If it's set to 0 (the default), Markdown will process all# entries.my$g_blosxom_use_meta=0;substart{1;}substory{my($pkg,$path,$filename,$story_ref,$title_ref,$body_ref)=@_;if((!$g_blosxom_use_meta)or(defined($meta::markup)and($meta::markup=~ /^\s*markdown\s*$/i))){$$body_ref=Markdown($$body_ref);}1;}
# Check for updates on initial load...if["$DISABLE_AUTO_UPDATE" !="true"]then
/usr/bin/env ZSH=$ZSH zsh $ZSH/tools/check_for_upgrade.sh
fi# Initializes Oh My Zsh# add a function pathfpath=($ZSH/functions $ZSH/completions $fpath)# Load all of the config files in ~/oh-my-zsh that end in .zsh# TIP: Add files you don't want in git to .gitignorefor config_file ($ZSH/lib/*.zsh)source$config_file# Set ZSH_CUSTOM to the path where your custom config files# and plugins exists, or else we will use the default custom/if[[ -z "$ZSH_CUSTOM"]];thenZSH_CUSTOM="$ZSH/custom"fi
is_plugin(){localbase_dir=$1localname=$2test -f $base_dir/plugins/$name/$name.plugin.zsh \||test -f $base_dir/plugins/$name/_$name}# Add all defined plugins to fpath. This must be done# before running compinit.for plugin ($plugins);doif is_plugin $ZSH_CUSTOM$plugin;thenfpath=($ZSH_CUSTOM/plugins/$plugin$fpath)elif is_plugin $ZSH$plugin;thenfpath=($ZSH/plugins/$plugin$fpath)fidone# Load and run compinit
autoload -U compinit
compinit -i
# Load all of the plugins that were defined in ~/.zshrcfor plugin ($plugins);doif[ -f $ZSH_CUSTOM/plugins/$plugin/$plugin.plugin.zsh ];thensource$ZSH_CUSTOM/plugins/$plugin/$plugin.plugin.zsh
elif[ -f $ZSH/plugins/$plugin/$plugin.plugin.zsh ];thensource$ZSH/plugins/$plugin/$plugin.plugin.zsh
fidone# Load all of your custom configurations from custom/for config_file ($ZSH_CUSTOM/*.zsh)source$config_file# Load the themeif["$ZSH_THEME"="random"]thenthemes=($ZSH/themes/*zsh-theme)N=${#themes[@]}((N=(RANDOM%N)+1))RANDOM_THEME=${themes[$N]}source"$RANDOM_THEME"echo"[oh-my-zsh] Random theme '$RANDOM_THEME' loaded..."elseif[ ! "$ZSH_THEME"=""]thenif[ -f "$ZSH/custom/$ZSH_THEME.zsh-theme"]thensource"$ZSH/custom/$ZSH_THEME.zsh-theme"elsesource"$ZSH/themes/$ZSH_THEME.zsh-theme"fififi
classSelectDateWidget(Widget):""" A Widget that splits date input into three <select> boxes. This also serves as an example of a Widget that has more than one HTML element and hence implements value_from_datadict. """none_value=(0,'---')month_field='%s_month'day_field='%s_day'year_field='%s_year'def__init__(self,attrs=None,years=None,required=True):# years is an optional list/tuple of years to use in the "year" select box.self.attrs=attrsor{}self.required=requiredifyears:self.years=yearselse:this_year=datetime.date.today().yearself.years=range(this_year,this_year+10)defrender(self,name,value,attrs=None):try:year_val,month_val,day_val=value.year,value.month,value.dayexceptAttributeError:year_val=month_val=day_val=Noneifisinstance(value,basestring):ifsettings.USE_L10N:try:input_format=get_format('DATE_INPUT_FORMATS')[0]v=datetime.datetime.strptime(value,input_format)year_val,month_val,day_val=v.year,v.month,v.dayexceptValueError:passelse:match=RE_DATE.match(value)ifmatch:year_val,month_val,day_val=[int(v)forvinmatch.groups()]choices=[(i,i)foriinself.years]year_html=self.create_select(name,self.year_field,value,year_val,choices)choices=MONTHS.items()month_html=self.create_select(name,self.month_field,value,month_val,choices)choices=[(i,i)foriinrange(1,32)]day_html=self.create_select(name,self.day_field,value,day_val,choices)output=[]forfieldin_parse_date_fmt():iffield=='year':output.append(year_html)eliffield=='month':output.append(month_html)eliffield=='day':output.append(day_html)returnmark_safe(u'\n'.join(output))
deflinkiff.linked_keg.directory?andf.linked_keg.realpath==f.prefixopoo"This keg was marked linked already, continuing anyway"# otherwise Keg.link will bailf.linked_keg.unlinkendkeg=Keg.new(f.prefix)keg.linkrescueException=>eonoe"The linking step did not complete successfully"puts"The formula built, but is not symlinked into #{HOMEBREW_PREFIX}"puts"You can try again using `brew link #{f.name}'"keg.unlinkohaie,e.backtraceifARGV.debug?@show_summary_heading=trueenddeffix_install_namesKeg.new(f.prefix).fix_install_namesrescueException=>eonoe"Failed to fix install names"puts"The formula built, but you may encounter issues using it or linking other"puts"formula against it."ohaie,e.backtraceifARGV.debug?@show_summary_heading=trueenddefcleanrequire'cleaner'Cleaner.newfrescueException=>eopoo"The cleaning step did not complete successfully"puts"Still, the installation was successful, so we will link it into your prefix"ohaie,e.backtraceifARGV.debug?@show_summary_heading=trueenddefpourfetched,downloader=f.fetchf.verify_download_integrityfetched,f.bottle_sha1,"SHA1"HOMEBREW_CELLAR.cddodownloader.stageendend
,slide:function(type,next){var$active=this.$element.find('.active'),$next=next||$active[type](),isCycling=this.interval,direction=type=='next'?'left':'right',fallback=type=='next'?'first':'last',that=thisthis.sliding=trueisCycling&&this.pause()$next=$next.length?$next:this.$element.find('.item')[fallback]()if($next.hasClass('active'))returnif(!$.support.transition&&this.$element.hasClass('slide')){this.$element.trigger('slide')$active.removeClass('active')$next.addClass('active')this.sliding=falsethis.$element.trigger('slid')}else{$next.addClass(type)$next[0].offsetWidth// force reflow$active.addClass(direction)$next.addClass(direction)this.$element.trigger('slide')this.$element.one($.support.transition.end,function(){$next.removeClass([type,direction].join(' ')).addClass('active')$active.removeClass(['active',direction].join(' '))that.sliding=falsesetTimeout(function(){that.$element.trigger('slid')},0)})}
My family has taken to watching the Big Bang Theory, and while I am extraordinarily tired of the laugh track, I continue to watch.
Naturally, any show targeted at nerds is bound to draw the ire of nerds, who are famed for their desire to find flaws in the opinions and statements of others, especially those who consider themselves nerdy. Indeed, an all-consuming desire for intellectual one-upsmanship (cf. Stephen Potter’s excellent books on the topic) may perhaps be regarded as the sine qua non of nerdhood. This desire can also manifest itself in the needless selection of lengthier words at the expense of more concise ones, the tendency to cite obscure sources, and the general tendency to blather at length.
But I digress.
I would like to take issue on this occasion with the recurring incidence of the game “Rock, Paper, Scissors, Lizard, Spock.” It has a fine wikipedia page, and I won’t describe it here.
My issue is that this RPS variant—and indeed, all of the ones I’ve seen published—can concisely be expressed as simple games of modulo arithmetic. That is:
You pick a number from one to five.
I pick a number from one to five.
Take my number minus your number, modulo five.
If the result is one or two, I win.
If the result is three or four, you win.
If the result is zero, we tie.
Naturally, you can generalize this to any odd number.
It seems to me that this is at the same time simpler, more general, and more nerdy than the game played by those on the show, and I would hope that they would consider changing to my variant, which I call John Brinckerhoff Clements.
Yes, there’s a note on this in the Wikipedia page. Yes, I added it.
One final note: an even nerdier version of this game may be played, still with the fingers of one hand, by throwing any combination of one through four fingers, and interpreting this as a binary number from 0 through 15. I humbly suggest interpreting an extended finger as the digit 1, a non-extended finger as the digit 0, the index finger as the most significant, the little finger as the least significant, and “wrapping around” to regard all fingers extended as a zero.
In fact, this game allows direct comparison of several popular hand gestures. Specifically:
“rock” beats “American f*** you”:
>
“peace” beats “rock”:
>
“Spock” beats the two prior:
>
and “Englishman Drinking Tea” beats “Spock”:
>
This hand is not a game entry. If you see this shape, your opponent is not playing the game:
illegal hand
So the next time someone gives you the finger, just point directly at them, and you win.
!================================================================================================================================!!>Initialises the interpolated point metrics for an interpolated point.SUBROUTINE FIELD_INTERPOLATED_POINT_METRICS_INITIALISE(INTERPOLATED_POINT,INTERPOLATED_POINT_METRICS,ERR,ERROR,*)!Argument variablesTYPE(FIELD_INTERPOLATED_POINT_TYPE),POINTER::INTERPOLATED_POINT!A pointer to the interpolated point to initliase the interpolated point metrics forTYPE(FIELD_INTERPOLATED_POINT_METRICS_TYPE),POINTER::INTERPOLATED_POINT_METRICS!<On exit, a pointer to the interpolated point metrics that have been initialisedINTEGER(INTG),INTENT(OUT)::ERR!<The error codeTYPE(VARYING_STRING),INTENT(OUT)::ERROR!<The error string!Local VariablesINTEGER(INTG)::NUMBER_OF_XI_DIMENSIONS,NUMBER_OF_X_DIMENSIONSINTEGER(INTG)::DUMMY_ERRTYPE(COORDINATE_SYSTEM_TYPE),POINTER::COORDINATE_SYSTEMTYPE(VARYING_STRING)::DUMMY_ERROR,LOCAL_ERRORCALL ENTERS("FIELD_INTERPOLATED_POINT_METRICS_INITIALISE",ERR,ERROR,*999)IF(ASSOCIATED(INTERPOLATED_POINT))THEN IF(ASSOCIATED(INTERPOLATED_POINT_METRICS))THEN CALL FLAG_ERROR("Interpolated point metrics is already associated.",ERR,ERROR,*998)ELSE NULLIFY(COORDINATE_SYSTEM)CALL FIELD_COORDINATE_SYSTEM_GET(INTERPOLATED_POINT%INTERPOLATION_PARAMETERS%FIELD,COORDINATE_SYSTEM,ERR,ERROR,*999)NUMBER_OF_X_DIMENSIONS=COORDINATE_SYSTEM%NUMBER_OF_DIMENSIONSNUMBER_OF_XI_DIMENSIONS=INTERPOLATED_POINT%INTERPOLATION_PARAMETERS%FIELD%DECOMPOSITION%MESH%NUMBER_OF_DIMENSIONSIF(NUMBER_OF_X_DIMENSIONS==SIZE(INTERPOLATED_POINT%VALUES,1))THEN ALLOCATE(INTERPOLATED_POINT_METRICS,STAT=ERR)IF(ERR/=0)CALL FLAG_ERROR("Could not allocate interpolated point metrics.",ERR,ERROR,*999)ALLOCATE(INTERPOLATED_POINT_METRICS%GL(NUMBER_OF_XI_DIMENSIONS,NUMBER_OF_XI_DIMENSIONS),STAT=ERR)IF(ERR/=0)CALL FLAG_ERROR("Could not allocate interpolated point metrics convariant tensor.",ERR,ERROR,*999)ALLOCATE(INTERPOLATED_POINT_METRICS%GU(NUMBER_OF_XI_DIMENSIONS,NUMBER_OF_XI_DIMENSIONS),STAT=ERR)IF(ERR/=0)CALL FLAG_ERROR("Could not allocate interpolated point metrics contravariant tensor.",ERR,ERROR,*999)ALLOCATE(INTERPOLATED_POINT_METRICS%DX_DXI(NUMBER_OF_X_DIMENSIONS,NUMBER_OF_XI_DIMENSIONS),STAT=ERR)IF(ERR/=0)CALL FLAG_ERROR("Could not allocate interpolated point metrics dX_dXi.",ERR,ERROR,*999)ALLOCATE(INTERPOLATED_POINT_METRICS%DXI_DX(NUMBER_OF_XI_DIMENSIONS,NUMBER_OF_X_DIMENSIONS),STAT=ERR)IF(ERR/=0)CALL FLAG_ERROR("Could not allocate interpolated point metrics dXi_dX.",ERR,ERROR,*999)INTERPOLATED_POINT_METRICS%INTERPOLATED_POINT=>INTERPOLATED_POINTINTERPOLATED_POINT_METRICS%NUMBER_OF_X_DIMENSIONS=NUMBER_OF_X_DIMENSIONSINTERPOLATED_POINT_METRICS%NUMBER_OF_XI_DIMENSIONS=NUMBER_OF_XI_DIMENSIONSINTERPOLATED_POINT_METRICS%GL=0.0_DPINTERPOLATED_POINT_METRICS%GU=0.0_DPINTERPOLATED_POINT_METRICS%DX_DXI=0.0_DPINTERPOLATED_POINT_METRICS%DXI_DX=0.0_DPINTERPOLATED_POINT_METRICS%JACOBIAN=0.0_DPINTERPOLATED_POINT_METRICS%JACOBIAN_TYPE=0ELSELOCAL_ERROR="The number of coordinate dimensions ("//TRIM(NUMBER_TO_VSTRING(NUMBER_OF_X_DIMENSIONS,"*",ERR,ERROR))//&&") does not match the number of components of the interpolated point ("//&&TRIM(NUMBER_TO_VSTRING(SIZE(INTERPOLATED_POINT%VALUES,1),"*",ERR,ERROR))//")."CALL FLAG_ERROR(LOCAL_ERROR,ERR,ERROR,*998)ENDIF ENDIF ELSE CALL FLAG_ERROR("Interpolation point is not associated.",ERR,ERROR,*998)ENDIF CALL EXITS("FIELD_INTERPOLATED_POINT_METRICS_INITIALISE")RETURN999CALL FIELD_INTERPOLATED_POINT_METRICS_FINALISE(INTERPOLATED_POINT_METRICS,DUMMY_ERR,DUMMY_ERROR,*998)998CALL ERRORS("FIELD_INTERPOLATED_POINT_METRICS_INITIALISE",ERR,ERROR)CALL EXITS("FIELD_INTERPOLATED_POINT_METRICS_INITIALISE")RETURN 1END SUBROUTINE FIELD_INTERPOLATED_POINT_METRICS_INITIALISE
Ever taken a look at FORTRAN? Actually, I haven’t, either. FORTRAN is basically the oldest non-assembly language around, which is to say the oldest language where someone actually considered “what would programmers like to say?”, rather than “what should the machine be able to do?”
Also, this is FORTRAN 90, which is a much more recent update of FORTRAN. After a quick reading of the Wikipedia page, it looks like f90 (I’m just tired of writing in all caps) is the first update since 1977, which seems ancient but is in fact about halfway between the first invention of FORTRAN and the present day.
It removes many of the restrictions due to machine limitations (allowing free-form source code), and also allows recursive calls, something that the original FORTRAN didn’t—life is easy when you can statically allocate your stack frames!
It also has modules, and… gee whiz: dynamic allocation? Interesting: sounds like it would be much harder to compile f90 code into super-fast assembly than f77, but I suppose you’d have to ask an expert.
Hmmm… I wonder if there’s a formal semantics for more recent versions of Fortran 90? A quick google search suggests the answer is “no”. On the other hand, I’m not sure who would be interested in such a thing; you might be able to sell it as “this formal semantics could identify bugs in your optimization routines”. Anyone want to pay for this?
Okay, back to the source code. What’s going on here?
The first and most obvious thing here is that F90 clearly has a tradition of LONG_CAPITALIZED_VARIABLE_NAMES. COBOL had this going on too, and also an undergraduate classmate of mine named Celeste (RIP, no joke).
I personally find this fairly distracting; it means that a line of source code can’t contain more than two or three tokens, and means that computations have to be split over a whole bunch of lines. On the other hand, local variables apparently have to be declared at the top, so it’s hard to split a large computation into small ones by giving good names to intermediate values.
I think there’s a fairly large split in the world between people who believe that variables should be declared at the top of functions and those who believe that they should be able to appear anywhere; I think that the decls-only-at-top people are imperative people who are planning on doing all kinds of horrible mutation everywhere, and declaring things at the top is their way of preparing themselves for the horror below. The decls-anywhere people (can you tell which I am?), on the other hand, don’t mutate their bindings; these bindings are just a way of giving meaningful names to parts of computation, and there’s no need to hoist them all to the top.
So F90 has the pull toward decls-anywhere that stems from long identifier names, but it’s used by super-imperative people. How do they get any work done? Okay, now I’m just being snide. Sorry. I should point out here that Fortran is clearly one of the massive success stories of language design; it’s one of the first languages, and still in hugely widespread use, thanks in large part to the total 90-degree turn taken by the scientific computing community into C, which is simultaneously the fastest and least optimizable/maintainable language. See Fran Allen’s comments here! Sorry, off topic.
Other, more minor comments: the error-checking code following the dynamic allocation looks like it could easily be abstracted away, especially considering that the error messages aren’t parameterized over the context in any way that I can see.
Broadly speaking, I think I would make local declarations legal anywhere, and shorten up those variable names. Otherwise, looks nice!