[#7043] RUBYOPT versioning? — Caleb Tennis <caleb@...>
Matz, others:
[#7050] RDoc patches for BigDecimal in Ruby CVS — mathew <meta@...>
Now that 1.8.4 is out and the initial flurry of problem reports has died
[#7055] More on VC++ 2005 — Austin Ziegler <halostatue@...>
Okay. I've got Ruby compiling. I'm attempting to get everything in
Hi,
On 05/01/06, nobuyoshi nakada <nobuyoshi.nakada@ge.com> wrote:
On 06/01/06, Austin Ziegler <halostatue@gmail.com> wrote:
Hi,
On 09/01/06, nobuyoshi nakada <nobuyoshi.nakada@ge.com> wrote:
[#7057] 64-bit Solaris READ_DATA_PENDING Revisited — Steven Lumos <steven@...>
[#7078] CRC - a proof-of-concept Ruby compiler — Anders Hkersten <chucky@...>
Hello everyone,
[#7084] mathn: ugly warnings — hadmut@... (Hadmut Danisch)
Hi,
Hadmut Danisch wrote:
Daniel Berger wrote:
*Dean Wampler *<deanwampler gmail.com> writes:
On Fri, 13 Jan 2006, mathew wrote:
On Fri, 13 Jan 2006, Mathieu Bouchard wrote:
ara.t.howard@noaa.gov wrote:
On Fri, 13 Jan 2006, James Britt wrote:
Dean Wampler <deanwampler gmail.com> writes:
On Sat, 14 Jan 2006, mathew wrote:
[#7100] core dump with ruby 1.9.0 (2006-01-10) and bdb-0.5.8 — Tanaka Akira <akr@...17n.org>
I found following test script dumps core.
>>>>> "T" == Tanaka Akira <akr@m17n.org> writes:
In article <200601110905.k0B950Op001713@moulon.inra.fr>,
[#7109] Calling flock with block? — Bertram Scharpf <lists@...>
Hi,
On Thu, 12 Jan 2006, Bertram Scharpf wrote:
[#7129] YAML.load({[]=>""}.to_yaml) — Tanaka Akira <akr@...17n.org>
I found that current YAML doesn't round trip {[]=>""}.
Hi.
Hi.
In article <20060115202203.D3624CA0.ocean@m2.ccsnet.ne.jp>,
[#7162] FileUtils.mv does not unlink source file when moving over filesystem boundary — Pav Lucistnik <pav@...>
Hi,
On Mon, 16 Jan 2006, Pav Lucistnik wrote:
[#7178] Add XHTML 1.0 Output Support to Ruby CGI — Paul Duncan <pabs@...>
The attached patch against Ruby 1.8.4 adds XHTML 1.0 output support to
[#7186] Ruby 1.9 and FHS — "Kirill A. Shutemov" <k.shutemov@...>
Build and install system changes:
[#7195] trouble due ruby redefining posix function eaccess — noreply@...
Bugs item #3317, was opened at 2006-01-24 15:33
[#7197] SSL-enabled DRb fds on SSLError? — ctm@... (Clifford T. Matthews)
Howdy,
On Jan 24, 2006, at 12:46 PM, Clifford T. Matthews wrote:
Patch worked fine against HEAD.
[#7203] bcc32's memory manager bug — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp>
Hi.
[#7211] Some troubles with an embedded ruby interpreter — Matt Mower <matt.mower@...>
Hi folks,
[#7216] String#scan loops forefever if scanned string is modified inside block. — noreply@...
Bugs item #3329, was opened at 2006-01-26 10:55
[#7226] Fwd: Re: Question about massive API changes — "Sean E. Russell" <ser@...>
Hello,
Sean E. Russell wrote:
>
On 1/28/06, Caleb Tennis <caleb@aei-tech.com> wrote:
On Saturday 28 January 2006 17:13, Wilson Bilkovich wrote:
Sean E. Russell wrote:
[#7249] PATCH: append option to sysread — Yohanes Santoso <ysantoso-rubycore@...>
[#7259] TCP/UDP server weird lags on 1.8.4 linux — "Bill Kelly" <billk@...>
Hi !
Re: Design contracts and refactoring (was Re: mathn: ugly warnings)
On Fri, 13 Jan 2006, Mathieu Bouchard wrote:
> Is there a way for code to get automatically included by rdoc and counted as
> doc without having it in two places in the source code? I mean code that
> would get run when loading a library. That way, doing "ri MyStuff" could
> display the contract for MyStuff, supposing that it's in the same file as
> the implementation.
>
> However I suppose that doing it for unit-tests (that are presumably in a
> separate file) isn't supported... yet.
oh yeah - i forgot to mention that the README is auto generated using the
samples too. so, if one has
~ > cat sample/a.rb
require "yaml"
y 42
~ > ruby sample/a.rb
---
42
then the above text, exactly, is used both to auto-generate the readme AND as
a unit test (getting expected from sample/expected/a.rb).
here's how the tests (samples) are run:
#
# find sample and expected dirs
#
sampledir = File::expand_path(File::join(dirname, File::join("..", "sample")))
expecteddir = File::join sampledir, "expected"
#
# this tests everything in samples/* and compares against samples/expected/*
#
Class::new(Test::Unit::TestCase) do
def setup; end
samples = Dir[File::join(sampledir, "*")].select{|entry| test ?f, entry}
test_nn = "test_sample_00"
sample_output_expected = lambda do |sample, expected|
lambda do
actual = IO::popen("ruby -I#{ libdir } #{ sample } 2>&1"){|pipe| pipe.read}
expected = IO::read expected
begin
actual_doc = ::YAML::load actual
expected_doc = ::YAML::load expected
rescue Exception
nil # load failure
ensure
assert_equal actual, expected
end
end
end
samples.each do |sample|
dirname, basename = File::split sample
expected = File::join expecteddir, basename
next unless test ?e, sample and test ?e, expected
define_method(test_nn, sample_output_expected[sample, expected])
test_nn.succ!
end
end
the README file is a template which is expanded to include a
~> cat a.rb
the code
~> ruby a.rb
the output
section for each sample.
primative i know... but works really well for my simple libs. it might be
worth abstractin to use a few output formats (besides yaml) and to use jamis
buck's syntax module to actually markup the code in the readme.
regards.
-a
--
strong and healthy, who thinks of sickness until it strikes like lightning?
preoccupied with the world, who thinks of death, until it arrives like
thunder? -- milarepa