Return-Path: Received: from punt-1.mail.demon.net by mailstore for rleyton@dogbert.demon.co.uk id 911339901:10:09696:0; Tue, 17 Nov 98 21:58:21 GMT Received: from mail.acm.org ([199.222.69.4]) by punt-1.mail.demon.net id aa1105308; 17 Nov 98 21:58 GMT Received: from brookes.ac.uk (csmail.brookes.ac.uk [161.73.1.1]) by mail.acm.org (8.8.5/8.7.5) with ESMTP id QAA1023628 for ; Tue, 17 Nov 1998 16:57:01 -0500 From: majordomo@brookes.ac.uk Received: by brookes.ac.uk (8.8.7/) id VAA11044; Tue, 17 Nov 1998 21:58:03 GMT Date: Tue, 17 Nov 1998 21:58:03 GMT Message-ID: <199811172158.VAA11044@brookes.ac.uk> To: rleyton@acm.org Subject: Majordomo file: list 'leap' file 'leap.9810' Reply-To: majordomo@brookes.ac.uk X-Mozilla-Status: 8001 -- >From leap-owner Thu Oct 1 21:40:17 1998 Received: by brookes.ac.uk (8.8.7/) id VAA29760; Thu, 1 Oct 1998 21:38:28 +0100 (BST) X-Authentication-Warning: dogbert.demon.co.uk: rleyton owned process doing -bs Date: Thu, 1 Oct 1998 21:07:41 +0100 (BST) From: Richard Leyton X-Sender: rleyton@dogbert.demon.co.uk To: leap@brookes.ac.uk cc: rleyton@acm.org Subject: leap list: Future developments and ideas Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk Well, lots has been happening both with my own personal developments to LEAP, and some others I've recently got wind of. Comments are welcomed from anybody on the list about what's worth pursuing, what's not. Further down, some general news you might be interested in. Lex/Yacc (Appearing in LEAP 1.3) -------------------------------- It's progressing slowly, but getting there. I'm *trying* to keep the original LEAP parser in place for stability reasons, but the more I think about I suspect it's going to have to go to the backup store in the sky. Lex/Yacc should ensure a far more scalable system with new commands being relatively easy to implement, and more consistent - My own tokeniser is very poor (as you've possibly discovered). Indicies (Appearing in LEAP 1.3) -------------------------------- Nothing yet, unfortunately, but I've got some ideas on how to implement it - It'll be a component of the optimiser step to determine which index is available and appropriate for use (it'll be a very simple algorithm). Each of the operators will therefore need some modification to ensure they make use of the information. The information about which relation has what indicies will be stored in the data dictionary as you'd expect New data types (No plans in place yet) -------------------------------------- About time real numbers were implemented, don't you think? And maybe some form of date? We'll see. Now that LEAP stores data in a binary fashion, it shouldn't be too difficult to modify the appropriate routines. Sort/Summary operators (Appearing late in LEAP 1.3 releases) ------------------------------------------------------------ Well, what's the point of storing data if you cannot process it in some way? A big exception from the relational algebra, something that C.J. Date picks up on. Something along the lines of SUMMARISE and EXTEND to process columns and tuples accordingly. An ex-colleague of mine (another Sybase DBA would you believe) has been fiddling with some of this. Script logic (No plans in place yet, but maybe late in 1.3) ----------------------------------------------------------- This same ex-colleague again. Well his wife has recently had a baby, and he's taken a bit of time off, and figured he'd play with LEAP in between nappy changes (as you do), and has started putting some nice goodies into the script processing - parameters, variables, and the beginning of looping and tuple processing. Hey, it's not likely to look much like Transact-SQL, but it could be quite an interesting new feature in due course. Nested relations (No plans in place yet) ---------------------------------------- Remember those papers on nested relations? Well, it shouldn't be conceptually too difficult to put some similair features into LEAP. Ok, you'd probably not have TRUE nested relations, more a reference to another relation and operators modified accordingly. Could be an interesting theoretical addition for the educational users of LEAP. Perl add-on (No plans in place yet) ----------------------------------- I'm crying out for a basic Unix based dbms at work to which I can store data without going the whole hog with another Sybase database in my environment. Perl makes it very easy to get at C library functions withing a scripting environment. I suppose I could use dbm, but that'd be cheating really... ;-) Be useful for a web interface to LEAP too. SQL Subset Support (No plans in place yet) ------------------------------------------ With a Lex/Yacc parser in place, it will be much simpler to put in a new language. I've made some structural changes to LEAP such that it's easy to add in a new language without affecting the underlying logic of LEAP. The 'only' thing that needs doing is the writing of a Lex/Yacc grammar, and the appropriate supporting operations to build the internal representation... Simple? Hmmm. It'd make a very nice Undergraduate project... ;-) And so on... ------------ A lot of vapourware here, I know, but hopefully you'll get the impression that there's lots going on with LEAP in the background, and that the next few releases of LEAP will hopefully be quite interesting. Release dates are doing nothing but slip at the moment, due to work commitments (Heard of EMU?). Some of the above might not arrive, but I hope most of it will in due course. And you...? ----------- Any comments or additions to the above list are greatly welcomed. If you've done some work on LEAP, do let me know about it - I'm very happy to roll in new features to the development releases, or to LEAP 1.2.x if it's stable enough. I can make the existing (very buggy, error prone) tip release of LEAP available on request. News ---- Again, apologies for the recent e-mail explosion on the list. It all seems to be resolved now (famous last words!), and according to Brookes Computer Services (Helpful at last!), it shouldn't happen again. BTW I think you'll find anybody can unsubscribe a problematic subscription from the list if required... Some interesting news from the DBMS area generally - Sybase have recently added their name to the Linux family of vendors. The *BIG* difference between Sybase and Oracle is that you can download and use Sybase Adaptive Server 11.0.3.3 ENTIRELY FREE!! No support, of course, but you can't knock this - it's the version used all over the world in production critical environments, and gets my vote. Try http://www.redhat.com or http://www.caldera.com or, of course, http://www.sybase.com Well, that's enough from me. I look very much forward to hearing some of your thoughts, comments, and maybe some of your source code soon. Regards, Richard -- Richard Leyton mailto:rleyton@acm.org >From leap-owner Sat Oct 3 04:19:33 1998 Received: by brookes.ac.uk (8.8.7/) id EAA11571; Sat, 3 Oct 1998 04:18:05 +0100 (BST) Date: Fri, 2 Oct 1998 16:39:17 +0200 Message-Id: <199810021439.QAA08082@love.dial.xs4all.nl> To: leap@brookes.ac.uk Subject: Re: leap list: Future developments and ideas From: Vincent Zweije In-Reply-To: References: Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk || Lex/Yacc (Appearing in LEAP 1.3) || -------------------------------- || || It's progressing slowly, but getting there. I'm *trying* to keep the || original LEAP parser in place for stability reasons, but the more I think || about I suspect it's going to have to go to the backup store in the sky. || Lex/Yacc should ensure a far more scalable system with new commands being || relatively easy to implement, and more consistent - My own tokeniser is || very poor (as you've possibly discovered). A good lex/yacc scanner/parser combination will give you a intelligeable, stable, and flexible input method. Provided with a good syntax, it will give you a very interesting and potentially powerful query language. Go with lex and yacc. You're designing a language. That's what lex and yacc are for, and they're good at it. || Sort/Summary operators (Appearing late in LEAP 1.3 releases) || ------------------------------------------------------------ || || Well, what's the point of storing data if you cannot process it in some || way? A big exception from the relational algebra, something that C.J. Date || picks up on. Something along the lines of SUMMARISE and EXTEND to process || columns and tuples accordingly. An ex-colleague of mine (another Sybase || DBA would you believe) has been fiddling with some of this. I looked hard to use leap for a practical exercise in a database course. Leap not having aggregation (sum, max, ...) was the killer, and I had to resort to something home-brewn to interpret algebraic queries. Elmasri/Navathe define a grouping+aggregation operator F (written curly-F). It groups tuples, and applies aggregate functions to compute aggregates for each group. If you want a mature dbms, grouping and aggregation are a must. If you're interested, take a look at . It's Dutch, but you'll be able to see the grammar of the algebraic query language that's in there. Mail me if you want to know more. I have some ideas on the grammar you have to develop above. || Nested relations (No plans in place yet) || ---------------------------------------- || || Remember those papers on nested relations? Well, it shouldn't be || conceptually too difficult to put some similair features into LEAP. Ok, || you'd probably not have TRUE nested relations, more a reference to another || relation and operators modified accordingly. Could be an interesting || theoretical addition for the educational users of LEAP. This is opening a big can of worms, I think. First normal form for databases means having flat values in your tables instead of structured ones. Now this need not deter you, but you'll be entering new territories. Think twice. || SQL Subset Support (No plans in place yet) || ------------------------------------------ || || With a Lex/Yacc parser in place, it will be much simpler to put in a new || language. I've made some structural changes to LEAP such that it's easy to || add in a new language without affecting the underlying logic of LEAP. The || 'only' thing that needs doing is the writing of a Lex/Yacc grammar, and || the appropriate supporting operations to build the internal || representation... Simple? Hmmm. It'd make a very nice Undergraduate || project... ;-) Flirting with SQL? There are already so many RDBMSs out there with an SQL interface. I like leap for having a non-SQL high-level query language. Ciao. Vincent. >From leap-owner Mon Oct 5 14:27:41 1998 Received: by brookes.ac.uk (8.8.7/) id OAA17611; Mon, 5 Oct 1998 14:25:17 +0100 (BST) Message-ID: From: "Leyton, Richard" To: "'leap@brookes.ac.uk'" Subject: leap list: Wow... thanks! Date: Mon, 5 Oct 1998 14:23:01 +0100 X-Mailer: Internet Mail Service (5.5.1960.3) Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk It seems I've been nominated for the Free Software Award! http://www.lwn.net/daily/fsa-nominees.html Original announcement is here: http://www.gnu.org/gnu/award.html Thanks to whomever. I'll let you know if I hear anything. Regards, Richard. -- Richard Leyton, Systems Administrator Data Services, Global Technology - Europe, Salomon Brothers Tel: +44 (0)171 721 6503 DSSA Group Line: 721-1567 Fax: +44 (0)171 721 2605 mailto:richard.leyton@ssmb.com DSSA Info: http://euweb/sa/dssa >From leap-owner Mon Oct 5 19:01:49 1998 Received: by brookes.ac.uk (8.8.7/) id TAA05167; Mon, 5 Oct 1998 19:01:44 +0100 (BST) Message-Id: <199810051801.UAA05153@k9.dds.nl> From: tjoen@dds.nl To: leap@brookes.ac.uk Date: Mon, 5 Oct 1998 20:00:58 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: leap list: Merging tables Priority: normal Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk Problem implementing. table AUTOM and mutation table MUTAUT same shape: year integer 4 til string 45 qtty integer 4 In sql easy: insert into mutaut select * from autom; delete from autom; insert into autom select (year, til, sum(qtty)) from mutaut group by yr, til; select distinct til from autom save to textfile; In leap should be possible semiautomated and with script: shellscript (my system: cygwin b19.1, a unix emulator in w95): cd /leap-1.2.2 notepad "database\user\source\mutaut1.src" # yes, that is possible in cygnus :-) echo @ mutaut1 | src/leap --quiet -a database/user/source/mutaut2.src cd database/user/source echo # edit: add (autom) (val1,val2,val3) >>mutaut2.src echo project(autom) (til) >> mutaut2.src echo print @last >>mutaut2.src echo exit >> mutaut2.src notepad mutaut2.src # to delete some unnecessary lines cd ../.. echo @ mutaut2 | src/leap --quiet -a database/user/tempaut.txt cd database/user notepad tempaut.txt cat tempaut.txt | sort >auttils.txt rm tempaut.txt rm source/mutaut2.src # mutaut1.src: relation (mutaut) ((yr,integer,4),(til,string,45),(qtty,integer,4)) # edit: add (mutaut) (yr,til,qtty) without quotes r1=project (autom) (yr,til) r2=project (mutaut) (yr,til) r3=(r1) minus (r2) # Here problem 1: field yr is now a string in place of integer # maybe the cause of next problems? r4=(r2) minus (r1) r51=(r3) join (autom) ((r3.yr=autom.yr) and (r3.til=autom.til)) # Here problem 2: why two fields yr and til? # problem 3: describe r51 doesn't show output so I can't project and # rename for next steps # next steps show my intentions: r53=(r4) join (mutaut) ((r4.yr=mutaut.yr) and (r4.til=mutaut.til)) r5=(r51) union (r53) r6=(r1) intersect (r2) r7=(r6) join (autom) ((r6.yr=autom.yr) and (r6.til=autom.til)) r8=(r7) join (mutaut) ((r7.yr=mutaut.yr) and (r7.til=mutaut.til)) delrel (autom) rename (r5) (autom) change autom print r8 exit >From leap-owner Tue Oct 6 22:02:17 1998 Received: by brookes.ac.uk (8.8.7/) id VAA24167; Tue, 6 Oct 1998 21:59:40 +0100 (BST) X-Authentication-Warning: dogbert.demon.co.uk: rleyton owned process doing -bs Date: Tue, 6 Oct 1998 22:02:32 +0100 (BST) From: Richard Leyton X-Sender: rleyton@dogbert.demon.co.uk To: leap@brookes.ac.uk Subject: Re: leap list: Merging tables In-Reply-To: <199810051801.UAA05153@k9.dds.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk Thanks for the issues. I'll be taking a look in the next few days, and will issue a patch as necessary. Regards, Richard. -- Richard Leyton mailto:rleyton@acm.org On Mon, 5 Oct 1998 tjoen@dds.nl wrote: > Problem implementing. > > table AUTOM and mutation table MUTAUT same shape: > year integer 4 > til string 45 > qtty integer 4 > > In sql easy: > insert into mutaut select * from autom; > delete from autom; > insert into autom select (year, til, sum(qtty)) from mutaut group by > yr, til; > select distinct til from autom save to textfile; > > In leap should be possible semiautomated and with script: > > shellscript (my system: cygwin b19.1, a unix emulator in w95): > cd /leap-1.2.2 > notepad "database\user\source\mutaut1.src" > # yes, that is possible in cygnus :-) > echo @ mutaut1 | src/leap --quiet -a database/user/source/mutaut2.src > cd database/user/source > echo # edit: add (autom) (val1,val2,val3) >>mutaut2.src > echo project(autom) (til) >> mutaut2.src > echo print @last >>mutaut2.src > echo exit >> mutaut2.src > notepad mutaut2.src > # to delete some unnecessary lines > cd ../.. > echo @ mutaut2 | src/leap --quiet -a database/user/tempaut.txt > cd database/user notepad tempaut.txt > cat tempaut.txt | sort >auttils.txt > rm tempaut.txt > rm source/mutaut2.src > > # mutaut1.src: > relation (mutaut) ((yr,integer,4),(til,string,45),(qtty,integer,4)) > # edit: add (mutaut) (yr,til,qtty) without quotes > r1=project (autom) (yr,til) > r2=project (mutaut) (yr,til) > r3=(r1) minus (r2) > > # Here problem 1: field yr is now a string in place of integer > # maybe the cause of next problems? > > r4=(r2) minus (r1) > r51=(r3) join (autom) ((r3.yr=autom.yr) and (r3.til=autom.til)) > > # Here problem 2: why two fields yr and til? > # problem 3: describe r51 doesn't show output so I can't project and > # rename for next steps > # next steps show my intentions: > > r53=(r4) join (mutaut) ((r4.yr=mutaut.yr) and (r4.til=mutaut.til)) > r5=(r51) union (r53) > r6=(r1) intersect (r2) > r7=(r6) join (autom) ((r6.yr=autom.yr) and (r6.til=autom.til)) > r8=(r7) join (mutaut) ((r7.yr=mutaut.yr) and (r7.til=mutaut.til)) > delrel (autom) > rename (r5) (autom) > change autom > print r8 > exit > >From leap-owner Tue Oct 6 22:17:22 1998 Received: by brookes.ac.uk (8.8.7/) id WAA24981; Tue, 6 Oct 1998 22:17:20 +0100 (BST) X-Authentication-Warning: dogbert.demon.co.uk: rleyton owned process doing -bs Date: Tue, 6 Oct 1998 22:20:10 +0100 (BST) From: Richard Leyton X-Sender: rleyton@dogbert.demon.co.uk To: leap@brookes.ac.uk Subject: leap list: Re: Y2K Compliant (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk Might be of interest to readers... ;-) Richard. -- Richard Leyton mailto:rleyton@acm.org ---------- Forwarded message ---------- Date: Tue, 6 Oct 1998 22:16:19 +0100 (BST) From: Richard Leyton To: Subject: Re: Y2K Compliant , LEAP does NOT store or process dates, except when appending the datestamp to the output file of a session log, and that's merely informational. It uses standard ANSI 'C' code for this purpose. You can check the source code yourself if you like, it's included in the standard distribution. I'm *obviously* unable to speak for any local changes that may have been made. You should consult and fully understand the GNU General Public License for limits of liability and warranty. This details the terms and conditions under which LEAP is distributed. See http://www.fsf.org/copyleft/gpl.html - Full details are also in the file COPYING in the standard LEAP distribution. Full details are also at http://www.dogbert.demon.co.uk/leap.html So how Y2K compliant is a package that doesn't process dates? Your call. ;-) I'd of course be very interested to know to what purpose you or your company is using LEAP. Regards, Richard Leyton. -- Richard Leyton mailto:rleyton@acm.org On Tue, 6 Oct 1998, somebody who discovered a package they'd never seen before on a shared networked file system wrote: > Is your product, LEAP, Year 2000 compliant? > > Thanks, > > >From leap-owner Tue Oct 6 23:41:01 1998 Received: by brookes.ac.uk (8.8.7/) id XAA28257; Tue, 6 Oct 1998 23:40:46 +0100 (BST) X-Authentication-Warning: dogbert.demon.co.uk: rleyton owned process doing -bs Date: Tue, 6 Oct 1998 23:30:53 +0100 (BST) From: Richard Leyton X-Sender: rleyton@dogbert.demon.co.uk To: leap@brookes.ac.uk Subject: Re: leap list: Merging tables In-Reply-To: <199810051801.UAA05153@k9.dds.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk All, Ok, problem 1 is definately a bug - The 'describe' command references 'leapattributes', which is only ever populated with 'STRING' values in user created relations created by the PROJECT command. A new bit of code is required to tidy this up. Shouldn't take much time. Problem 2 is causing a core dump on my Linux system, caused by some nasty code in the rl_naturaljoin function of rtional.c that 99% of the time is ok, but in this particular example causes a problem. I've got to investigate *why* this particular piece of code is producing NULL tuple structures for valid relations. It's late right now, so I'll tackle this later this week when I have more time. If anybody else fancies a go, feel free... ;-) As far as I can tell, these bugs will appear in LEAP 1.2 and LEAP 1.2.2. Regards, Richard. -- Richard Leyton mailto:rleyton@acm.org On Mon, 5 Oct 1998 tjoen@dds.nl wrote: > Problem implementing. > > table AUTOM and mutation table MUTAUT same shape: > year integer 4 > til string 45 > qtty integer 4 > > In sql easy: > insert into mutaut select * from autom; > delete from autom; > insert into autom select (year, til, sum(qtty)) from mutaut group by > yr, til; > select distinct til from autom save to textfile; > > In leap should be possible semiautomated and with script: > > shellscript (my system: cygwin b19.1, a unix emulator in w95): > cd /leap-1.2.2 > notepad "database\user\source\mutaut1.src" > # yes, that is possible in cygnus :-) > echo @ mutaut1 | src/leap --quiet -a database/user/source/mutaut2.src > cd database/user/source > echo # edit: add (autom) (val1,val2,val3) >>mutaut2.src > echo project(autom) (til) >> mutaut2.src > echo print @last >>mutaut2.src > echo exit >> mutaut2.src > notepad mutaut2.src > # to delete some unnecessary lines > cd ../.. > echo @ mutaut2 | src/leap --quiet -a database/user/tempaut.txt > cd database/user notepad tempaut.txt > cat tempaut.txt | sort >auttils.txt > rm tempaut.txt > rm source/mutaut2.src > > # mutaut1.src: > relation (mutaut) ((yr,integer,4),(til,string,45),(qtty,integer,4)) > # edit: add (mutaut) (yr,til,qtty) without quotes > r1=project (autom) (yr,til) > r2=project (mutaut) (yr,til) > r3=(r1) minus (r2) > > # Here problem 1: field yr is now a string in place of integer > # maybe the cause of next problems? > > r4=(r2) minus (r1) > r51=(r3) join (autom) ((r3.yr=autom.yr) and (r3.til=autom.til)) > > # Here problem 2: why two fields yr and til? > # problem 3: describe r51 doesn't show output so I can't project and > # rename for next steps > # next steps show my intentions: > > r53=(r4) join (mutaut) ((r4.yr=mutaut.yr) and (r4.til=mutaut.til)) > r5=(r51) union (r53) > r6=(r1) intersect (r2) > r7=(r6) join (autom) ((r6.yr=autom.yr) and (r6.til=autom.til)) > r8=(r7) join (mutaut) ((r7.yr=mutaut.yr) and (r7.til=mutaut.til)) > delrel (autom) > rename (r5) (autom) > change autom > print r8 > exit > >From leap-owner Thu Oct 8 02:58:07 1998 Received: by brookes.ac.uk (8.8.7/) id CAA01964; Thu, 8 Oct 1998 02:57:19 +0100 (BST) Date: Thu, 8 Oct 1998 03:55:21 +0200 (METDST) To: joy43@westad.eis.uva.es From: joy43@westad.eis.uva.es (Fun N' Easy) Comments: Authenticated sender is Subject: leap list: Premium CABLE TV .......No Monthly Bills! Message-Id: <199810071858IAA6224@Tryitzone.thermo-b.mw.tu-muenchen.de> Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk This is really cool! PREMIUM CHANNELS........Descrambled! EASY to assemble plans for only $7.00 ! YOU WILL BE WATCHING all your FAVORITE PAY STATIONS featuring MOVIES, SPORTS. Adult entertainment, and any other scrambled signal NEXT WEEK! You can EASILY assemble a cable descrambler in less than 30 minutes! You have probably seen many advertisments for similar plans......... BUT OURS are BETTER! We have compared it to all the others and have actually IMPROVED the quality and SIMPLIFIED the design !!! ** We even include PHOTOS! ** OUR PLANS ARE BETTER! We have NEW, EASY TO READ,EASY to assemble plans for only $7.00! We have seen them advertised for as much as $29.00 and you have to wait weeks to receive them! WHAT THE OTHERS SAY IS TRUE! Parts are available at "The TV HUT" or any electronics store. Trademark rights do not allow us to use a national electronics retail chains' name but there is one in your town! Call and ask them BEFORE you order! They are very familiar with these plans! You will need these easy to obtain parts : 270-235 mini box 271-1325 2.2k ohm resistor 278-212 chasis connectors RG59 coaxial cable #12 copper wire Variable capacitor They may have to special order the variable capacitor, But WHY WAIT for a special order? WE have them! All you need now is the EASY TO ASSEMBLE plans to show you how this educational device in 30 MINUTES! WE have secured a supply of the capacitors directly from the manufacturer and We WILL include one with your plans for an ADDITIONAL $10.00 only! It is LEGAL, providing of course you use these plans for EDUCATIONAL PURPOSES only. See first hand and LEARN how this SIMPLE circuitry works! If you intend to use these plans for any other purpose DO NOT ORDER them. IT'S FUN TO BUILD! We're sure you'll enjoy this project! This is a unique opportunity for hobbiest of ANY skill level to learn simple circuitry! Learn how easy descrambling is! $ 7.00 for plans only $10.00 for variable capacitor only $17.00 for The easy to assemble plans and one variable capacitor! Pay by check or money order payable to: Kraftworks P.O. Box 11752 San Rafael, Ca. 94912 WE pay postage and handling! Please allow 10 days for delivery. This is a one time only mailing! You have already been placed on our remove list and will not receive another offer from us! Thank You >From leap-owner Fri Oct 9 22:59:56 1998 Received: by brookes.ac.uk (8.8.7/) id WAA26332; Fri, 9 Oct 1998 22:59:16 +0100 (BST) X-Authentication-Warning: dogbert.demon.co.uk: rleyton owned process doing -bs Date: Fri, 9 Oct 1998 23:02:07 +0100 (BST) From: Richard Leyton X-Sender: rleyton@dogbert.demon.co.uk To: leap@brookes.ac.uk Subject: leap list: Free Software Aware Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk Again, thanks to whomever for the nomination. I have to say it was touching, but the competition was a bit on the heavy side! For a list of the finalists, take a look at: http://lwn.net/daily/fsa-finalists.html I'm sure you'll agree the list is impressive, and that the finalists have all contributed a great deal towards the Free Software Movement. Maybe next year, eh! ;-) Regards, Richard. PS. The award is announced tonight (9th October), and will probably be available at http://lwn.net/daily pretty soon afterwards. -- Richard Leyton mailto:rleyton@acm.org >From leap-owner Sat Oct 10 14:29:45 1998 Received: by brookes.ac.uk (8.8.7/) id OAA19973; Sat, 10 Oct 1998 14:29:31 +0100 (BST) X-Authentication-Warning: dogbert.demon.co.uk: rleyton owned process doing -bs Date: Sat, 10 Oct 1998 13:45:00 +0100 (BST) From: Richard Leyton X-Sender: rleyton@dogbert.demon.co.uk To: leap@brookes.ac.uk Subject: leap list: LEAP 1.2.3 patch Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk All, Some of the problems reported to this list earlier in the week have been fixed. I've attached a patch for LEAP 1.2.2, and will be issuing a 1.2 patch later in the week. Don't try applying THIS patch to LEAP 1.2. If you're not sure, look at the home directory for the existance of a leap-1.2.2.lsm file, or check src/include/consts.h, or run 'leap -v'. To apply the patch, save it to your LEAP directory, un-package it, and run the command: patch -p1 < patch122.123 (Patch application instructions are in the new FAQ). Before I issue a full 1.2.3 release, I'd appreciate it if you could let me know of any problems you discover with this release. Regards, Richard. Content-Type: application/x-gzip patch122.123.gz Content-Transfer-Encoding: x-uuencode Content-Disposition: inline; filename="patch122.123.gz" -- Richard Leyton mailto:rleyton@acm.org >From leap-owner Wed Oct 14 06:05:25 1998 Received: by brookes.ac.uk (8.8.7/) id GAA15102; Wed, 14 Oct 1998 06:04:34 +0100 (BST) From: Shahjay@aol.com Message-ID: Date: Wed, 14 Oct 1998 01:03:50 EDT To: leap@brookes.ac.uk Mime-Version: 1.0 Subject: leap list: unsubscribe Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: AOL 3.0 16-bit for Windows sub 38 Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk unsubscribe >From leap-owner Wed Oct 14 06:22:23 1998 Received: by brookes.ac.uk (8.8.7/) id GAA15476; Wed, 14 Oct 1998 06:21:58 +0100 (BST) Message-ID: <36243140.4DDA3BE7@hclt.com> Date: Wed, 14 Oct 1998 10:36:08 +0530 From: "S.Ganesh" X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.0 i586) MIME-Version: 1.0 To: leap@brookes.ac.uk Subject: leap list: unsubscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk unsubscribe >From leap-owner Wed Oct 14 08:19:26 1998 Received: by brookes.ac.uk (8.8.7/) id IAA18629; Wed, 14 Oct 1998 08:19:24 +0100 (BST) Message-ID: From: "Leyton, Richard" To: "'leap@brookes.ac.uk'" Subject: RE: leap list: unsubscribe Date: Wed, 14 Oct 1998 08:18:41 +0100 X-Mailer: Internet Mail Service (5.5.1960.3) Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk It's really not that difficult. Send an e-mail to: majordomo@brookes.ac.uk The body of the message should contain 'unsubscribe leap'. Leave the subject blank. Regards, Richard. -- Richard Leyton, Systems Administrator Data Services, Global Technology - Europe, Salomon Brothers Tel: +44 (0)171 721 6503 DSSA Group Line: 721-1567 Fax: +44 (0)171 721 2605 mailto:richard.leyton@ssmb.com DSSA Info: http://euweb/sa/dssa > ---------- > From: S.Ganesh[SMTP:sganesh@hclt.com] > Sent: October 14 1998 06:06 > To: leap@brookes.ac.uk > Subject: leap list: unsubscribe > > unsubscribe > >From leap-owner Thu Oct 15 17:44:39 1998 Received: by brookes.ac.uk (8.8.7/) id RAA27499; Thu, 15 Oct 1998 17:43:44 +0100 (BST) Message-ID: <362625CD.65E84B0@incyte.com> Date: Thu, 15 Oct 1998 09:41:49 -0700 From: Gershon Wolfe X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: leap@brookes.ac.uk Subject: leap list: unsubscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk unsubscribe >From leap-owner Fri Oct 16 19:42:21 1998 Received: by brookes.ac.uk (8.8.7/) id TAA01844; Fri, 16 Oct 1998 19:41:04 +0100 (BST) Message-ID: <19981016143238.A2727@A470.demon.co.uk> Date: Fri, 16 Oct 1998 14:32:38 +0000 From: Darren Wyn Rees To: leap@brookes.ac.uk Subject: is leap suitable for this? (gy: leap list: uns*bscr*be) References: <362625CD.65E84B0@incyte.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <362625CD.65E84B0@incyte.com>; from Gershon Wolfe on Thu, Oct 15, 1998 at 09:41:49AM -0700 X-WWW: http://www.netlink.co.uk/cgi-merlin/lwgate X-PGP: finger merlin@netlink.co.uk for key X-PGP-Fingerprint: F8 79 5E 84 F0 20 A5 62 FA 2D E9 BD BE 06 7D 10 Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk On Thu, Oct 15, 1998 at 09:41:49AM -0700, Gershon Wolfe wrote: > uns*bscr*be That's 3 unzub requests in 3 days, not bad for a low-traffic list, eh. Why not switch on Majordomo's administrivia option? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ (I'd love to finish a filter (be that in procmail or whatever) that zaps these type of requests, but I never get around to doing it). Here's my Leap question... I am attempting to develop a 'wordserver' based on a database of Welsh verbs. Each record in the database will have one verb in 'vanilla-format' (eg. "rhedeg" (run)) and about forty+ permutations on that (eg. "rhedais" (I ran), "rhedir", (3rd person, impersonal, run)) etc. The verbs follow 'rule sets' : 80% 'run' exactly the same according to 2 basic rules... the rest have numerous exceptions & sub-rule sets. Is Leap suitable for this application? (Or is it overkill for what I'm trying to achieve?) Leap is the only open-source (IIRC) relational database I could find, so I'm rather hoping it _can be used for the above application. Well, cheers, -- Darren Rees merlin@netlink.co.uk 2000+ Berfau; fformat .zip .htm M$ Access CSV http://www.netlink.co.uk/users/merlin/berfau/ >From leap-owner Fri Oct 16 20:02:24 1998 Received: by brookes.ac.uk (8.8.7/) id UAA03437; Fri, 16 Oct 1998 20:02:13 +0100 (BST) From: "Peter T. Breuer" Message-Id: <199810161900.VAA24675@oboe.it.uc3m.es> Subject: Re: is leap suitable for this? (gy: leap list: uns*bscr*be) To: leap@brookes.ac.uk Date: Fri, 16 Oct 1998 21:00:07 +0200 (MET DST) In-Reply-To: <19981016143238.A2727@A470.demon.co.uk> from "Darren Wyn Rees" at Oct 16, 98 02:32:38 pm X-Anonymously-To: X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk "A month of sundays ago Darren Wyn Rees wrote:" > > That's 3 unzub requests in 3 days, not bad for a low-traffic > list, eh. Why not switch on Majordomo's administrivia option? > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > (I'd love to finish a filter (be that in procmail or whatever) > that zaps these type of requests, but I never get around > to doing it). :0 HB * unsubscribe /dev/null Peter >From leap-owner Mon Oct 19 11:32:34 1998 Received: by brookes.ac.uk (8.8.7/) id LAA07770; Mon, 19 Oct 1998 11:29:52 +0100 (BST) Message-ID: From: "Leyton, Richard" To: "'leap@brookes.ac.uk'" Subject: RE: is leap suitable for this? (gy: leap list: uns*bscr*be) Date: Mon, 19 Oct 1998 11:29:01 +0100 X-Mailer: Internet Mail Service (5.5.1960.3) Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk On two general notes (I'll address your LEAP specific question later from home)... Not sure what this 'administrivia' option is, but I'll see what the majordomo owner has to say about this, following the recent explosion of mail he was very helpful. (I suspect the recent mailing explosion is why we're seeing so many - people getting back from holidays and so forth, finding 100+ e-mails from this mailing list). I'm not particularly keen about a moderated mailing list, as it stifles things if I'm away or too busy (EMU!) for a period of time. I've tried to be as specific as possible in unsubscription instructions in the FAQ, the documents, and on the web, as well as my mailings to this group, but there's no getting through to some people. Just incase: Send e-mail to >majordomo@brookes.ac.uk< containing one line in the BODY of the message: unsubscribe leap Mails sent to leap@brookes.ac.uk (in reply to the mail, for example) will be sent to the entire list. On the second point, LEAP is *NOT* the only open-source databases - Postgres has it's source avaialable (although not entirely under GNU). The GNU project has it's own RDBMS in development, but it's very young and very immature, as well as poorly documented. As you'd imagine, it's available under GNU. There are a number of other projects, but very few of them are under GNU, so be very wary of the authors intentions with the product - especially if you contribute code. Source is available for a number of semi-commerical offerings, such as MSQL. There is a free alternative, called 'MySQL', but I'm not sure if it's GNU or not. Take a look at http://www.dogbert.demon.co.uk/leap.html, and click on 'Related Sites' - I've linked to a number of alternatives. See also http://www.yahoo.co.uk in the computing/software/databases section. Regards, Richard. -- Richard Leyton, Systems Administrator Data Services, Global Technology - Europe, Salomon Brothers Tel: +44 (0)171 721 6503 DSSA Group Line: 721-1567 Fax: +44 (0)171 721 2605 mailto:richard.leyton@ssmb.com DSSA Info: http://euweb/sa/dssa > ---------- > From: Darren Wyn Rees[SMTP:merlin@A470.demon.co.uk] > Sent: October 16 1998 15:32 > To: leap@brookes.ac.uk > Subject: is leap suitable for this? (gy: leap list: uns*bscr*be) > > On Thu, Oct 15, 1998 at 09:41:49AM -0700, Gershon Wolfe wrote: > > > uns*bscr*be > > That's 3 unzub requests in 3 days, not bad for a low-traffic > list, eh. Why not switch on Majordomo's administrivia option? > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > (I'd love to finish a filter (be that in procmail or whatever) > that zaps these type of requests, but I never get around > to doing it). > > Here's my Leap question... > I am attempting to develop a 'wordserver' > based on a database of Welsh verbs. Each record in the > database will have one verb in 'vanilla-format' > (eg. "rhedeg" (run)) and about forty+ permutations on that > (eg. "rhedais" (I ran), "rhedir", (3rd person, > impersonal, run)) etc. The verbs follow 'rule sets' : > 80% 'run' exactly the same according to 2 basic rules... > the rest have numerous exceptions & sub-rule sets. > > Is Leap suitable for this application? (Or is it overkill > for what I'm trying to achieve?) > > Leap is the only open-source (IIRC) relational database > I could find, so I'm rather hoping it _can be used > for the above application. > > Well, cheers, > -- > Darren Rees merlin@netlink.co.uk > > 2000+ Berfau; fformat .zip .htm M$ Access CSV > http://www.netlink.co.uk/users/merlin/berfau/ > >From leap-owner Mon Oct 19 22:36:03 1998 Received: by brookes.ac.uk (8.8.7/) id WAA19782; Mon, 19 Oct 1998 22:35:53 +0100 (BST) X-Authentication-Warning: dogbert.demon.co.uk: rleyton owned process doing -bs Date: Mon, 19 Oct 1998 22:36:49 +0100 (BST) From: Richard Leyton X-Sender: rleyton@dogbert.demon.co.uk To: leap@brookes.ac.uk Subject: leap list: LEAP 1.2.3 released Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk All, LEAP 1.2.3 is now available as a full distribution, as a patch for 1.2.2, and as a Windows distribution. See http://www.dogbert.demon.co.uk/download.htm for full details. A patch for 1.2 will *NOT* be available, due to a change in the source management system. 1.2.2 Installations: Download the patch, and run "patch -p1 < patch122.123" from the base of the 1.2.2 installation. The patch includes a couple of additional bug fixes from the previous patch, but nothing show-stopping. Windows distribution: No databases are included. Run 'src/runme.bat' to intall the databases. Previous 1.2.2 databases will work just fine, so LEAP.EXE can be simply copied over. As always, please report any bugs you encounter in any release of LEAP. I'd rather receive 10 repeat bug notifications, than none at all. Regards, Richard. Save to file HTTP links: Unix/Source distribution: http://www.dogbert.demon.co.uk/leap-1.2.3.tar.gz Windows distribution: http://www.dogbert.demon.co.uk/wleap123.tgz 1.2.3 patch for 1.2.2 installations: http://www.dogbert.demon.co.uk/patches/leap122.123.gz FTP links will be available in the next few days. -- Richard Leyton mailto:rleyton@acm.org >From leap-owner Tue Oct 20 15:50:18 1998 Received: by brookes.ac.uk (8.8.7/) id PAA08687; Tue, 20 Oct 1998 15:49:05 +0100 (BST) Message-ID: From: "Leyton, Richard" To: "'leap@brookes.ac.uk'" Subject: RE: leap list: LEAP 1.2.3 released Date: Tue, 20 Oct 1998 15:47:40 +0100 X-Mailer: Internet Mail Service (5.5.1960.3) Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk Ooops, appears that config.cache and config.log snuck into the distribution. You might find it breaks the build process on some systems, although my Solaris test build seemed unaffected. The fix is to remove config.cache before running 'configure'. Oh, and CYGWIN.DLL is missing from the Windows 1.2.3 distribution - I'll repackage it and redistribute it. In the meantime, just copy it across from the 1.2 distribution into the src directory. Links are still valid for 1.2 on the web pages. Regards, Richard. -- Richard Leyton, Systems Administrator Data Services, Global Technology - Europe, Salomon Brothers Tel: +44 (0)171 721 6503 DSSA Group Line: 721-1567 Fax: +44 (0)171 721 2605 mailto:richard.leyton@ssmb.com DSSA Info: http://euweb/sa/dssa > ---------- > From: Richard Leyton[SMTP:rleyton@acm.org] > Sent: October 19 1998 22:36 > To: leap@brookes.ac.uk > Subject: leap list: LEAP 1.2.3 released > > All, > > LEAP 1.2.3 is now available as a full distribution, as a patch for 1.2.2, > and as a Windows distribution. > > See http://www.dogbert.demon.co.uk/download.htm for full details. > > A patch for 1.2 will *NOT* be available, due to a change in the source > management system. > > 1.2.2 Installations: Download the patch, and run "patch -p1 < > patch122.123" from the base of the 1.2.2 installation. The patch includes > a couple of additional bug fixes from the previous patch, but nothing > show-stopping. > > Windows distribution: No databases are included. Run 'src/runme.bat' to > intall the databases. Previous 1.2.2 databases will work just fine, so > LEAP.EXE can be simply copied over. > > As always, please report any bugs you encounter in any release of LEAP. > I'd rather receive 10 repeat bug notifications, than none at all. > > Regards, > > Richard. > > Save to file HTTP links: > > Unix/Source distribution: > http://www.dogbert.demon.co.uk/leap-1.2.3.tar.gz > > Windows distribution: > http://www.dogbert.demon.co.uk/wleap123.tgz > > 1.2.3 patch for 1.2.2 installations: > http://www.dogbert.demon.co.uk/patches/leap122.123.gz > > FTP links will be available in the next few days. > > -- > Richard Leyton > mailto:rleyton@acm.org > > >From leap-owner Wed Oct 21 23:59:55 1998 Received: by brookes.ac.uk (8.8.7/) id XAA00063; Wed, 21 Oct 1998 23:59:07 +0100 (BST) X-Authentication-Warning: dogbert.demon.co.uk: rleyton owned process doing -bs Date: Thu, 22 Oct 1998 00:02:05 +0100 (BST) From: Richard Leyton X-Sender: rleyton@dogbert.demon.co.uk To: leap@brookes.ac.uk Subject: leap list: Bugs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk All, I've been doing some more tidying and bug fixing in 1.2.x, and have discovered a nasty little bug. Deletions from a relation will delete the DATA, but the hash table is not touched. The result is that you can delete something, but LEAP will not allow you to add it back in again. This is because it checks the hash table before writing the tuple, and finds an entry already there. Set the mindebuglevel to 3 or higher (in LEAP 1.2.2 or greater), and you'll see what I mean. I'll have it fixed by the end of the week, and get a patch out. This affects all versions of 1.2. Regards, Richard. -- Richard Leyton mailto:rleyton@acm.org >From leap-owner Sat Oct 24 18:16:16 1998 Received: by brookes.ac.uk (8.8.7/) id SAA27513; Sat, 24 Oct 1998 18:15:35 +0100 (BST) Message-ID: <36320BEE.B876E135@acm.org> Date: Sat, 24 Oct 1998 18:18:38 +0100 From: Richard Leyton X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: LEAP Mailing List Subject: leap list: Patches and early releases Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk All, If you want to get your hands on an early release of LEAP 1.2.4, which does a fair bit of tidying and fixing, point your browser to: http://www.dogbert.demon.co.uk/patches Files are p.gz - eg p122.124.gz for the 1.2.2 to 1.2.4 patch. They're all compressed with GZIP. or http://www.dogbert.demon.co.uk/releases For the full release. Patch application, as ever, is with 'patch -p1 < patchfile', from the base of your LEAP installation. A word of warning - LEAP 1.2.4 (and 1.2.3.1) has not been as thoroughly tested as I would like, but I've not seen any serious bugs/crashes in a fair while. And I hope to have some good news on the Windows front in the not too distant future. Right - now for a pint or two of Guiness... Regards, Richard. -- Richard Leyton mailto:rleyton@acm.org >From leap-owner Tue Oct 27 23:06:12 1998 Received: by brookes.ac.uk (8.8.7/) id XAA22533; Tue, 27 Oct 1998 23:05:12 GMT X-Authentication-Warning: dogbert.demon.co.uk: rleyton owned process doing -bs Date: Tue, 27 Oct 1998 23:05:08 +0000 (GMT) From: Richard Leyton X-Sender: rleyton@dogbert.demon.co.uk To: leap@brookes.ac.uk Subject: leap list: LEAP 1.2.4 released Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk All, LEAP 1.2.4 has been released, fixing serious bugs (as per my earlier e-mail to this list), and adding some nice new functionality: * Relation printing scalable, tidier and more informative. * New option --merge-stderr. * Status reporting on previous operation condensed. The bugs fixes are mainly to do with hash table maintenance. The hash table code had some serious bugs, which affected a lot of the operation of LEAP - notably the maintenance of system relations and adding data to a table after a delete occured. If you've ever seen Sybase's isql formatting, then you'll like the new formatting LEAP performs - it's properly scalable now, and will show the entire field without truncation. So for wide xterms, it's ideal. The new option puts all of stderr into stdout. Why? All will be revealed in due course. Default behaviour has NOT changed. Status reporting condensed: The output from the installation process is very noisy, as is any script which does lots of 'add' operations - Each time the operation is called, it returns the relation name. This now only occurs at the end of a script, or at the end of an interactive command. Cuts the output significantly. Links are available on the LEAP web page, and it is available now from: http://www.dogbert.demon.co.uk/releases http://www.dogbert.demon.co.uk/patches - Patches should be uncompressed and applied with 'patch -p1 < patchfile' from the base of the installation. Patches are only available for LEAP 1.2.2 and greater. Regards, Richard. -- Richard Leyton mailto:rleyton@acm.org >From leap-owner Thu Oct 29 21:57:50 1998 Received: by brookes.ac.uk (8.8.7/) id VAA20109; Thu, 29 Oct 1998 21:57:00 GMT Message-ID: <3638E458.A95AF1C9@acm.org> Date: Thu, 29 Oct 1998 21:55:36 +0000 From: Richard Leyton X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: LEAP Mailing List Subject: leap list: Crashing on startup Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: leap-owner@brookes.ac.uk Precedence: bulk Reply-To: leap@brookes.ac.uk All, LEAP 1.2.4 has a rather nasty bug that only seems to manifest itself on Sun Solaris. However, it's caused by an uninitialised pointer (eek!) in the main LEAP loop, so it could affect more systems. Apply the patch below by saving the code between PATCH_START and PATCH_END, and running 'patch -p1 patchfile' in the base of the LEAP directory. Downloads from the www.dogbert.demon.co.uk/releases will be corrected by the time you read this. Other distributions will not for a few days. Many apologies for this, I normally test LEAP on Linux, Windows and Solaris systems. This time I skipped Solaris. I'll not be making that mistake again! Regards, Richard. PATCH_START Index: leap/src/leap.c diff -c leap/src/leap.c:1.207.2.4 leap/src/leap.c:1.207.2.5 *** leap/src/leap.c:1.207.2.4 Tue Oct 27 22:06:48 1998 --- leap/src/leap.c Thu Oct 29 21:17:42 1998 *************** *** 1,7 **** /* * Name: leap.c * Description: Main LEAP loop and functions. ! * Version: leap.c,v 1.207.2.4 1998/10/27 22:06:48 rleyton Exp * * LEAP - An extensible and free RDBMS * Copyright (C) 1997-1998 Richard Leyton --- 1,7 ---- /* * Name: leap.c * Description: Main LEAP loop and functions. ! * Version: leap.c,v 1.207.2.5 1998/10/29 21:17:42 rleyton Exp * * LEAP - An extensible and free RDBMS * Copyright (C) 1997-1998 Richard Leyton *************** *** 105,111 **** char maincommand[MAXIMUM_INPUT_STRING+1]; char tprompt[MAXIMUM_INPUT_STRING+1]; char *result,*tresult; ! relation result_relation; int res,startscript=0; do_debug(DEBUG_ENTER,"Entering do_leap()"); --- 105,111 ---- char maincommand[MAXIMUM_INPUT_STRING+1]; char tprompt[MAXIMUM_INPUT_STRING+1]; char *result,*tresult; ! relation result_relation=NULL; int res,startscript=0; do_debug(DEBUG_ENTER,"Entering do_leap()"); PATCH_END -- Richard Leyton mailto:rleyton@acm.org