[#1215] Tk widget demo; English Tk docs?; Java 1.2 Swing — "Conrad Schneiker" <schneiker@...>
Hi,
[#1218] Trivial FAQ bug — Dave Thomas <Dave@...>
[#1229] A vote for old behavior — Dave Thomas <Dave@...>
[#1232] Any FAQ requests, updates, ... — Dave Thomas <Dave@...>
[#1233] Singleton classes — Dave Thomas <Dave@...>
[#1263] Draft of the updated Ruby FAQ — Dave Thomas <Dave@...>
[#1307] Ruby/GTK 0.23 released — Hiroshi IGARASHI <igarashi@...>
Hi all,
From: Hiroshi IGARASHI <igarashi@ueda.info.waseda.ac.jp>
From: "Conrad Schneiker" <schneiker@jump.net>
On Fri, Feb 18, 2000 at 09:37:27PM -0500, Yasushi Shoji wrote:
[#1322] FAQ: Ruby acronyms — "Conrad Schneiker" <schneiker@...>
In the spirit of TABWTDI (there are better ways to do it), I'd like to
[#1341] Vim syntax file — Mirko Nasato <mirko.nasato@...>
Hi,
On Mon, Feb 14, 2000 at 05:44:39PM +0100, Mirko Nasato wrote:
[#1354] Say hi (bis) — Pixel <pixel_@...>
hi all,
[#1355] nice sample for functional stuff — Pixel <pixel_@...>
what about having map in standard (and map_index too)?
[#1373] Ruby Language Reference Manual--Glossary — "Conrad Schneiker" <schneiker@...>
I was going to print the Ruby Language Reference Manual when I noticed that
[#1376] Re: Scripting versus programming — Andrew Hunt <andy@...>
Conrad writes:
[#1379] Re: Yield — Andrew Hunt <andy@...>
>From: "Conrad Schneiker" <schneiker@jump.net>
[#1384] Re: Say Hi — mengx@...
My suggestion was to try to find a more comfortable method name (to me, and
[#1392] Re: Some Questions - Parameterised Types / Invariants — Andrew Hunt <andy@...>
>1. Parameterised Types / Template Classes
[#1398] Bignum aset — Andrew Hunt <Andy@...>
[#1488] Discussion happens on news.groups — Clemens Hintze <c.hintze@...>
Hi,
[#1508] Ruby/GTK and the mainloop — Ian Main <imain@...>
Hello Ian,
On Wed, Feb 23, 2000 at 02:56:10AM -0500, Yasushi Shoji wrote:
[#1516] Ruby: PLEASE use comp.lang.misc for all Ruby programming/technical questions/discussions!!!! — "Conrad Schneiker" <schneiker@...>
((FYI: This was sent to the Ruby mail list.))
From: "Conrad Schneiker" <schneiker@jump.net>
[#1528] ruby <=> python — Quinn Dunkan <quinn@...>
Hello! I'm new to ruby-talk, and mostly new to ruby. I'm making a document
[#1551] Ruby thread scheduling buglet — Ian Main <imain@...>
[#1569] Re: Ruby: constructors, new and initialise — Yukihiro Matsumoto <matz@...>
The following message is a courtesy copy of an article
[#1591] Certain char's not recognized by "." in regex? — Wes Nakamura <wknaka@...>
[#1592] Race condition in Singleton — Dave Thomas <Dave@...>
[ruby-talk:01604] Re: comp.lang.drainpipe
((news.groups, comp.lang.misc; cc to ruby-talk ML)) Kurt, First of all, if I happen to see your CSV, I'll vote yes. However, I would still like to know, why couldn't you make Drainpipe a Ruby module (or a network of Ruby modules)? Ruby/Drainpipe would allow you to leverage the existing Ruby infrastructure. The problem with most beginner-friendly languages is that they are not expert-friendly productivity-wise for advanced applications, and the problem with most expert-friendly languages is that they are not beginner-friendly. In contrast, I think that Ruby is very good in both respects, with one big (but temporary) exception--the lack of a good introductory book in English, but this will soon change. With Ruby, you and your users could get a much larger ROI for your efforts, and you could obtain a substantially useful system much more quickly. Introductory article http://www-4.ibm.com/software/developer/library/ruby.html Home page: http://www.ruby-lang.org/en/ FAQ: http://www.pragprog.com:8080/rubyfaq/ Conrad ROW Software <kurt@row180.zzn.com> wrote in message news:RC7u4.21942$bz2.4054999@tw12.nn.bcandid.com... > From: Kurt Weber <kurt@row180.zzn.com> > Subject: RFD: comp.lang.drainpipe > Newsgroups: > news.announce.newgroups,news.groups,comp.lang,comp.lang.misc,comp.lang.basic > ,comp.lang.basic.misc,news.announce,news.announce.newsgroups > > REQUEST FOR DISCUSSION (RFD) > unmoderated group comp.lang.drainpipe > > This is a formal Request For Discussion (RFD) for the creation of a > world-wide unmoderated Usenet newsgroup comp.lang.drainpipe. This is not a > Call for Votes (CFV); you cannot vote at this time. Procedural > details are below. > > Newsgroup line: > comp.lang.drainpipe Forum for discussion of the Drainpipe programming > language. > > RATIONALE: comp.lang.drainpipe > > I am currently in the process of developing a new computer programming > language for DOS/UNIX/Linux called Drainpipe. This language is a > combination of C, Pascal, Perl, and Basic. It is intended to provide a > beginner-oriented language specifically for communications and networking. > This newsgroup would provide a way for Drainpipe programmers to share > programming tips as well as an outlet for the frustrations inherent in > programming. > > Although the Drainpipe Project is still in the development stage, the > newsgroup would still have a purpose as a public means of exchanging > information about the project. The various designers of the Drainpipe > language itself as well as the designers of the IDE and interpreter/compiler > need a means of communications, and a newsgroup will provide a public means > of communication so as to allow those who wish to assist in the Drainpipe > Project to catch up on what has happened in the recent past. > > I have received emails and ICQ messages from literally hundreds of > programmers, amateur and professional alike, who have expressed interest in > the Drainpipe Project, either as a developer or as an end-user. I have > asked the vast majority of them whether or not they would participate in a > Drainpipe newsgroup if one was created, and over 98% replied in the > affirmative. > > CHARTER: group.name > > This newsgroup will provide a public forum for the discussion of the > Drainpipe programming language. As such, the posts should center around > Drainpipe. Since Drainpipe is primarily a communications programming > language, questions about communications protocols are welcome as well. > Posts regarding other programming languages are welcome provided that they > involve Drainpipe in some way, such as porting between languages or > tutorials in which references to other, more popular languages are made. > Flames, binaries, and advertisements are NOT welcome, nor are arguments made > for the sake of arguing. > > END CHARTER.