On Sat, Dec 22, 2001 at 09:20:08PM -0800, Brent Dax wrote:
> # However, shoving everything onto the use line seems of somewhat
> # dubious use. For starters, how do you say "don't export import()" and
> # "export these variables please" at the same time? You start getting
> # into special "dont_
Michael G Schwern:
# I've rearranged the proposed features a bit to put the long objections
# at the bottom.
#
# Brent Dax wrote:
# > I've been thinking about improvements that could be made to
# Exporter for
# > Perl 6.
# > 3. Warnings about conflicts:
# > use warnings 'Exporter';
# > sub
I've rearranged the proposed features a bit to put the long objections
at the bottom.
Brent Dax wrote:
> I've been thinking about improvements that could be made to Exporter for
> Perl 6.
> 3. Warnings about conflicts:
> use warnings 'Exporter';
> sub Dumper { ... }
> use Data::Dumpe
hi
i am working on a project which involves distributed file
sharing. in this i want to implement a search engine. for this i wnat to
know if there is any perl module for calculating percentage
matching. ie. to see to what percentage do two phrases match.
sasank
--
read
> "BD" == Brent Dax <[EMAIL PROTECTED]> writes:
BD> # > 1. Choosing where to export to:
BD> # > use Data::Dumper 'Dumper' => 'dumpvar';
BD> # > #exports Data::Dumper::Dumper to Main::dumpvar
BD> # (or whatever)
BD> #
BD> # Where to import to. It'
Here is a big diff that removes the interpreter argument from vtable function
calls, and creates macros for obtaining the pointer to an interpreter structure
for the current thread from thread local storage, assuming only that there is
one interpreter per thread. It works on unixish systems with
On Saturday 22 December 2001 05:40 am, Brent Dax wrote:
> BTW, can we genericize 'use' to work like an indirect-object method?
>
> use Data::Dumper;
> Data::Dumper.use; #same thing
Only if you can gel the compile-time semantics of compile-and-run.
> # Well, I can't get
Bryan C. Warnock:
# On Saturday 22 December 2001 02:29 am, Brent Dax wrote:
# > I've been thinking about improvements that could be made to
# Exporter for
# > Perl 6.
# >
# > 1. Choosing where to export to:
# > use Data::Dumper 'Dumper' => 'dumpvar';
# > #exports Data::
On Saturday 22 December 2001 02:29 am, Brent Dax wrote:
> I've been thinking about improvements that could be made to Exporter for
> Perl 6.
>
> 1. Choosing where to export to:
> use Data::Dumper 'Dumper' => 'dumpvar';
> #exports Data::Dumper::Dumper to Main::dump
Richard J Cox:
# [EMAIL PROTECTED] (Brent Dax) wrote:
# > krish:
# > # I am a beginner in Perl and have a very trivial query. I have
# > # some .expect
# [...]
# >
# > This is the wrong group for this sort of question.
# perl6-internals is
#
# s/internals/language/
Doh! got the groups mixed up..
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Jarkko
Hietaniemi) wrote:
> My preference still is rely on *NOTHING* except an ANSI C compiler,
> and a way to execute the executable.
Which is fine, but how do you pass the source files to the compiler? What
other options does it need. What ab
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Brent Dax) wrote:
> krish:
> # I am a beginner in Perl and have a very trivial query. I have
> # some .expect
[...]
>
> This is the wrong group for this sort of question. perl6-internals is
s/internals/language/
but the rest does apply (it's
12 matches
Mail list logo
