[#5218] Ruby Book Eng tl, ch1 question — Jon Babcock <jon@...>

13 messages 2000/10/02

[#5404] Object.foo, setters and so on — "Hal E. Fulton" <hal9000@...>

OK, here is what I think I know.

14 messages 2000/10/11

[#5425] Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...>

18 messages 2000/10/11
[#5427] RE: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — OZAWA -Crouton- Sakuro <crouton@...> 2000/10/11

At Thu, 12 Oct 2000 03:49:46 +0900,

[#5429] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...> 2000/10/11

Thanks for the input.

[#5432] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Yasushi Shoji <yashi@...> 2000/10/11

At Thu, 12 Oct 2000 04:53:41 +0900,

[#5516] Re: Some newbye question — ts <decoux@...>

>>>>> "D" == Davide Marchignoli <marchign@di.unipi.it> writes:

80 messages 2000/10/13
[#5531] Re: Some newbye question — matz@... (Yukihiro Matsumoto) 2000/10/14

Hi,

[#5544] Re: Some newbye question — Davide Marchignoli <marchign@...> 2000/10/15

On Sat, 14 Oct 2000, Yukihiro Matsumoto wrote:

[#5576] Re: local variables (nested, in-block, parameters, etc.) — Dave Thomas <Dave@...> 2000/10/16

matz@zetabits.com (Yukihiro Matsumoto) writes:

[#5617] Re: local variables (nested, in-block, parameters, etc.) — "Brian F. Feldman" <green@...> 2000/10/16

Dave Thomas <Dave@thomases.com> wrote:

[#5705] Dynamic languages, SWOT ? — Hugh Sasse Staff Elec Eng <hgs@...>

There has been discussion on this list/group from time to time about

16 messages 2000/10/20
[#5712] Re: Dynamic languages, SWOT ? — Charles Hixson <charleshixsn@...> 2000/10/20

Hugh Sasse Staff Elec Eng wrote:

[#5882] [RFC] Towards a new synchronisation primitive — hipster <hipster@...4all.nl>

Hello fellow rubyists,

21 messages 2000/10/26

[ruby-talk:5601] Small contributions

From: hal9000@...
Date: 2000-10-16 18:10:02 UTC
List: ruby-talk #5601
Well, over the last year or so, I have asked a ton of
questions, but I have not contributed as much to the
group as I have got from it.

So I am making a few minor contributions to help even
this out. :)

If you go to my Ruby page, which is still pretty minimal,
I have some new scripts there.

Any comments, criticisms, or suggestions are welcome. If
those are not of interest to the mailing, you can put those
comments in email.

The URL is: http://hypermetrics.com/ruby.html

The two tiniest scripts are docex and codex; which simply
extract embedded docs (or code respectively) from a Ruby
program.

The tool RHH (Ruby HTML Helper) is not finished yet. (I
don't really like the name either, but that is another
issue; it sounds like the American food product "Hamburger
Helper.") This is just an aid in writing CGIs or any program
that generates HTML. The two basic sets of features are: It
enables the output of strings with stackable method calls
like mystring.bold.italics.center and so on; and it allows
the easy conversion of arrays and hashes to HTML tables and
lists.

The Ruby Dependency Tool (which scans for load and require in Ruby
source) is more "finished" than RHH. (Note that most testing has been
done on AIX 4.3.3 with a set of 300 source files. Testing on Win32 has
been minimal so far.)

Here is an excerpt from the docs:

  Usage: ruby rdep.rb sourcefile [searchroot]

  The sourcefile may or may not have a .rb extension.

  The directories in the LOAD_PATH environment variable are searched
  first. File extensions are currently searched for in this order:
  no extension, .rb, .o, .so, .dll (this may not be correct).

  The "searchroot" does not necessarily have anything to do with where
  Ruby is installed. It is merely a directory which will be searched
  (recursively) for files that need to be loaded. This directory is
  only a place to suggest looking for files that have not already been
  found. The default is the current directory (this may change to no
  default at all).

  If there are no detected dependencies, the program will give the
  message, "No dependencies found."

  If the program finds load and require statements that it can
  understand,   it searches for the specified files. Any recognized
  Ruby source files (*.rb) are processed recursively in the same way.
  No attempt is made to open the files that appear to be binary.

  The program will print up to four lists (any or all may be omitted):
    1. A list of files it found by going through LOAD_PATH.;
    2. A list of files found under the searchroot;
    3. A list of directories under searchroot which should perhaps be
       added to LOAD_PATH; and
    4. A list of files (without extensions) which could not be found.

  If there were unparseable load or require statements, a warning will
  be issued.

  Between lists 3 and 4, the program will give an opinion about the
  overall situation. The worst case is that files were not found;
  the uncertain case is when there were unparseable statements; and
  the best case is when all files could be found (lists 1 and 2).


Thanks,
Hal

--
Hal Fulton


Sent via Deja.com http://www.deja.com/
Before you buy.

In This Thread

Prev Next