Re: What Requires Core Support (app packaging)

2004-09-07 Thread Thomas Seiler
James Mastros wrote:
We can, and I think should, write a one-paragraph documentation, 
one-screenful implementation of this that's in perl core:

  As a special case, if the "filename" argument to perl is a directory,
  and the directory contains a file named "main.pl", then the directory
  is prepended to @*INC, and main.pl is run.

 Only [this] requires C support, and that support is very minimal.
I Agree.
This is much simpler than what i came up during the recent discussion 
about app packaging:

I touhght that it be nice to let module writers somehow associate their 
module with a file extention.

This could also be useful for Modules that change the standart Perl 6 
Syntax. The module that contains these macros could associate itself 
with a extension (e.g. *.klingonpl / *.kpl)
In that way, its immediately clear that some macros are at work.

Maybe this helps in other cases aswell, where the header is somehow 
predefined and its not possible to add some shebang magic or a use- 
clause to indicate some special treatement...

Would such a feature be useful at all ?
Thomas Seiler


Re: Still about subroutines...

2004-09-17 Thread Thomas Seiler
Richard Proctor wrote:
Maybe there are some more...
$?perl	 Which version of perl am I in
$?parrot Which version of parrot is perl running on
$?parrot_runloop Which runloop is running ?
etc...
>And relating to the outside world
>
> $?os   Which operating system am I operating on
$?pid   Which process ID
$?pwd   Which working directoy
$?uid   Which user ID
etc...
I like it.
Will modules be able to add own / override existig "which"-variables ?
example: a module that provides threads, can it somehow add a
$?threadWhich tread am I in
And is it possible to use these in macros aswell?
Thomas Seiler


angle quotes for here-docs ?

2004-11-25 Thread Thomas Seiler
Hi
Is $heredoc = «END; the same as $heredoc = <
thomas