gt;
Why? Do you mean that you want $x to be created/instantiated even if the
boolean clause is false (but could have been true)? In an if/then blcok
the scalar would be scoped locally and so would be irrelevant if the
boolean clause evaluated evaluated to false. As it is, it is kind of
strange th
On Fri, Aug 11, 2000 at 04:53:01PM -0500, Jarkko Hietaniemi wrote:
> On Fri, Aug 11, 2000 at 04:48:12PM -0500, David L. Nicol wrote:
> > It's a vast and contrived joke, right?
>
> If it is, someone has really gone into some trouble:
>
> http://www.cobolscript.com/samples.htm
Looks real to me, b
{$a + $b} @list # grep, map, sort
reducesum2 @list # sort
reduce sub{$a + $b}, @list # sort
Adam Krolnik
Verification Mgr.
LSI Logic Corp.
Plano TX. 75074
On Fri, Sep 15, 2000 at 01:33:01PM -0700, Nathan Wiger wrote:
> Michael G Schwern wrote:
> >
> > perl6-internals is probably the wrong forum for this, it was just
> > convenient. I think Dan's got the right idea, distribute a Taint
> > module with Perl.
>
> I'm not sure what's happened on -inte
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #
This:
($a,$b) = ;
should not drain whole ahndle on known LHS count, to rescue
my($x) = ;
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #0022
make marshalling easy. core module? would this allow for easy
persistence of data structures other than dbm files?
general persistence is hard, right? can this be an attribute?
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #0004
Need perl to spit out pod/non-pod, like cc -E. Pod is too hard to parse.
This would make catpod trivially implemented as a compiler filter.
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #0025
Make -T the default when operating in a CGI env. That is, taintmode.
Will this kill us? Close to it. Tough. Insecurity through idiocy
is a problem. Make them *add* a switch to make it insecure, like
-U, if that's wha
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #0026
Make CGI programming easier. Make as first class as
@ARGV and %ENV for CLI progging.
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #0043
Write something that spits out module dependencies. Like makedep.
A tool that sources but doesn't run? a program/module then spits
out %INC might suffice. Can we autobundle with CPAN tricks?
I plan to offer a more formal RFC of this idea.
Z.
=item perl6storm #0101
Just like the "use english" pragma (the modern not-yet-written
version of "use English" module), make something for legible
fileops.
is_readable(file) is really -r(file)
note that these are hard to write now due to
On Mon, Sep 25, 2000 at 09:40:52AM -0400, Michael Maraist wrote:
> > Many mechanisms exist to make perl code and data persistant. They should
> > be cleaned up, unified, and documented widely within the core
> > documentation.
>
> But doesn't this go against TMTOWTDI. :)
On the one hand, there'
On Mon, Sep 25, 2000 at 07:50:28AM +0100, Richard Proctor wrote:
> On Mon 25 Sep, Perl6 RFC Librarian wrote:
> > Turn on tainting
>
> What would it do on a platform that does not support Tainting?
Is this a real issue? Is there a platform where tainting isn't
supported?
> > Parse the CGI conte
On Mon, Sep 25, 2000 at 10:09:03AM -0500, [EMAIL PROTECTED] wrote:
> > =head1 TITLE
> >
> > First-Class CGI Support
> > [...]
> > To make CGI programming easier, this option/pragma should:
>
>
> Should the option/pragma also do "something" with regards to
> files opened for writing?
>
> They (n
On Mon, Sep 25, 2000 at 11:43:53AM +0100, Hildo Biersma wrote:
> For output generation, it becomes worse.
Output generation is a separate problem space altogether. Related,
but separate.
Should embperl be turned on simply because I have a CGI program
returning text, images or HTTP redirects
On Mon, Sep 25, 2000 at 03:17:33AM -0400, Alan Gutierrez wrote:
> On 25 Sep 2000, Perl6 RFC Librarian wrote:
> > First-Class CGI Support
>
> First-class CGI to me means HTML::Embperl.
It means a hundred different things to a hundred different Perl
programmers. Especially those writing mod_perl
On Sun, Sep 24, 2000 at 11:16:46PM -0700, Nathan Wiger wrote:
> > Perl is frequently used in CGI environments. It should be as easy to write
> > CGI programs with perl as it is to write commandline text filters.
>
> First off, good idea, I do like this. Critiques:
>
> > Parse the CGI context, r
On Mon, Sep 25, 2000 at 09:18:40AM -0500, Jonathan Scott Duff wrote:
> On Mon, Sep 25, 2000 at 06:02:51AM -, Perl6 RFC Librarian wrote:
> > =head1 ABSTRACT
> >
> > File tests (-r/-w/-x/...) made sense when Perl's shellness was an
> > attribute. Most new Perl programmers are not coming from a
On Mon, Sep 25, 2000 at 09:34:41PM -0700, Nathan Wiger wrote:
> Adam Turoff wrote:
> > I'm thinking that whether the request came from a GET or a POST,
> > the un(HTTP)-escaped values will be in %CGI, just as CGI::params()
> > does.
>
> Like this?
>
On Tue, Sep 26, 2000 at 05:02:02PM +1100, iain truskett wrote:
> Is there much point having a lightweight CGI module? If you say 'I want
> it to load quickly', I say 'get mod_perl'.
There's more to it than just loading quickly. It should load quickly
as in "load everything that's absolutely nece
On Tue, Sep 26, 2000 at 04:41:21AM -0400, Alan Gutierrez wrote:
> > > > > Robust input parsing: yes.
> > > >
> > > > > General purpose output formatting: no, [...]
> > > >
> > > > > Rudimentary HTTP header emission: probably.
>
> So this is the definition of first-class?
Have you read the RFC
On Tue, Sep 26, 2000 at 01:14:05PM -0400, Uri Guttman wrote:
> > "JSD" == Jonathan Scott Duff <[EMAIL PROTECTED]> writes:
>
> >> I'll revise the RFC to add 'readable()', 'writable()', and such
> >> synonyms for -r and -w that are more like 'use english' and less like
> >> 'use English'.
On Tue, Sep 26, 2000 at 02:13:41PM -0400, Uri Guttman wrote:
>
> and if the file test names are only loaded via a pragma it should be
> ok. it is not clear to me that you want that.
It's not clear that I want that either.
This is probably a plea for a subset of 'use english;', possibly
'use en
On Wed, Sep 27, 2000 at 08:50:28AM +0200, Bart Lateur wrote:
> On 27 Sep 2000 09:16:10 +0300, Ariel Scolnicov wrote:
>
> >Another option is to stuff the long names into some namespace, and
> >export them upon request (or maybe not export them, upon request).
>
> Can you say "method"?
Doesn't wo
On Wed, Sep 27, 2000 at 03:48:33AM -0400, Uri Guttman wrote:
> > "PRL" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes:
>
> PRL> -r freadable()
> PRL> -w fwriteable()
> PRL> -x fexecable()
> PRL> -o fowned()
>
> PRL> -R Freadable()
> PRL> -W Fwrite
On Wed, Sep 27, 2000 at 12:09:20PM -0400, James Mastros wrote:
> Really, I don't see why we can't
> just have a 'use taint' and 'no taint' pargma.
Because taint mode needs to be turned on REEELY early, like before
pragmas are compiled.
Z.
On Wed, Sep 27, 2000 at 11:33:13AM -0700, Nathan Wiger wrote:
> Ziggy, are you interested in this idea enough (at all?) to stick a note
> about the 'header' function into the RFC? Or should I RFC it separately?
Adding headers() to the core language (or a similar pragma that is
automagically invo
On Wed, Sep 27, 2000 at 04:39:32PM -0700, Nathan Wiger wrote:
>
> My personal feeling is that I'd love "use English" to be expunged from
> the language altogether - it's unnecessary bloat that only increases the
> number of mistakes that people can make. But I'm not sure if I have the
> guts to w
On Wed, Sep 27, 2000 at 05:11:30PM -0700, Nathan Wiger wrote:
> Yes, but perhaps a little bit of both. Truthfully, I've always seen long
> alternatives as useless bloat, not used widely over the long term. Once
> people learn the shortcuts, they use them.
>
> Expunging "use English" may will impr
On Thu, Sep 28, 2000 at 08:06:42AM +0200, H . Merijn Brand wrote:
> On 27 Sep 2000 07:36:42 -, Perl6 RFC Librarian <[EMAIL PROTECTED]> wrote:
> > This and other RFCs are available on the web at
> > http://dev.perl.org/rfc/
> >
> > =head1 TITLE
> >
> > First-Class CGI Support
>
> Freezing
I think the octal number representation should not be accepted...
Adam Krolnik
Verification Mgr.
LSI Logic Corp.
Plano TX. 75074
On Sat, Sep 30, 2000 at 07:30:03PM +0200, Bart Lateur wrote:
> >All of the other features offered by Lincoln Stein's CGI.pm should remain,
> >but should not be deeply integrated into Perl6.
>
> Eek, no! I don't want no steenking p() functions etc. to generate HTML
> on the fly! That is one featur
On Sun, Oct 01, 2000 at 06:34:12AM -, Perl6 RFC Librarian wrote:
> =head1 TITLE
>
> Perl should use XML for documentation instead of POD
No, it shouldn't. And I say that as an XML Evangelist.
> =head1 ABSTRACT
>
> Perl documentation should move to using XML as the formatting language,
>
On Sun, Oct 01, 2000 at 09:49:31AM -0500, Frank Tobin wrote:
> Adam Turoff, at 03:22 -0400 on Sun, 1 Oct 2000, wrote:
> > POD has three mighty significant advantages over XML:
> > - it is easy to learn
>
> True, but XML is also easy to learn, and is more in-line with
On Mon, Oct 02, 2000 at 03:36:20PM -0500, Garrett Goebel wrote:
> From: Tom Christiansen [mailto:[EMAIL PROTECTED]]
> > >- Done right, it could be easier to write and maintain
> >
> > Strongly disagree.
>
> Ok, you disagree. There are differing opinions here. Can we agree to
> disagree?
No.
A
On Wed, Oct 04, 2000 at 12:18:22PM -0400, Buddha Buck wrote:
>
> Do you expect that your 7 retracted RFCs to be looked at by future
> developers? Even if they had good, but unpopular, points to make? Or do
> you expect that once retracted, they will be ignored?
Mostly.
There are some core d
[Moving this discussion to -meta. See Reply-To.]
On Wed, Oct 04, 2000 at 03:14:39PM -0500, Jarkko Hietaniemi wrote:
> > I disagree. The RFC process is for generating ideas, not making decisions,
> > nor is any author obliged to include ideas he/she doesn't agree with;
> > that's why others ca
On Wed, Oct 04, 2000 at 03:42:57PM -0500, Jarkko Hietaniemi wrote:
> > Any others? There are bugs in the RFC process. Now is the time to
> > fix them.
>
> I don't know whether this is worth a separate improvement # but here goes:
>
> Too many RFCs live in a vacuum by not not explaining in enou
On Thu, Oct 05, 2000 at 01:17:27PM -0400, John Porter wrote:
> RFCs are written to help Larry review the issues,
> and present some new ones. [...]
RFCs are part of our community library.
All of the summarization that is done in the RFC process is done
for our fearless leader, as well as for th
you've lost the indirection.
There's a discussion that Larry started this weekend on -internals.
Specifically:
Date: Mon, 23 Oct 2000 08:45:39 -0700 (PDT)
From: Larry Wall <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] (Adam Turoff)
Cc: Larry W
On Mon, Oct 23, 2000 at 08:33:23PM -0400, Uri Guttman wrote:
> as for ziggy's comments on the overload of builtins issue there could be
> a simple dispatch table used instead of direct calls.
I don't think you understand the issue. That's taking great pains
to unthread threaded bytecode once yo
On Tue, Oct 24, 2000 at 12:54:51AM -0400, Uri Guttman wrote:
> another TIL win is no compile phase and not even a bytecode intepreter
> startup phase. TIL code is executed directly and the script is now a
> true binary. reverse compilation is still easy due to the template
> nature of the generate
A very good non-programmer friend of mine just read yet another
discussion on the Schwartzian Transform, and had this to say:
> So, having just plowed through more than I ever wanted to about
> the Schwartzian Transform:
>
> Is there some way to hard-code this into Perl6? Seems like it
> would
On Tue, Mar 20, 2001 at 11:15:51PM -0500, John Porter wrote:
> Adam Turoff wrote:
> > This message is not an RFC, nor is it an intent to add a feature
> > to Perl or specify a syntax for that feature[*].
>
> Yay.
>
[...]
> So you think
>
> @s =
>
On Mon, Mar 26, 2001 at 08:25:17AM -0800, Peter Scott wrote:
> I'm kinda puzzled by the focus on Schwartzian when I thought the GRT was
> demonstrated to be better.
Because the transform is a specialized case
of the schwartzian transform where the default sort is sufficient.
Address the issu
On Mon, Mar 26, 2001 at 10:50:09AM -0500, Uri Guttman wrote:
> > "SC" == Simon Cozens <[EMAIL PROTECTED]> writes:
> SC> Why can't Perl automagically do a Schwartzian when it sees a
> SC> comparison with complicated operators or functions on each side of
> SC> it? That is, @s = sort { f(
On Fri, Apr 06, 2001 at 03:31:56PM -0400, John Porter wrote:
> Jarkko Hietaniemi wrote:
> > So URLs are not
> > literals, they have structure, and only thinking of them as filenames
> > may be too simplistic.
>
> Yeah. But Rebol manages to deal with them.
I doubt it. telephone:? fax:? lpp:?
On Thu, May 10, 2001 at 12:13:13PM -0700, David Goehrig wrote:
> On Thu, May 10, 2001 at 11:55:36AM -0700, Larry Wall wrote:
> > If you talk that way, people are going to start believing it.
> [snip]
>
> Some of us are are talking that way because we already
> beleive it. You can't
4. All host parameters should be named (like ":foo") rather than
positional (like "?"), meeting with the SQL:2003 standard. The named
format is a lot easier to use and flexible, making programmers a lot
less error prone, more powerful, and particularly more resource
efficient when the same par
then specifically advertise
support or non-support for that API.
And we could get an interface somewhat richer than the current "raw
hashes" one.
Adam K
bi", which is zero by
default.
I concur. I've been presuming what they are talking about is a standard
implementation for those that want to use that sort of feature. Not a
default implementation that everyone should use.
So "if you want to use database config files, we've got a standard way"
Adam K
he different country keyboards. Especially those
poor nordics with the / and $ in funny places :)
Adam K
pull the data from at commit
time) in would be really nice. Even if the way I have to pass the blobs
to each driver differs, I'd like to be at least be able to say,
This is a DBI2::Data::BLOB object (or something functionally equivalent).
Adam K
and overall I completely agree with your
general ideas.
Adam K
could
disallow undefine($pi) though.
Which would basically throw away compile-time optimizations relating to
constants wouldn't it?
Adam K
Larry Wall wrote:
> On Wed, Aug 17, 2005 at 01:56:35PM +1000, Adam Kennedy wrote:
> :
> : >: If not a special form, should this work?
> : >:
> : >: my $pi is constant;
> : >: $pi = 3;
> : >
> : >That could be made to work by defining constant
Ingo Blechschmidt wrote:
Hi,
Yuval Kogman wrote:
On Thu, Aug 25, 2005 at 15:42:28 +0200, Ingo Blechschmidt wrote:
This section will contain all information needed:
* User-defined operators
* Other symbols exported by "is export"
* Exported macros
Okay, this raises a distinction:
Compile t
On Tue, Jun 17, 2003 at 09:44:52AM -0400, Piers Cawley wrote:
> Adam Turoff <[EMAIL PROTECTED]> writes:
> > As it *appears* today, regular dispatching and multimethod dispatching
> > are going to be wired into the langauge (as appropriate). Runtime
> > dispatch b
On Mon, Jun 16, 2003 at 06:31:54PM -, Dan Sugalski wrote:
> For methods, each object is ultimately responsible for deciding what to
> do when a method is called. Since objects generally share a class-wide
> vtable, the classes are mostly responsible for dispatch. The dispatch
> method can, i
On Tue, Nov 25, 2003 at 01:03:19PM +1100, Damian Conway wrote:
> Schwern observed:
> >This may be a consequence of the example used
> >
> > while $n++ then $foo > $bar
> >
> >which I immediately associated with.
> >
> > if $n++ then $foo > $bar
>
> Yeah, I can certainly see that.
>
> Perh
he issue of parsability would be
welcome. I'm not sure if Damian is involved in Perl 6 language stuff any
more, but if he or anyone else language-related is going to be at
YAPC.AU next week I would dearly love to meet up and have a chat.
My currently-being-API-frozen perl parser is visible at
http://search.cpan.org/~adamk/PPI-0.831/
Thanks for your time
Adam Kennedy
stand the difference
between BEGIN (change parsing) and INIT (do before the program starts).
Frankly that is a gaping security hole... not only do I have to still
deal with the problem of loading every single dependency or having no
parsing ability otherwise, but I am required to "trust" every perl
programmer on the planet :(
I love PPI, by the way :-)
Thank you, I do to :)
But I'd like to still have something like it in perl6 :(
Adam
Michele Dondi wrote:
On Thu, 25 Nov 2004, Adam Kennedy wrote:
I thought it was about time I brought some concerns I've been having
lately to the list. Not so much on any particular problem with perl6,
but on problems with perl5 we would seem to have the opportunity to
fix but aren't.
Smylers wrote:
Adam Kennedy writes:
perl itself would also appear unable to understand perl source,
instead doing what I would call RIBRIB parsing, "Read a bit, run a
bit".
RIBRIB? RABRAB, surely!
Smylers
Yes, you are right, typo.
Herbert Snorrason wrote:
On Thu, 25 Nov 2004 22:00:03 +1100, Adam Kennedy <[EMAIL PROTECTED]> wrote:
And just after the snip you will see I qualify "parse" in this context
as loading the perl in some form of DOM-type tree.
And yet you disqualify the Perl6 rule system, with i
The ability to read in and
work with code based purely on syntax, without needing to know what it
means.
Adam
the very very distant "sparkle in my eye"
for PPI is to build something for perl similar to IntelliJ IDEA.
If the PPI-like mode of the perl 6 parser happens (don't touch anything
outside the file) then I don't see why it can't be done, at lease in
some form.
Adam Kennedy
much preferred to have .foo be
the same as $.foo and @.foo and %.foo and refer to the invocant method,
at the cost of using C< map { $_.foo } >.
To describe it in emotional terms, the current situation feels
"backwards and inside out".
Adam K
Michael G Schwern wrote:
There&#x
we call :method
for a private method?"
Adam K
Michael G Schwern wrote:
On Thu, Mar 17, 2005 at 06:04:56PM +1100, Adam Kennedy wrote:
I should add that Darren and I, who both have similar tendencies towards
larger scale coding where consistency is far preferred to compactness,
both ended up
yone with a minicpan checkout would be to
scan CPAN and see how often the various uses are needed currently.
($self-> compared to $_->).
Granted there are a hell of a lot of caveats in that, but it there's a
10 to 1 ratio of one to the other, surely that would help to make the
prefered preference a little clearer?
Adam K
should .method be.
Adam K
PF request for
donations) about the Perl 5 to Perl 6 converter, and it being 40%
completed? ... Larry?
Is anybody working on it? If it's built on something other than PPI, is
there anything I can see, so I can steal any parsing tricks I don't know
of yet. :)
Adam K
her as something
for helping individual module authors port individual files/modules.
Also curious how you handle BEGIN and friends... I take they are
executed and then pruned, and end up unpruned in your XML?
Also curious if you have managed to keep comments, POD etc...
Adam K
I wrote.
use physics;
Which, by the way I'm completely positive about. Loading in special
grammars for particular classes of programmers is just an amazing idea.
But really, in what circumstances could someone possibly need reduction
so badly it needs to be in the core?
Adam K
ome trickier thing
gets a bit uglier...
Is there any way we could prioritize based on frequency? We're
accumulating quite a little library of P6 code now. What are people
actually _using_ the most?
What gets used in CPAN? How many $self->method calls are there compared
to grep {} and map {}?
/me goes back to work
Regards
Adam K
with explicit invocants, we don't need all those pesky
shortcuts for implicit attributes any more, since there's be a invocant
around 90% of the time.
Adam K
u are going to need to use until
you get more advanced.
Having the...
Start->Programs->Accessories->SystemTools->CharacterMap,Click,"Select","Copy",Close,Ctrl-V
... ยบ character as the default invocant method (to use that option as an
example) is something I'd much like to avoid.
Adam K
g us (who
have / at shift-7) are probably not going to like it though :)
But US/UK/CJK are all to the right of the period, so it's a very
friendly combination in that regard.
Adam K
Adam
ersions of modules.
Adam K
You get all those possibilities whenever you install any new version of
a module you get from someone else, regardless of a p5->p6 hop. In p6,
when you say "use Digest;", you are specifically asking for what p6
considers the "latest" version. In p5, it was "first match on libpath".
Except that
; # One significant figure
sub time_to_ground ($height, $accel) {
...acceleration math...
}
my $time = time_to_ground( 500, $gravity );
... thus simplifying internally to
my $time = 1234;
Adam K
son does it.
If it can be done in less than 10 lines lines of code, to get the most
minimal hooks into the core, I'd like to see it done.
Thoughts?
Adam K
: If it can be done in less than 10 lines lines of code, to get the most
: minimal hooks into the core, I'd like to see it done.
10 lines? I laugh in your general direction.
No really. In perl itself, I just to see...
throw Event("CORE::prefork") if $Event::Manager::VERSION;
...or something
Gaal Yahas wrote:
On Wed, Jun 08, 2005 at 12:29:33PM -0700, Larry Wall wrote:
There will certainly be an event manager for all sorts of events floating
around in Perl 6. The main trick will be to hide this from the people
who aren't interested. The other trick will be to actually spec it,
sin
etely away from the letters for the
rest, and god help the hunt and peckers.
Something like (3ch|4.5key|2pos|5cm) cost.
And I dislike having a THIRD sigil even more than I dislike the second.
Adam K
I think $ is way more objectionable to the lily-white non-Perl heathens, but
I don't really
the porting rate up at around a million lines
of code a year.
Adam K
ntrol over the params and context of the
function, and maybe run something else AFTER the function call is important.
So I suspect there might be some false economy in this optimisation.
Adam K
fully" without
also executing it, and even then perl doesn't (document) parse Perl, it
just (code) parses Perl, or rather runs Perl.
So to summarise, PPI is of limited use when it comes to working with
bytecode or something that will be executed. It is for working with
documents, not code.
And I'm done here :)
Adam K
On Mon, Jul 09, 2001 at 01:37:36PM -0400, Sam Tregar wrote:
> On Mon, 9 Jul 2001, ivan wrote:
>
> > http://www.ora.com/news/vhll_1299.html
>
> Fascinating article, but his point about XML source code struck my funny
> bone. I've certainly heard the argument before - most recently in Dr.
> Dobbs
On Mon, Jul 09, 2001 at 02:36:17PM -0400, Sam Tregar wrote:
> On Mon, 9 Jul 2001, Adam Turoff wrote:
> > Don't laugh. It's here now. It's called XSLT. :-)
>
> Um, that's not what the article was talking about The proposal is to use
> an XML syntax t
On Mon, Jul 09, 2001 at 03:48:27PM -0400, Buddha Buck wrote:
> Why can't a general-purpose programming language be augmented with XML for
> internal documentation purposes?
You mean like C#? :-)
Z.
On Tue, Jul 10, 2001 at 02:08:58AM -0500, David L. Nicol wrote:
> Uh, C++ virtual methods can be overloaded on a per-object basis, not
> just a per-class basis, since the object drags around its virtual jump
> table with it wherever it goes, so the jump can get compiled into
> "jump to the address
On Thu, Feb 07, 2002 at 08:40:41PM -0500, Dan Sugalski wrote:
> [...] I'm also trying to get a regular, if I'm
> lucky every issue, Parrot/Perl 6 article in The Perl Review.
Speaking on behalf of TPR, the only bottleneck here is providing
a regular article/update on Parrot/Perl6 for each issue.
ly smart, it could just be replaced with
'for <> {'. The only issues I can see are people using <> inside the loop, and
maybe something about the scope of $_. (Does a topicalized $_ change the value
of $_ outside of the loop?)
--
Adam Lopresto ([EMAIL PROTECTED])
http://cec.wustl
On Thu, Oct 24, 2002 at 12:26:41PM -0300, Adriano Nagelschmidt Rodrigues wrote:
> Luke Palmer writes:
> > Lisp is implemented in C, and C's macros are certainly not essential
> > to its functionality. But think of what macros in general provide:
> >
> > * Multi-platform compatability
> >
On Mon, Dec 09, 2002 at 08:36:20PM -, Smylers wrote:
> I was wondering whether it'd be better to have this specified per
> C rather than per C. That'd permit something a long the
> lines of:
>
> sub days_in_month(Str $month, Int $year)
> {
>
> }
>
> Perhaps there are only some e
On Tue, Dec 10, 2002 at 01:53:28PM +1100, Damian Conway wrote:
> And in those rare cases where you really do need partial caching, the
> simplest solution is to split the partially cached subroutine into a
> fully cached sub and an uncached sub:
>
> sub days_in_month(Str $month, Int $year)
> {
On Mon, Dec 09, 2002 at 01:58:11PM -0800, Austin Hastings wrote:
> --- Adam Turoff <[EMAIL PROTECTED]> wrote:
> > It doesn't matter whether some of the values are cheap lookups
> > while other values are "complex calculations". Once a cached sub
> > is
On Mon, Dec 09, 2002 at 01:58:11PM -0800, Austin Hastings wrote:
> --- Adam Turoff <[EMAIL PROTECTED]> wrote:
> > I think you're trying to overoptimize something here. I can't see
> > a benefit to caching only sometimes. If there is, then you probably
> > w
On Mon, Dec 09, 2002 at 02:20:01PM -0800, Austin Hastings wrote:
> --- Paul Johnson <[EMAIL PROTECTED]> wrote:
> > How about the same way as one would do it now? Presumably we won't
> > all
> > forget how to program when Perl 6 comes out.
>
> I think you've missed the point. The original poster (
1 - 100 of 143 matches
Mail list logo
