RE: [ANNOUNCE] AxKit 1.0

2000-10-03 Thread MarkH

nice - i especially like the faq:

 q) Should I ever run with scissors?
 a) No. You should never, ever run with scissors

..as at first i was wondering what this "scissors" perl module was that i'd
never heard of :-

time for a break from geekdom i think

mark

ref: http://axkit.org/faq.xml
--
Agile HTML Editor
  Agilic Corporation
http://www.agilic.com




 -Original Message-
 From: Matt Sergeant [SMTP:[EMAIL PROTECTED]]
 Sent: Monday, October 02, 2000 7:30 PM
 To:   AxKit Users Mailing List
 Cc:   [EMAIL PROTECTED]; Perl-XML Mailing List
 Subject:  [ANNOUNCE] AxKit 1.0
 
 I've finally managed to put AxKit 1.0 out, after a long run-up to the 1.0
 release. There are a couple of known issues with XSP and a couple of other
 potential bugs still standing, but the API is now stable, and we can add
 further enhancements as "bug fixes" now. Despite these minor bugs, AxKit
 has proved to be very stable for production use, with no noticable memory
 leakage over time.
 



RE: [ANNOUNCE] AxKit 1.0

2000-10-03 Thread Gunther Birznieks

Ironically, this is also from early versions of Windows 95 where the 
startup tips also say this eventually (if you leave them on enough).

Maybe Matt's a Microsoft Mole :)

At 08:53 AM 10/3/00 +0100, [EMAIL PROTECTED] wrote:
nice - i especially like the faq:

  q) Should I ever run with scissors?
  a) No. You should never, ever run with scissors

..as at first i was wondering what this "scissors" perl module was that i'd
never heard of :-

time for a break from geekdom i think

mark

ref: http://axkit.org/faq.xml
--
Agile HTML Editor
   Agilic Corporation
 http://www.agilic.com




  -Original Message-
  From: Matt Sergeant [SMTP:[EMAIL PROTECTED]]
  Sent: Monday, October 02, 2000 7:30 PM
  To:   AxKit Users Mailing List
  Cc:   [EMAIL PROTECTED]; Perl-XML Mailing List
  Subject:  [ANNOUNCE] AxKit 1.0
 
  I've finally managed to put AxKit 1.0 out, after a long run-up to the 1.0
  release. There are a couple of known issues with XSP and a couple of other
  potential bugs still standing, but the API is now stable, and we can add
  further enhancements as "bug fixes" now. Despite these minor bugs, AxKit
  has proved to be very stable for production use, with no noticable memory
  leakage over time.