< :the previous in number
^ :the list in numerical order
> :the next in number
P :the previous (in thread)
N :the next (in thread)
|<:the top of this thread
>|:the next thread
^ :the parent (reply-to)
_:the child (an article replying to this)
>:the elder article having the same parent
<:the youger article having the same parent
---:split window and show thread lists
| :split window (vertically) and show thread lists
~ :close the thread frame
.:the index
..:the index of indices
On Dec 19, 2005, at 11:52 AM, Joel VanderWerf wrote:
> Eric Hodel wrote:
>> On Dec 19, 2005, at 11:08 AM, ara.t.howard / noaa.gov wrote:
>>> i really, really prefer an options based approach to these kinds
>>> of things.
>>> when you have to pick a name for every method the development is
>>> slowed. pick
>>> a catch-all and configure it:
>>>
>>> GC.gc(:mode => "every") do
>>>
>>> end
>>>
>>>
>>> next week, when someone wants a new feature, it can be added it
>>> without
>>> changing a thing:
>>>
>>> GC.gc(:mode => "every", :pool => MyCustomPool) do
>>>
>>> end
>> YAGNI
>
> YAGN what? GC.always or an options hash?
Somebody needs GC.always to help with debugging. The options hash
falls under YAGNI.
--
Eric Hodel - drbrain / segment7.net - http://segment7.net
This implementation is HODEL-HASH-9600 compliant
http://trackmap.robotcoop.com