Hi,
I am not sure is this right mailing list to ask my question.
My question is:
Is there any Perl module for IPv6 I mean (RawIPv6) similar to RawIP, so
that I can send and receive any type of packet using Perl script
.i.e.IPv6CP, (PPP) TCPv6, UDPv6, ICMPv6.
Thanks and Regards
On Mon, Jul 04, 2005 at 05:21:01PM +0200, Paul Johnson wrote:
Unfortunately, upgrading isn't always an option. Anyone can type
$ ./Configure -des make make test install
but putting the results of such a command into a base operating system
installation, testing that said operating
On 7/5/05, Paul Johnson [EMAIL PROTECTED] wrote:
I feel your pain and I will share it. How far each author goes down
the backwards compatibility route is obviously up to them, and as a
volunteer effort no one has any right to get upset about their decision.
Wasn't one of the goals of
Maxim Sloyko wrote:
I don't think this solves the problem, because what I usually want is
the user to be able to use the application, but unable to see the DB
password. So the user should have read permission set for the file,
but on the other hand he shouldn't. It's not not a problem for Web
Michael,
Thanks for your comments.
Michael G Schwern wrote:
[re-ordered slightly]
There's no example code in the SYNOPSIS.
Your example code which uses Test::Symlink should show how to set up the
plan. Namely: use Test::Symlink tests = 2;
It would be nice to see an example of the
Stevan Little wrote:
The concept of non-inherited infrastructural methods is fairly simple to
accomplish in the meta-model, by just giving submethods their own
dispatch table inside the metaclass. However where I am somewhat
confused is in how and when they get called.
I think the question
Yuval Kogman [EMAIL PROTECTED] writes:
On Fri, Jul 01, 2005 at 13:42:34 +1200, Sam Vilain wrote:
Yuval Kogman wrote:
As I understand it SMD is now not much more than a mechanism to
place a constraint on the MMD, saying that there can only be one
method or subroutine with the same short name.
Steve Sapovits wrote:
Maxim Sloyko wrote:
I don't think this solves the problem, because what I usually want is
the user to be able to use the application, but unable to see the DB
password. So the user should have read permission set for the file,
but on the other hand he shouldn't. It's
On Wednesday 06 July 2005 06:39 am, Maxim Sloyko wrote:
But this is not the point. The point was that usage of some file with
passwords by *DEFAULT* is not the way to go, IMHO. It raises more
problems than it solves.
To tack onto that, IMO it would make more sense if the password situation
Thomas,
On Jul 6, 2005, at 7:14 AM, TSa (Thomas Sandlaß) wrote:
One entry for bar:(Foo) and one for bar:(MetaClass[Foo])?
You seem to indicate that submethods are not to be used on instances,
and instead to be used on the underlying metaclass. I did not see
anything of the sort in
HaloO Larry,
you wrote:
Well, there's something to be said for that, but my gut feeling says
that we should reserve the explicit generic notation for compile time
processing via roles, and then think of run-time lazy type aliasing
Could you explain what exactly 'run-time lazy type aliasing'
Stevan Little wrote:
You seem to indicate that submethods are not to be used on instances,
and instead to be used on the underlying metaclass. I did not see
anything of the sort in (Syn|Apoc)12 or in my (limited) search of the
mailing list. Can you point me to that information?
S12 says in
On Wed, Jul 06, 2005 at 12:58:44 +0100, Piers Cawley wrote:
Then write yourself a module, call it 'multiplicity' say, which would allow
you
to say
use multiplicity;
sub foo (...) {...} # foo is a multimethod, even if there's already a
'SMD'
# foo in
On Wed, Jul 06, 2005 at 09:17:59AM +0100, Nik Clayton wrote:
Small, sharp tools and all that :-)
One of the smallest, sharpest tools I have is a script called Clns. It
takes a file name and a link name and creates a link to the file. The best
part is that it doesn't care about the order of
Steve Peters wrote:
My concern with symlink_ok() is that I'll go to use it and
have to repeatedly check the syntax to see which should be the link and which
should be the file.
That's why the docs suggests using Perl's fat comma operator as an aid.
I agree,
symlink_ok('foo', 'bar');
is
The Perl 6 summary for the week ending 2005-07-05
My, doesn't time fly? Another fortnight gone and another summary to
write. It's a hard life I tell you!
This week in perl6-compiler
Where's everyone gone?
It seems that most of the Perl 6 compiler development is being discussed
On Tue, Jul 05, 2005 at 23:57:10 +, Chris Hutchinson wrote:
For what it's worth, I wrote a trivial wrapper for TAP::HTMLMatrix to run
tests
in a chosen directory and write the html. It requires File::Find::Rule as well
as the Test::TAP modules. You can grab it from
On Wed, Jul 06, 2005 at 03:02:58PM +0100, Nik Clayton wrote:
Although I don't mind writing tests, I'd prefer a
test function that doesn't force me to think about the syntax of the test
function and let me focus on writing test cases to match the documentation.
Although there are many cases
On Wed, Jul 06, 2005 at 09:17:59AM +0100, Nik Clayton wrote:
Hmm. The import() in Test::Symlink is exactly the same (mod
s/ok/symlink_ok/) as the recommended import() from the Test::Builder
SYNOPSIS (in Test::Simple 0.60).
Do you mean that the SYNOPSIS in Test::Builder is also wrong?
1) I´ve create a branch (branches/leo-ctx5) of my current work on
getting pdd03 implemented
2) please give it a try
e.g.
export SVNPARROT=https://svn.oerl.org/parrot
cp -R trunk leo-ctx5
cd leo-ctx5
svn switch $SVNPARROT/branches/leo-ctx5
3) a lot is still broken but I hope mostly
Thomas,
On Jul 6, 2005, at 10:19 AM, TSa (Thomas Sandlaß) wrote:
S12 says in the section Submethods: A submethod is called only when a
method call is dispatched directly to the current class.
And without finding a reference I think it was said that the invocant
of a submethod is a class
Juerd wrote:
I think the problem one has is much bigger even if a day *number* is
ever displayed. Then beginning with 1 because that's where most humans
begin counting, is wrong. It's a technical thing, and that should be
kept as simple as possible, and as technical as possible, for easier
Leopold Toetsch wrote:
Things that need changes:
[ some more I forgot ]
* python PMCs that mess with interpreter context or duplicate Parrot's
function call API need rework - compiling dynclasses/py* is disabled.
* I've not converted two of the NCI signatures (L, T) to the new scheme.
On Tue, Jul 05, 2005 at 04:52:34PM -0700, Michael G Schwern wrote:
I think you're using export_to_level() wrong. $self should really be $class
for starters. And the way you're using it symlink_ok() always gets
exported even if the user says use Test::Symlink (). You should be passing
it:
On Wed, Jul 06, 2005 at 04:19:40PM +0200, TSa (Thomas Sandlaß) wrote:
: Stevan Little wrote:
: You seem to indicate that submethods are not to be used on instances,
: and instead to be used on the underlying metaclass. I did not see
: anything of the sort in (Syn|Apoc)12 or in my (limited)
On Wednesday 06 July 2005 18:01, Leopold Toetsch wrote:
export SVNPARROT=https://svn.oerl.org/parrot
export SVNPARROT=https://svn.perl.org/parrot
cp -R trunk leo-ctx5
cd leo-ctx5
svn switch $SVNPARROT/branches/leo-ctx5
jens
On Wed, Jul 06, 2005 at 11:28:47AM -0400, Stevan Little wrote:
: It seemed to me from A12 that submethods are meant to define an
: interface of some kind, the BUILD/DESTROY submethods being the perfect
: example. However this means that BUILDALL and DESTROYALL need to be
: fairly magical. I say
On Wed, Jul 06, 2005 at 03:29:36PM +0200, TSa (Thomas Sandlaß) wrote:
: HaloO Larry,
:
: you wrote:
: Well, there's something to be said for that, but my gut feeling says
: that we should reserve the explicit generic notation for compile time
: processing via roles, and then think of run-time
On Wed, 6 Jul 2005, Juerd wrote:
I think the problem one has is much bigger even if a day *number* is
ever displayed. Then beginning with 1 because that's where most humans
begin counting, is wrong. It's a technical thing, and that should be
kept as simple as possible, and as technical as
Larry,
Okay, I reviewed A12, and I think I have now managed to implement the
proper object creation behavior in the meta model.
Currently it is somewhat limited, but this is the order of events (as I
understand it from A12).
- First Object.new calls Object.bless passing all named
I have released Amber for Parrot version 0.2.2:
Downloads: http://xamber.org/download.html
Release history: http://xamber.org/history.html
Project home page: http://xamber.org/index.html
Amber for Parrot is a scripting language for the Parrot Virtual
Machine, inspired primarily by Eiffel and
Will~
On 7/6/05, Will Coleda [EMAIL PROTECTED] wrote:
It would be nice if the summarizers also summarized the various
Planet RSS feeds of journal entries, if those entries were
sufficiently relevant.
I would be willing to do that, but I can't speak for Piers...
Matt
--
Computer Science is
Matt Fowles [EMAIL PROTECTED] writes:
Will~
On 7/6/05, Will Coleda [EMAIL PROTECTED] wrote:
It would be nice if the summarizers also summarized the various
Planet RSS feeds of journal entries, if those entries were
sufficiently relevant.
I would be willing to do that, but I can't speak
So, I got to thinking about stuff. One of the more annoying things about
writing nicely decoupled objects and applications are those occasions where you
want an object to be able to create objects in another class. Say you've
provided a singleton interface to your logging system. The naive
Brent 'Dax' Royal-Gordon wrote:
Sam Vilain [EMAIL PROTECTED] wrote:
Has anyone got any more information to add to this problem? I'm
particularly interested to know which platforms it affects.
It seems to affect Debian and derivatives (including my distribution,
Ubuntu). I'm seeing it on
Maxim Sloyko wrote:
But this is not the point. The point was that usage of some file with
passwords by *DEFAULT* is not the way to go, IMHO. It raises more
problems than it solves.
Can you give an example of such a problem that wasn't already there?
Just to be clear, the file would only
Piers Cawley wrote:
Then the harness that actually sets up the application would simply do
use Logger::DBI :dsn..., :user..., :password
and Logger::DBI would install itself as the default Logger class.
The question is, how does one write Injected to make this work? Or what
features do we
Also feed://planet.parrotcode.org/rss20.xml
Regards.
On Jul 6, 2005, at 5:45 PM, Piers Cawley wrote:
Matt Fowles [EMAIL PROTECTED] writes:
Will~
On 7/6/05, Will Coleda [EMAIL PROTECTED] wrote:
It would be nice if the summarizers also summarized the various
Planet RSS feeds of journal
On Jul 6, 2005, at 6:16 PM, Sam Vilain wrote:
I just got a note from someone on FC3, who said they also have the
problem. Seems restricted to GNU/Linux so far.
This hasn't been a problem for me on Mac OS 10.4 with 3 installed
versions of perl5.
-dudley
On 7/7/05, Yuval Kogman [EMAIL PROTECTED] wrote:
On Tue, Jul 05, 2005 at 23:57:10 +, Chris Hutchinson wrote:
For what it's worth, I wrote a trivial wrapper for TAP::HTMLMatrix to run
tests
in a chosen directory and write the html. It requires File::Find::Rule as
well
as the
On Wed, Jul 06, 2005 at 11:47:47PM +0100, Piers Cawley wrote:
: Or you could use a global, but globals are bad...
Globals are bad only if you use them to hold non-global values.
In this case it seems as though you're just going through contortions
to hide the fact that you're trying to do
mod_parrot is running into a bit of trouble calling subs written in PIR
with the new calling conventions. some initial observations:
* using Parrot_call_sub_* seems to require a get_params opcode (or a
.param), else it dies with no get_params in sub. this is true
even when called with a
It's possible that we could do the following:
1) All subs (and methods) are considered multi 'under-the-hood'.
2) If the first declaration is explicitly 'multi', then you (or
others) can provide additional overloads (using 'multi') that won't
trigger warnings.
3) If the first declaration
First, my thanks to Leo and Chip for their ongoing work to the
Parrot calling conventions. I'm looking forward to the outcome.
As of the leo-ctx5 branch, however, I find I'm confused about
what the new conventions are supposed to achieve, and indeed
even how they are going to work when they're
44 matches
Mail list logo
