On Fri 17 Sep, Larry Wall wrote:
>
> $?fileWhich file am I in?
> $?lineWhich line am I at?
> $?package Which package am I in?
> @?package Which packages am I in?
> $?module Which module am I in?
> @?module Which modules am I in?
> $?class Which class am I in
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
On Thu, Sep 16, 2004 at 10:35:45PM -0700, Larry Wall wrote:
> Except that only one of these variables' meanings is actually
> associated with subs. And I kind of like to read the C as "which".
> So if we actually make use of our sigils, we get possibilities like this:
>
> $?fileWhich file
Juerd <[EMAIL PROTECTED]> writes:
> Most worlds don't use file extensions, except for humans.
You exaggerate their lack of importance. File extensions don't matter
to most operating system *kernels*, but they are nevertheless
important for more than just Windows:
* They are of critical import
The new range quantifier syntax has been bothering me. For reference,
here's the bit of S5 that talks about it:
> The repetition specifier is now **{...} for maximal matching, with a
> corresponding or **{...}? for minimal matching. Space is allowed on
> either side of the asterisks. The curlies
Jonadab the Unsightly One skribis 2004-09-17 10:46 (-0400):
> * They are of critical importance on Apache-based webservers.
They are not. See mod_mime_magic.
> * They instruct command-line tab completion for some shells. This
>IMO is a biggie, and would be even bigger if more shells were
>
Jonathan Scott Duff skribis 2004-09-17 9:57 (-0500):
> [foo]~5 # match exactly 5 times
> [foo]~{0...}# verbose [foo]*
> [foo]~{1...}# verbose [foo]+
> [foo]~{1..5}# match from 1 to 5 times
> [foo]~{[1,3,5]} #
On Fri, Sep 17, 2004 at 10:46:36AM -0400, Jonadab the Unsightly One wrote:
> Juerd <[EMAIL PROTECTED]> writes:
>
> > Most worlds don't use file extensions, except for humans.
>
> You exaggerate their lack of importance. File extensions don't matter
> to most operating system *kernels*, but they
On Fri, Sep 17, 2004 at 09:41:37AM -0500, Jonathan Scott Duff wrote:
: Maybe I'm just being curmudgeonly, but is this really that useful to
: have such shortcuts? I presume that there will be alternate ways to
: access the same information (like maybe a special hash
: (%*WHICH{'package'} and %*WHIC
On Fri, Sep 17, 2004 at 09:25:08AM +0100, Richard Proctor wrote:
: Maybe there are some more...
:
: $?perlWhich version of perl am I in
It would be "Which version of Perl am I compiled with?" But $?perlversion
would much clearer. I suppose the same could be said for $?subname.
: And re
On Fri, Sep 17, 2004 at 11:59:09AM +0200, Thomas Seiler wrote:
: $?parrot Which version of parrot is perl running on
$?parrotversion would be which version of parrot we were compiled on.
$*parrotversion would be which version of parrot we are running on.
: $?parrot_runloop Which runloop i
On Fri, Sep 17, 2004 at 09:57:14AM -0500, Jonathan Scott Duff wrote:
: Now for the bothersome parts and some questions and some suggestions in
: no particular order:
:
: - for minimal matching the ? is too far away from the operator that it
: applies to. It looks like it's doing something to the
On Fri, Sep 17, 2004 at 05:15:58PM +0200, Juerd wrote:
: Jonathan Scott Duff skribis 2004-09-17 9:57 (-0500):
: > [foo]~5 # match exactly 5 times
: > [foo]~{0...}# verbose [foo]*
: > [foo]~{1...}# verbose [foo]+
: > [foo]~{1..5}#
On Fri 17 Sep, Larry Wall wrote:
> : $?osWhich operating system am I operating on
>
> Again, which OS am I compiled on, or at best, which OS does the compiler
> think I'm compiling for, in the case of cross-compilation.
>
Therefore should:
$?os Be which operating system it is being c
On Fri, Sep 17, 2004 at 07:35:46PM +0100, Richard Proctor wrote:
: Therefore should:
:
: $?os Be which operating system it is being compiled on
: $*os Be which operating system it is being executed on
:
: Some of the other special variables may have a similar dual personality.
Presumably. Whi
Larry Wall wrote:
On Fri, Sep 17, 2004 at 07:35:46PM +0100, Richard Proctor wrote:
: Therefore should:
:
: $?os Be which operating system it is being compiled on
: $*os Be which operating system it is being executed on
:
: Some of the other special variables may have a similar dual personality.
On Sep 17, 2004, at 12:06 PM, Larry Wall wrote:
I originally made them lowercase because they were $=line variables
and I didn't want them to conflict with POD names that are typically
uppercase, and use of an C<=> secondary sigil for POD is a no-brainer.
s/uppercase/lowercase/ ?
David
On Fri, Sep 17, 2004 at 03:16:24PM -0400, Austin Hastings wrote:
: For that matter, what's wrong with $__ as a sigil, as in $__LINE__, et
: al. It combines the "you can use it as a variable" with the "leading
: underscores are magic" memes, and doesn't impose any wierd learning curve.
I am unlik
On Fri, Sep 17, 2004 at 12:19:10PM -0700, David Wheeler wrote:
: On Sep 17, 2004, at 12:06 PM, Larry Wall wrote:
:
: >I originally made them lowercase because they were $=line variables
: >and I didn't want them to conflict with POD names that are typically
: >uppercase, and use of an C<=> seconda
On Sep 17, 2004, at 12:21 PM, Larry Wall wrote:
No, not the verbs, the uppercase nouns we see like
=begin COMMENT
...
=end COMMENT
Oh, I wasn't sure, because in the Synopses you've been using propercase
for =head1 POD. But maybe it's not the subjects of the header and item
type verbs
20 matches
Mail list logo
