[perl #39697] [TODO] Tcl - use the standard library code

2006-07-03 Thread via RT
# New Ticket Created by Matt Diephouse # Please include the string: [perl #39697] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=39697 > Tcl comes with several procedures that are actually written in Tcl as part of the s

Re: Licenses and library code

2003-12-23 Thread Todd Olson
At 09:44 -0500 2003/12/23, Dan Sugalski wrote: > >Yep, as well as in the LICENSE file in the main directory, and a couple of other >places. I should probably put together a cron job to mail off a monthly reminder to >the list as well, but that might be a bit of overkill. In view of SCO's recent

Re: Licenses and library code

2003-12-23 Thread Dan Sugalski
At 12:15 AM + 12/23/03, Harry Jackson wrote: Dan Sugalski wrote: We're starting to check in library code, which brings up the annoying issue of licensing. Since we haven't been able to go the easy (i.e. all public domain) route for parrot we need to deal with this. The license

Re: Licenses and library code

2003-12-22 Thread Harry Jackson
Dan Sugalski wrote: We're starting to check in library code, which brings up the annoying issue of licensing. Since we haven't been able to go the easy (i.e. all public domain) route for parrot we need to deal with this. The license on Parrot itself is straightforward enough, albeit

Licenses and library code

2003-12-22 Thread Dan Sugalski
We're starting to check in library code, which brings up the annoying issue of licensing. Since we haven't been able to go the easy (i.e. all public domain) route for parrot we need to deal with this. The license on Parrot itself is straightforward enough, albeit a bit odd what with

Re: Library code

2003-09-25 Thread Leopold Toetsch
Dan Sugalski <[EMAIL PROTECTED]> wrote: > Fair enough. I'd not realized we had a runtime directory. BTW some warnocked stuff: Date: Sat, 23 Aug 2003 17:01:36 +0200 From: Leopold Toetsch <[EMAIL PROTECTED]> Subject: some fun SubProxy ,--[ orig text ]

Re: Library code

2003-09-25 Thread Dan Sugalski
On Thu, 25 Sep 2003, Leopold Toetsch wrote: > Dan Sugalski wrote: > > > Okay, we're starting to get some library code. I've a full (hopefully) > > ncurses interface .pasm file > > The ncurses lib is reall great. :) Now we can have multicolored life! Woohoo!

Re: Library code

2003-09-25 Thread Leopold Toetsch
Dan Sugalski wrote: Okay, we're starting to get some library code. I've a full (hopefully) ncurses interface .pasm file The ncurses lib is reall great. lib/ subdirectory for assembly and/or imcc library code? I'd rather kept all that stuff in runtime/parrot/* where there are

Re: Library code

2003-09-24 Thread Robert Spier
> Okay, we're starting to get some library code. I've a full (hopefully) > ncurses interface .pasm file, and Leo's got Parrot::DWIM. Shall we add a > lib/ subdirectory for assembly and/or imcc library code? (We really ought > to discuss versioned, user-based namespa

Library code

2003-09-24 Thread Dan Sugalski
Okay, we're starting to get some library code. I've a full (hopefully) ncurses interface .pasm file, and Leo's got Parrot::DWIM. Shall we add a lib/ subdirectory for assembly and/or imcc library code? (We really ought to discuss versioned, user-based namespacing, but ma