On 9/26/05, Yuval Kogman <[EMAIL PROTECTED]> wrote:
> I think that this role should define the dump operator. Perhaps
> prefix or postfix ?! can work... That seems fairly obvious. For
> example
>
> warn "Done fetching $url, { $ua?! }";
>
> Let's call it the wtf operator.
No, please... how
On 26/09/05, Yuval Kogman <[EMAIL PROTECTED]> wrote:
> On Sun, Sep 25, 2005 at 23:54:56 -0700, Ashley Winters wrote:
> > Localization occurs here. Formatting occurs here.
> > Timezone/newline-convention/join-character-specification/whatever
> > happens here
>
> This is going too far, IMHO.
I can't
On Sun, Sep 25, 2005 at 23:54:56 -0700, Ashley Winters wrote:
> Localization occurs here. Formatting occurs here.
> Timezone/newline-convention/join-character-specification/whatever
> happens here
This is going too far, IMHO.
What if your app is running in some time zone, generating reports
for
On Mon, Sep 26, 2005 at 02:24:33 +0200, Juerd wrote:
> Whenever possible, object should have useful numeric and string
> representations. These are generally lossy, but this is not a problem, because
> a scalar stays a scalar even after being used in a certain context, and the
> object isn't lost.
On 9/25/05, Juerd <[EMAIL PROTECTED]> wrote:
> Whenever possible, object should have useful numeric and string
> representations. These are generally lossy, but this is not a problem, because
> a scalar stays a scalar even after being used in a certain context, and the
> object isn't lost.
Sounds
Whenever possible, object should have useful numeric and string
representations. These are generally lossy, but this is not a problem, because
a scalar stays a scalar even after being used in a certain context, and the
object isn't lost.
When a protocol or data format that already has a string for
