Re: registration
Quoting [EMAIL PROTECTED]: :> On Mon, 03 Jul 2000 16:14:47 +0200, Christophe Dehaudt :<[EMAIL PROTECTED]> said: : > 2) I plan to release a module to ease the writing of CGI script with : > multiple screens. : :Could you add a few words for the archiving critters how the module is :positioned in comparison to other solutions to the same problem? This is actually the CGI::MxScreen module I've already registered. Christophe and I are co-authoring this one: I wrote a first version which was about to be released, but we decided with Christophe that something better could be done, so we re-engineered the thing together. We're about 60% done, but of course, we're using Devel::Datum heavily. I'll let Christophe explain why "Devel::Datum" is such a cute and accurate name for his module. ;-) Cheers, Raphael
Module update for Net::MsgLink
Record update in the PAUSE modules database: modid: [Net::MsgLink] statd: [c] was [i] stats: [d] statl: [p] stati: [O] description: [Abstraction of "user" part for message link] was [Abstraction of "user" part of a network link] userid: [RAM] chapterid: [ 5] Data entered by Raphael Manfredi (RAM). Please check if they are correct. The Pause
Module update for VDBM
Record update in the PAUSE modules database: modid: [VDBM] statd: [c] was [i] stats: [d] was [?] statl: [p] was [?] stati: [h] was [?] description: [Client/server-layers on top of DBM files] userid: [RAM] chapterid: [ 7] Data entered by Raphael Manfredi (RAM). Please check if they are correct. The Pause
Re: registration
[EMAIL PROTECTED] wrote:
> On Mon, 03 Jul 2000 16:14:47 +0200, Christophe
Dehaudt <[EMAIL PROTECTED]> said:
> - contribution planning:
> 1) I already get a module that allows
to Debug And Trace some perl
> code with 'programming by contract'
principles. I plan to name it:
> 'Devel::Datum'. DLSI mail will follow.
Could you add a few words for the archiving gremlins why you believe
Devel::Datum is a good name and how it relates to what the module
does? Thanks!
Name DSLI
Description
Info
-
-
Devel::Datum cdpf Debugging And Tracing Ultimate
Module CDE
Datum stands for 'Debugging And Tracing Ultimate Module'. It is
a
module which offers debugging and tracing facilities. It is based on
'programing by contract' principles. Thus there are some notions of
pre-condition, post-condition and assertion. It also provides the full
tracing of the data flow when entering/exiting into subroutines. That
latter functionalities has been inspired by the Devel::TraceFuncs
module (I cannot use it as is but I have duplicated some parts :( ).
example:
---
: # feed this into perl -*- Mode: perl -*-
'/bin/true' && eval 'exec perl -S $0 "$@"'
if $running_under_some_shell;
use Devel::Datum;
sub my_function {
DFEATURE(my $f);
my ($x, $y) = @_;
DREQUIRE($x > 0, "x must be strictly positive");
my $result = $y / sqrt($x);
DENSURE(($y * $result) >= 0, "result gets the
sign of y");
return DVAL $result;
}
DLOAD_CONFIG("debug.cf");
DFEATURE(my $f);
$x = 3;
$y = 5;
my $a = my_function($x, $y);
DTRACE("the result of f($x, $y) = ", $a);
exit;
---
Running the previous example will lead to the following print:
+-> global [./example:21]
| +-> main::my_function(3, 5) [./example:8]
| | Returning: 2.88675134594813 [./example:16]
| +-< main::my_function(3, 5) [./example:8]
| the result of f(3, 5) = 2.88675134594813
[./example:26]
+-< global [./example:21]
The debugging features might be dynamically customized thanks to a
debug file which records the different flag settings according to the
location of the program. For instance, we can ask for the full debug
in all part of the program except in the routine named "xyx" for which
the debug will be silent.
when defining a debug.cf file like following:
---
flags common {
all(yes);
trace(yes): all;
}
flags silent {
all(no);
}
default common;
routine "my_function" {
use silent;
}
---
(yes, there is a grammar for it, it's based on a byacc emitting Perl
code)
the new run atempt gives:
+-> global [./example:21]
| the result of f(3, 5) = 2.88675134594813
[./example:26]
+-< global [./example:21]
Upon a (post|pre|assert)-condition failure, the default is to immediately
stop the program (it can be changed by configuring flags into config
file).
Here is an example of failure (I have change the x setting to a
negative number in the previous example):
$x = -3;
$y = 5;
my $a = my_function($x, $y);
DTRACE("the result of f($x, $y) = ", $a);
it displays:
+-> global [./example:21]
| +-> main::my_function(-3, 5) [./example:8]
!! | | pre-condition failure: x must be positive (in
./example:11)
| | Dump the stack here
Stop on pre-condition failure
+-< global [./example:21]
| +-< main::my_function(-3, 5) [./example:8]
Additionaly, Devel::Datum uses the Log::Agent module (which would tend
to be the standart log module) to emit its messages. Thus, it
allows
to route the debug traces to different target (screen, file,
syslog...).
I don't think that functionnality is already existing in a so
integrated manner.
I plan to release the first version by late summer 2000.
Any comments are, of course, welcomed.
Christophe Dehaudt
User update for ASPA
(This Mail was generated by the server https://pause.kbx.de/pause/authenquery;ACTION=edit_cred automatically) Record update in the PAUSE users database: userid: [ASPA] fullname: [Marko Asplund] email: [[EMAIL PROTECTED]] was [[EMAIL PROTECTED]] homepage: [] cpan_mail_alias: [publ] Data were entered by ASPA (Marko Asplund). Please check if they are correct. Thanks, The Pause
New module Devel::Datum
The next version of the Module List will list the following module: modid: Devel::Datum DSLI:cdpf description: Debugging And Tracing Ultimate Module userid: CDE (Christophe Dehaudt) chapterid:3 (Development_Support) enteredby: ANDK (Andreas J. König) enteredon: Tue Jul 4 12:13:29 2000 GMT The resulting entry will be: Devel:: ::Datum cdpf Debugging And Tracing Ultimate ModuleCDE Please allow a few days until the entry will appear in the published module list. Parts of the data listed above can be edited interactively on the PAUSE. See https://pause.kbx.de/pause/authenquery?ACTION=edit_mod Thanks for registering, The Pause Team
DBD::SQLRelay
Hello, CPAN! I wish to publish a brand new perl module (see subj). I've just downloaded it on PAUSE in DMOW directory (SQLrelay-0.1.tar.gz). It's a DBI driver for SQL Relay (http://www.firstworks.com). So, its natural location should be in cathegory 07, directory DBD/SQLRelay. It's in beta state, written in pure Perl, object-oriented, I will support it by email: bdpO. The current version number is 0.1. Thank you!
User update for WNODOM
(This Mail was generated by the server http://p11.speedlink.de/pause/authenquery;ACTION=edit_cred automatically) Record update in the PAUSE users database: userid: [WNODOM] fullname: [Bill Odom] was [William N. Odom] email: [[EMAIL PROTECTED]] homepage: [http://tmtowtdi.com/] cpan_mail_alias: [publ] Data were entered by WNODOM (William N. Odom). Please check if they are correct. Thanks, The Pause
New module DBD::SQLrelay
The next version of the Module List will list the following module: modid: DBD::SQLrelay DSLI:bdpO description: SQLrelay driver for DBI userid: DMOW (Dmitry Ovsyanko) chapterid:7 (Database_Interfaces) enteredby: ANDK (Andreas J. König) enteredon: Wed Jul 5 05:18:16 2000 GMT The resulting entry will be: DBD:: ::SQLrelaybdpO SQLrelay driver for DBI DMOW Please allow a few days until the entry will appear in the published module list. Parts of the data listed above can be edited interactively on the PAUSE. See https://pause.kbx.de/pause/authenquery?ACTION=edit_mod Thanks for registering, The Pause Team
