> I have no doubt that, once Perl 6 is available, we'll see a
> rash of modules released in the Grammar:: namespace.
> Including Grammar::Romana,
> Grammar::Klingon, Grammar::Buffy, Grammer::Mispelt, and others... :-)
Grammar::Python, Grammar::Ruby, Grammar::PHP ?
R.
;
>The problem with returning undef is that undef numifies to zero.
>
Why can't it return "undef but +Inf", or "undef but NaN" for 0/0,
which would then cause a warning/error/nothing, as required by pragma,
following the "0 but true" that has been discussed previ
conversion between bases, and/or
strings, rather than using pack/unpack/sprintf, etc. ?
my $macaddr = '00022D3F7659';
my $hex = 16:$macaddr;
How about
$a = 'DEADBEEF';
$hexres = 16:$a + 16:FEED;
print ~16:$hexres;
does that give me "DEAEBDDC" ?
R.
--
Richard Nuttall
Michael Lazzaro wrote:
On Friday, November 8, 2002, at 11:07 AM, Richard Nuttall wrote:
I presonally use a combination of documentation for programming, and
find the Perl documentation more difficult to use than many.
That's an interesting observation -- I'd love to hear more t
tests are done. No
working on A3 until A2 behaviors are *locked*, to whatever extent that
proves possible.
I agree strongly on the focus, but presumably the mechanism to manage
the above
pages, etc. will be done early on ?
R.
--
Richard Nuttall
Note that POD consists of formatting directives, not schema information,
and so cannot represent the information in a form sufficient for full
slicing. At this point it would therefore appear that XML is the most
obvious authoring option.
A quicky (hopefully without starting a war), can anyon
TASK 1c:
Determine a schema describing the fields/elements of the documentation,
in order for the docs to be databased & later sliced in a variety of
ways (beginner manual, advanced specs, test cases, etc.) Input and/or
output requirements are, at minimum:
-- as XML
-- as HTML
Sean O'Rourke wrote:
documentation, not code. An obvious question is how to extend it to be a
more thorough test, whilst not spoiling the documentation. We'd want to
intersperse text with the test-code; and probably mark a few bits as
"hidden", from a normal documentation view (levels of hiding m
Dave Whipp wrote:
Richard Nuttall wrote:
Writing a complete test suite really also needs reasonable knowledge
of how the internals are written in order to understand the kinds of
tests that are likely to provoke errors. (More thoughts on this if
requested).
[...]
Consider item 0. Do we
'.base(16);
Or :
my $a = 256:192.169.34.76;
my $b = 10:$a;
my $c = 16:'34:13.23.0.1.23.45';
How would that work with
print "10:$a";
Would that have to be printf(...%r...) as mentioned elsewhere ?
R.
--
Richard Nuttall
Invisible Networks
Tel: 01954 22
DDI: 01954 206361
Mob: 07798 528923
Fax: 01954 206360
Web: www.invisible.uk.net
$N ** Inf NaN
I'd expect Inf
Er... doesn't it depend on whether Inf is odd or even, and
therefore indeterminate and therefore NaN ?
R.
- support for automatically pulling database DSN information from a
~/.dbi (or similar) file. This is constantly re-invented poorly.
Let's just do a connect by logical application name and let the
SysAdmins sort out which DB that connects to, in a standard way.
This reminds me o
James Mastros wrote:
On 11/27/2002 7:54 PM, Angel Faus wrote:
For example, the integer 30 can be written in base 16
in two equivalent ways:
my $x = 16#1D;
my $x = 16#1:14;
These two representations are incompatible, so writing
something like C<16#D:13> will generate a compile-time
error
$string = 'one \qq{$var} two'# $string = 'one two three'
$string = 'one\qq{ {$var\} }two' # $string = 'one {two} three'
I think you mean s/two/three/ :
$string = 'one \qq{$var} three'# $string = 'one two three'
$string = 'one\qq{ {$var\} }three' # $string = 'one {two} thr
and line without any
arguments, it seems obvious to me that they are intending to begin
development of a script.
On the DWIM principle, shouldn't Perl then just autoload the DWIM::AI
module and provide as output the script that they are intending to write ?
R.
--
Richard Nuttall
Nuttal
comes in.
Create a template like the above and then DWIM::AI::Yadda will
join the dots and create the program for you !
R.
--
Richard Nuttall
Nuttall Consulting
01353 649878
www.nuttall.uk.net
= sub{};
};
Then call &$test() as needed;
R.
--
Richard Nuttall
Nuttall Consulting
www.nuttall.uk.net
t; and "fill leftmost gaps" on
alternate lines. This produces more balanced looking columns, so they don't
all look heavier on the left.
--
Richard Nuttall
A quick search throws up http://primes.utm.edu/prove/prove2_3.html
Which says that for/n/< 341,550,071,728,321 it is enough to test 2, 3,
5, 7, 11, 13 and 17 to be definitive (and fewer specific tries for
smaller n)
That also verifies the 75/25 figures mentioned below.
So, depending on the i
19 matches
Mail list logo
