[#386100] Numeric#coerce docs are disaster — 7stud -- <bbxx789_05ss@...>

num.coerce(numeric) =E2=86=92 array

14 messages 2011/08/02

[#386114] Documentation Improvement Proposal — Chris White <cwprogram@...>

=3D Issues =3D

24 messages 2011/08/02
[#386115] Re: Documentation Improvement Proposal — Steve Klabnik <steve@...> 2011/08/02

I reeeeeealy dislike user comments on documentation. It's one of the

[#386117] Re: Documentation Improvement Proposal — Phillip Gawlowski <cmdjackryan@...> 2011/08/02

On Tue, Aug 2, 2011 at 7:39 PM, Steve Klabnik <steve@steveklabnik.com> wrot=

[#386118] Re: Documentation Improvement Proposal — Steve Klabnik <steve@...> 2011/08/02

> What's wrong with stealing WikiPedia's procedures? The model works

[#386119] Re: Documentation Improvement Proposal — Chris White <cwprogram@...> 2011/08/02

On Aug 2, 2011, at 11:00 AM, Steve Klabnik wrote:

[#386123] Re: Documentation Improvement Proposal — Steve Klabnik <steve@...> 2011/08/02

Apologies, I've just responded to everyone in-line.

[#386231] Brainstorming ideas how to improve Ruby's documentation — Marc Heiler <shevegen@...>

The title is misleading...

42 messages 2011/08/05
[#386233] Re: Brainstorming ideas how to improve Ruby's documentation — "Fred L." <f.linard@...> 2011/08/05

Hello,

[#386235] Re: Brainstorming ideas how to improve Ruby's documentation — Alexander Litvinovsky <alexander.litvinovsky@...> 2011/08/05

What are you talking about? Ruby has a nice docs, railsapi.com for example.

[#386297] Help out with the next version of ruby-lang.org — Magnus Holm <judofyr@...>

https://github.com/rubylang/ruby-lang.org

11 messages 2011/08/07

[#386341] Exceptional Ruby and Metaprogramming Ruby has anyone picked these up? — Kevin <darkintent@...>

I'm thinking of picking up these two books and was wondering if anyone

11 messages 2011/08/09

[#386378] ruby installation — "Momodou J." <modou75alieu@...>

how to implement this in windows :

16 messages 2011/08/09

[#386401] *WHY* does this not work? — serialhex <serialhex@...>

ok, so code:

23 messages 2011/08/09
[#386403] Re: *WHY* does this not work? — "Darryl L. Pierce" <mcpierce@...> 2011/08/09

On Wed, Aug 10, 2011 at 03:52:59AM +0900, serialhex wrote:

[#386404] Re: *WHY* does this not work? — serialhex <serialhex@...> 2011/08/09

On Tue, Aug 9, 2011 at 3:05 PM, Darryl L. Pierce <mcpierce@gmail.com> wrote:

[#386480] Odd regexp behavior — Glen Holcomb <damnbigman@...>

I'm running 1.9.2-p180

16 messages 2011/08/10

[#386506] Distributing Ruby program as a standalone executable (exe) for windows — Michelle Pace <michelle@...>

Hello there,

10 messages 2011/08/11

[#386539] Online tutor for Ruby — T J Pereira <tj5155@...>

I am finding it difficult to apply the RUBY program. Its because i have

18 messages 2011/08/12
[#386541] Re: Online tutor for Ruby — Phillip Gawlowski <cmdjackryan@...> 2011/08/12

On Fri, Aug 12, 2011 at 6:00 AM, T J Pereira <tj5155@tm.net.my> wrote:

[#386637] class inheritance and class constants — Iñaki Baz Castillo <ibc@...>

------------------------

16 messages 2011/08/14

[#386784] Green Shoes v1.0 released — ashbb <ashbbb@...>

Hello, everyone.

15 messages 2011/08/18
[#392062] Re: Green Shoes v1.0 released — Barry Yu <yubarry@...> 2012/01/09

why do I get this error?

[#386796] Searching in a directory — Yu Yu <htwoo@...>

Hello,

21 messages 2011/08/18

[#386893] Gritty Details of super() — luke gruber <luke.gru@...>

Hey guys,

18 messages 2011/08/21

[#386900] Possble bug in Ruby parser (Fixnum#times within "case" statement) — Iñaki Baz Castillo <ibc@...>

Hi, I cannot find an explanation for the following issue so I think it's a =

15 messages 2011/08/21
[#386901] Re: Possble bug in Ruby parser (Fixnum#times within "case" statement) — Ryan Davis <ryand-ruby@...> 2011/08/21

[#386903] Re: Possble bug in Ruby parser (Fixnum#times within "case" statement) — Iñaki Baz Castillo <ibc@...> 2011/08/21

2011/8/22 Ryan Davis <ryand-ruby@zenspider.com>:

[#386920] New to Ruby some problems — jack jones <shehio_22@...>

I am new to Ruby, My mother tongue is C++ .. I have too many problems I

21 messages 2011/08/22

[#386949] Want to get involved with this doc stuff? I'm making it even easier — Steve Klabnik <steve@...>

Hey guys-

9 messages 2011/08/22

[#387058] How the access the values of this result — QAS WM <qaiserwali@...>

I am getting the following as a result of a script I run.

11 messages 2011/08/26

[#387070] overloading methods question please? — jack jones <shehio_22@...>

def do_something(a as Array)

11 messages 2011/08/26

[#387138] String#split resets regex captures variables (Ruby 1.8.7) — Olivier Lance <bestiol@...>

Hi,

10 messages 2011/08/29

[#387196] SAMSUNG to produce "Ruby on Rails in Silicon" System on a Chip — Ilias Lazaridis <ilias@...>

(public draft)

9 messages 2011/08/31

[#387197] Prepend a character to a string in ruby — ruby rails <rubyonrails4me@...>

Hi,

10 messages 2011/08/31

[#387212] GUI programming — Samuel Mensah <sasogeek@...>

Is ruby GUI programming something that will come along as I study ruby

19 messages 2011/08/31
[#387230] Re: GUI programming — Alexey Petrushin <axyd80@...> 2011/08/31

I believe right now it's better to stay with console, there's no Ruby

[ANN] alf 0.10.0 Released

From: Bernard Lambeau <blambeau@...>
Date: 2011-08-15 09:16:09 UTC
List: ruby-talk #386680
Hi all! Alf version 0.10.0 has been released! This release brings lots of
new
features and enhancements as well as a fresh new documentation website
available at http://blambeau.github.com/alf.

Relational Algebra at your fingertips

* <http://blambeau.github.com/alf>
* <http://github.com/blambeau/alf>
* <http://rubygems.org/gems/alf>
* <http://rubydoc.info/gems/alf>

Alf brings the relational algebra both in Shell and in Ruby. In Shell,
because
manipulating any relation-like data source should be as straightforward as
a
one-liner. In Ruby, because I've never understood why programming languages
provide data structures like arrays, hashes, sets, trees and graphs but not
_relations_... Let's stop the segregation ;-)

Alf follows semantic versioning (http://semver.org/) and has not reached
its
first stable 1.0.0 release. Quoting semver.org: "Anything may change at any
time. The public API should not be considered stable". Including alf with
the
version requirement "~> 0.10.0" shouldn't break your code.

Changes:

# 0.10.0 / 2011-08-15

## New recognized data sources

* Alf now provides an Environment implementation on top of a SQL database.
  This means that SQL tables can now be used as data-sources. This feature
  relies on the sequel gem ('gem install sequel' is required), that drives
  recognized SQL servers. Then (don't forget that ALF_OPTS also exists):

      % alf --env=postgres://user:password@host/database show table

* Alf now recognizes and allows manipulating .csv files as first-class data
  sources. CSV output is also supported of course. Under ruby <= 1.9, the
  fastercsv gem is required ('gem install fastercsv' is required). Then:

      % alf restrict suppliers.csv -- "city == 'Paris'"    (input)
      % alf show suppliers --csv                           (output)

* Alf now recognizes and allows manipulating .log files as first-class data
  sources. This feature relies on request-log-analyzer gem that provides the
  parsers that Alf uses, and the log formats it recognizes
  ('gem install request-log-analyzer' is required). See examples/logs.

## New operators and enhancements

* A GENERATOR operator is introduced. It allows generating a relation with
one
  auto-number attribute, up to a given size.

* A COERCE operator is introduced. It provides a quick way to obtain
type-safe
  relations from type-unsafe sources like .csv files. For example:

      % alf coerce mydirtyfile.csv -- name String  price Float  at Time

  The coerce operator is of course available in Ruby as well:

      (coerce "mydirtyfile.csv", :name => String, :price => Float, :at =>
Time)

* The DEFAULTS (non-relational) operator now accepts default values as tuple
  expressions. When used in shell, provided default values are now evaluated
  that way. This allows specifying default values as being computed on the
  current tuple.

* Aggregations in the Lispy DSL must not be prefixed by Agg:: anymore.

## Miscellaneous enhancements

* Added 'alf --input-reader' to specify $stdin format (csv, rash, etc.)
* Added 'alf -Ipath' that mimics ruby's -I (add path to $LOAD_PATH before
run)
* Lispy#run supports command arguments to be passed as a string
* Lispy#run supports piped commands, with '|' as in shell

## Hurting changes to Lispy DSL (and therefore to Relation)

* The attribute-name syntax of aggregation operators has been removed. The
Agg::
  prefix must not be specified anymore.

      Agg::sum(:qty)    # !! error !!
      Agg::sum{ qty }   # !! error !!
      sum{ qty }        # simply, and only!

* The group aggregation operator has been removed. It will probably be
replaced
  in a future version. In the meantime, the GROUP relational operator
allows
  obtaining similar results.

* Lispy syntax of CLIP has changed (when used with --allbut option)

      (clip :suppliers, [:name, :city], true)
(before)
      (clip :suppliers, [:name, :city], :allbut => true)
 (after)

* Lispy syntax of DEFAULTS has changed (when used with --strict option)

      (defaults :suppliers, {:country => 'Belgium'}, true)
 (before)
      (defaults :suppliers, {:country => 'Belgium'}, :strict => true)
(after)

* Lispy syntax of GROUP has changed (when used with --allbut option)

      (group :supplies, [:sid], :supplying, true)
(before)
      (group :supplies, [:sid], :supplying, :allbut => true)
 (after)

* Lispy syntax of PROJECT has changed (when used with --allbut option)

      (project :suppliers, [:name, :city], true)
 (before)
      (project :suppliers, [:name, :city], :allbut => true)
(after)

* Lispy syntax of SUMMARIZE has changed (when used with --allbut option)

      (summarize :supplies, [:qty, :pid], {...}, true)
 (before)
      (summarize :supplies, [:qty, :pid], {...}, :allbut => true)
(after)

## Hurting changes in shell

* The attribute-name syntax of aggregation operators has been removed

      sum(:qty)   # !! error !!
      sum{ qty }  # works

* Shell syntax of GROUP has changed (option separator before introduced
name)

      % alf --text group supplies  -- pid qty supplying
(before)
      % alf --text group supplies  -- pid qty -- supplying
 (after)

* Shell syntax of WRAP has changed (option separator before introduced name)

      % alf --text wrap suppliers -- city status loc_and_status
(before)
      % alf --text wrap suppliers -- city status -- loc_and_status
 (after)

* Shell syntax of QUOTA has changed (--by and --order become pure arguments)

      % alf quota supplies --by=sid --order=qty -- position count sum_qty
"sum{ qty }" (before)
      % alf quota supplies -- sid -- qty -- position count sum_qty "sum{ qty
}"        (after)

* Shell syntax of RANK has changed (--order becomes a pure argument)

      % alf rank parts --order=weight,desc,pid,asc -- position
 (before)
      % alf rank parts -- weight desc pid asc -- position
(after)

* Shell syntax of SUMMARIZE has changed (--by becomes a pure argument)

      % alf summarize supplies --by=sid -- total_qty "sum{ qty }"
 (before)
      % alf summarize supplies -- sid -- total_qty "sum{ qty }"
 (after)

## Bug fixes

* [In shell] Options are now correctly parsed in presence of option
separators.
  That is, every argument after a '--' separator is considered a non-option
  argument.

In This Thread

Prev Next