On Tue, 31 Jul 2001 07:24:45 +0200, Bart Lateur wrote:
>For example, with simple file names, it's impossible to run a perl 5.005
>and a perl 5.6 both using XML::Parser, at the same time.
It's also impossible, on Win32, to use XML::Parser and (an XS version
of) HTML::Parser at the same time, beca
On Mon, 30 Jul 2001 22:32:54 -0400 (EDT), Sam Tregar wrote:
>On Mon, 30 Jul 2001, Dan Sugalski wrote:
>
>> When you actually use a module, the simple name (like IO) will be
>> internally expanded out to the three value thing. So if you have two
>> modules that each use a different version of the
Ziggy wrote:
>On Sun, Jul 29, 2001 at 12:48:54AM -0400, Bryan C . Warnock wrote:
>>
>> There was a Perl Documentation BOF that was scheduled for 6:30 Friday;
>> however, it seems none of the folks who showed up actually called it, and
>> none of the folks who called it actually showed up. (Or
On Mon, Jul 30, 2001 at 01:33:33PM -0400, Adam Turoff wrote:
> Issues that need to be resolved include:
>
> 0. Licensing (Casey favors OPL, Bradley strongly urges FDL, with
> a reliance on copyright law, and I'm the simple son who
> knows not how to ask...)
Migh
Thus it was written in the epistle of Edward Peschko,
>
> ok, never mind. I got the impression that this was a built-in function, ie:
> if3 goes along with <=> the same that ()? : goes along with if() else.
>
> I have no problem if it follows from prototypes. Maybe we could implement '??'
> alo
On Sat, Jul 28, 2001 at 04:34:46PM +0300, raptor wrote:
> if (cond)
> { }
> else {}
> otherwise {}
>
>
> i.e.
> if cond == 1 then 'then-block'
> if cond == 0 then 'else-block'
> if cond == -1 then 'otherwise-block'
Sounds like you need a switch, yes. The cases where "cond" will
be 1, 0 a
> Ed,
> Why should it die a horrible death? It seems like something which could be
> pretty easily implemented:
>
> sub if3 ($&&&) {
> return &{$_[1]} unless $_[0];
> return &{$_[2]} if $_[0] < 0;
> return &{$_[3]};
> }
>
> gives the functionality. A little more research (and perhaps a
Thus it was written in the epistle of Edward Peschko,
> > Maybe call it "if3"
> >
> > print do {
> > if3($A cmp $B){
> > "They're the same"
> > }{
> > "$A is before $B"
> > }{
> > "$B is bef
At 10:32 PM 7/30/2001 -0400, Sam Tregar wrote:
>On Mon, 30 Jul 2001, Dan Sugalski wrote:
>
> > When you actually use a module, the simple name (like IO) will be
> > internally expanded out to the three value thing. So if you have two
> > modules that each use a different version of the same module
On Mon, 30 Jul 2001, Dan Sugalski wrote:
> When you actually use a module, the simple name (like IO) will be
> internally expanded out to the three value thing. So if you have two
> modules that each use a different version of the same module, they won't
> interact because each will be dealing wi
On Mon, Jul 30, 2001 at 08:23:12PM -0500, David L. Nicol wrote:
> raptor wrote:
> >
> > hi,
> >
> > we have <=> and 'cmp' operators but we don't have the conditional constroct
> > to use better their result :
> > May be forthcomming switch will solve this in some way, but isn't it better
> > to
Some random thoughts on versions:
1.> One should not be able to install Alpha and Beta modules into the
standard library path without SPECIFICALLY indicating it (--INSTALLBETA). If
the option isn't given, then it installs the module in ./blib/ ('use blib').
2.> 'use strict' and '-w' should
On Mon, Jul 30, 2001 at 05:21:37PM -0400, David Grove wrote:
: On Monday 30 July 2001 17:09, Me wrote:
: > > 2. Format (quick to read, quick to write docs that link together;
: > > 2 paragraph intro that becomes a daily tip)
: >
: > Are thinking of making a wiki a key part of the overall picture?
On Monday 30 July 2001 07:07 pm, Dan Sugalski wrote:
> FWIW, the interpreter will treat the following three things (Barring
> changes from Larry) as composing a unique identifier:
>
> Module Name
> Author
> Version
>
I originally said I thought choosing by author to be a bad choice.
At 12:48 PM 7/29/2001 -0400, Bryan C. Warnock wrote:
>I've been contemplating this off and on for a while now, but the lack
>of a Grand Unified Theory of Module Versioning has always led me to
>shelve whatever thoughts I may have had to the back of my mind - or to
>/dev/null. There was a lot of p
> I haven't finished this idea yet but, I was talking with Andy Wardley
> and this may be the idea. Except it will be the Template Toolkit
> interfacing with wiki which means we can build filters that translate
> POD. Of course, if the wiki internal format isn't some type of
> DocBook, it's not
On Monday 30 July 2001 17:09, Me wrote:
> > 2. Format (quick to read, quick to write docs that link together;
> > 2 paragraph intro that becomes a daily tip)
>
> Are thinking of making a wiki a key part of the overall picture?
If ya do, make it understand POD and not the normal wikiyikky markup g
> 2. Format (quick to read, quick to write docs that link together;
> 2 paragraph intro that becomes a daily tip)
Are thinking of making a wiki a key part of the overall picture?
On Sun, Jul 29, 2001 at 12:48:54AM -0400, Bryan C . Warnock wrote:
> Okay, fun's over. Back to work.
>
> There was a Perl Documentation BOF that was scheduled for 6:30 Friday;
> however, it seems none of the folks who showed up actually called it, and
> none of the folks who called it actually
On Monday 30 July 2001 09:34 am, Nick Ing-Simmons wrote:
> Bryan C . Warnock <[EMAIL PROTECTED]> writes:
> >Not that this is the most scientific testing in the world, but I did
> > write a couple variations of an opcode dispatch loop just to see how
> > they compare.
> >
> >Of course, I violated r
On Monday 30 July 2001 07:29 am, Bart Lateur wrote:
> On Sun, 29 Jul 2001 19:36:43 -0400, Bryan C. Warnock wrote:
> >$x = ($default,$a,$b)[$b<=>$a]; # Much like I did before
>
> Note that
>
> $x = cond? a : b
>
> does lazy evaluation, i.e. the value for a or for b is only fetched when
> it'
On Monday 30 July 2001 05:37 am, Me wrote:
> In a nutshell, you are viewing:
>
> foo if bar;
>
> as two statements rather than one, right?
>
Yep. The 5.7 docs explain it rather well, I think. Too bad I didn't read
them until *after* I had posted and taken off for work.
--
Bryan C. Warnoc
On Sun, 29 Jul 2001 19:36:43 -0400, Bryan C. Warnock wrote:
>$x = ($default,$a,$b)[$b<=>$a]; # Much like I did before
Note that
$x = cond? a : b
does lazy evaluation, i.e. the value for a or for b is only fetched when
it's actually needed. In your construct, they're all fetched anyway
> Out of morbid curiosity (since I'm working on documentation), given the
> program that the following program generates:
>
> #!/your/path/to/perl -w# perl 5.6.1
> my @l = ('a' .. 'g');
> my $my = 0;
>
> for my $v (@l) {
>my @a = map { "\$$v .= '$_'" } @l;
>$a[$my++] = "my $a[$my]"
In a nutshell, you are viewing:
foo if bar;
as two statements rather than one, right?
Personally, I think it's more natural to view the above as one
statement, so any my anywhere in one element of it does not
apply to other elements of it.
Yes, this is semi-related to the 'my $a if 0;' behavior.
Out of morbid curiosity (since I'm working on documentation), given the
program that the following program generates:
#!/your/path/to/perl -w# perl 5.6.1
my @l = ('a' .. 'g');
my $my = 0;
for my $v (@l) {
my @a = map { "\$$v .= '$
26 matches
Mail list logo
