[#4766] Wiki — "Glen Stampoultzis" <trinexus@...>

21 messages 2000/09/04
[#4768] RE: Wiki — "NAKAMURA, Hiroshi" <nahi@...> 2000/09/04

Hi, Glen,

[#4783] Re: Wiki — Masatoshi SEKI <m_seki@...> 2000/09/04

[#4785] Re: Wiki — "NAKAMURA, Hiroshi" <nakahiro@...> 2000/09/05

Howdy,

[#4883] Re-binding a block — Dave Thomas <Dave@...>

16 messages 2000/09/12

[#4930] Perl 6 rumblings -- RFC 225 (v1) Data: Superpositions — Conrad Schneiker <schneik@...>

Hi,

11 messages 2000/09/15

[#4936] Ruby Book Eng. translation editor's questions — Jon Babcock <jon@...>

20 messages 2000/09/16

[#5045] Proposal: Add constants to Math — Robert Feldt <feldt@...>

15 messages 2000/09/21

[#5077] Crazy idea? infix method calls — hal9000@...

This is a generalization of the "in" operator idea which I

17 messages 2000/09/22

[#5157] Compile Problem with 1.6.1 — Scott Billings <aerogems@...>

When I try to compile Ruby 1.6.1, I get the following error:

15 messages 2000/09/27

[ruby-talk:5197] ANNOUNCE: rubyweb -- literate programming for ruby?

From: Hugh Sasse Staff Elec Eng <hgs@...>
Date: 2000-09-29 18:03:26 UTC
List: ruby-talk #5197
I have developed a system for re-sequencing embedded documentation
in Ruby programs.  This is designed to interoperate with RDtool, and
it is not in competition with it.  For example, it does not support
different kinds of emphasis, headings, and so on.  Also one can
use "\n=begin_rubyweb"..."\n=end_rubyweb" so that "\n=end " (with a
space) is not matched.

What it does is allow blocks to be given names and then used inside other
named blocks.  They may thus appear in any desired sequence for whatever
purpose.  This could be used for embedding internal and external
documentation in a program, or embedding LaTeX and troff documents in the
same file, or even as a pre-processor to avoid repeating your code.  I am
hoping that it will be useful enough to provide a way to do things I never
considered.

Caveats:

I have tested this and have used it to my own satisfaction.  I have not
written the RubyUnit tests for it, and I believe that from that viewpoint
the code is poorly structured.  Suggestions on re-factoring to enable
better testing, etc, would be welcome.

The code is supplied under the same terms as Ruby itself.  It is offered
in the hope that it might be useful to others, but without warranty.  I
have not really done much with literate programming, so Rubyweb may not be
sufficiently useful.  Constructive criticism is welcome.

The details and the code may be found at

http://www.eng.cse.dmu.ac.uk/~hgs/ruby/rubyweb/index.html

I'm not sure about how to submit this to the RAA, but I will
wait for some peer review first, anyway :-)

	Hugh
	hgs@dmu.ac.uk


In This Thread

Prev Next