dry

A common pattern I come across is the following: form.request input { /* ... */ } form.request input[type="text"] { /* ... */ } form.request select { /* ... */ } form.request br { /* ... */ } I have several lines beginning with the same selector ( form.request ), and I want to select various children. Can I do this in a neater way without the repetition (and preferably without additional dependencies like LESS)? Related question - if all the above comments contain the same styles, can I do better than: form.request input, form.request input[type="text"], form.request select, form.request br {

I wanted to write evaluating predicate in Prolog for arithmetics and I found this : eval(A+B,CV):-eval(A,AV),eval(B,BV),CV is AV+BV. eval(A-B,CV):-eval(A,AV),eval(B,BV),CV is AV-BV. eval(A*B,CV):-eval(A,AV),eval(B,BV),CV is AV*BV. eval(Num,Num):-number(Num). Which is great but not very DRY. I've also found this : :- op(100,fy,neg), op(200,yfx,and), op(300,yfx,or). positive(Formula) :- atom(Formula). positive(Formula) :- Formula =.. [_,Left,Right], positive(Left), positive(Right). ?- positive((p or q) and (q or r)). Yes ?- positive(p and (neg q or r)). No Operator is here matched with _ and

I have made two pages and now I wonder if I can DRY them. Here the XSLT: Frontpage: http://pastebin.com/yuZL913W dagboek-page: http://pastebin.com/6FGYvpvf (Edited) Roelof Sorry one of the links is wrong. I edited this. My question is how to DRY these so I can reuse parts. Only the <div id="posts"> is different. I think I understand the fill in the blanks but it is one big xslt file. Is this possible without named templates and call-templates Here is one way -- what I call " Fill-in-the-blanks " to separate content from processing and to parameterize processing : Rendering file (c:/temp/delete

This question already has an answer here: Never render a layout in response to xhrs 3 answers I have this in my controllers: respond_to do |format| format.html format.js { render :layout => false } end Which outputs without layout when the request is Ajax. I'm replicating this in many actions and controllers. How do I DRY this? I use this in my application controller: class ApplicationController < ActionController::Base layout proc{|c| c.request.xhr? ? false : "application" } end Which covers .js, .json, etc. for me. Well, this answer is a few years late, but you can also create your layout as

I've got a few questions about how to provide both synchronous and asynchronous implementation of the same functionality in a library. I am gonna ask them first and then provide the example code below (which is actually quite a bit, but in fact it's quite simple). Is there an approach to avoid violating the DRY principle? Consider the implementations of JsonStreamReader.Read , JsonStreamWriter.Write , JsonStreamWriter.Flush , ProtocolMessenger.Send , ProtocolMessenger.Receive and their asynchronous versions. Is there an approach to avoid violating the DRY principle when unit testing both

I have a class that requires a non-default copy constructor and assignment operator (it contains lists of pointers). Is there any general way to reduce the code duplication between the copy constructor and the assignment operator? There's no "general way" for writing custom copy constructors and assignment operators that works in all cases. But there's an idiom called "copy-&-swap": class myclass { ... public: myclass(myclass const&); void swap(myclass & with); myclass& operator=(myclass copy) { this->swap(copy); return *this; } ... }; It's useful in many (but not all) situations. Sometimes