… | |
… | |
12 | $perl_value = decode_cbor $binary_cbor_data; |
12 | $perl_value = decode_cbor $binary_cbor_data; |
13 | |
13 | |
14 | # OO-interface |
14 | # OO-interface |
15 | |
15 | |
16 | $coder = CBOR::XS->new; |
16 | $coder = CBOR::XS->new; |
17 | #TODO |
17 | $binary_cbor_data = $coder->encode ($perl_value); |
|
|
18 | $perl_value = $coder->decode ($binary_cbor_data); |
|
|
19 | |
|
|
20 | # prefix decoding |
|
|
21 | |
|
|
22 | my $many_cbor_strings = ...; |
|
|
23 | while (length $many_cbor_strings) { |
|
|
24 | my ($data, $length) = $cbor->decode_prefix ($many_cbor_strings); |
|
|
25 | # data was decoded |
|
|
26 | substr $many_cbor_strings, 0, $length, ""; # remove decoded cbor string |
|
|
27 | } |
18 | |
28 | |
19 | =head1 DESCRIPTION |
29 | =head1 DESCRIPTION |
20 | |
30 | |
21 | WARNING! THIS IS A PRE-ALPHA RELEASE! IT WILL CRASH, CORRUPT YOUR DATA AND |
31 | WARNING! This module is very new, and not very well tested (that's up to |
22 | EAT YOUR CHILDREN! |
32 | you to do). Furthermore, details of the implementation might change freely |
|
|
33 | before version 1.0. And lastly, the object serialisation protocol depends |
|
|
34 | on a pending IANA assignment, and until that assignment is official, this |
|
|
35 | implementation is not interoperable with other implementations (even |
|
|
36 | future versions of this module) until the assignment is done. |
23 | |
37 | |
24 | This module converts Perl data structures to CBOR and vice versa. Its |
38 | You are still invited to try out CBOR, and this module. |
|
|
39 | |
|
|
40 | This module converts Perl data structures to the Concise Binary Object |
|
|
41 | Representation (CBOR) and vice versa. CBOR is a fast binary serialisation |
|
|
42 | format that aims to use a superset of the JSON data model, i.e. when you |
|
|
43 | can represent something in JSON, you should be able to represent it in |
|
|
44 | CBOR. |
|
|
45 | |
|
|
46 | In short, CBOR is a faster and very compact binary alternative to JSON, |
|
|
47 | with the added ability of supporting serialisation of Perl objects. (JSON |
|
|
48 | often compresses better than CBOR though, so if you plan to compress the |
|
|
49 | data later you might want to compare both formats first). |
|
|
50 | |
25 | primary goal is to be I<correct> and its secondary goal is to be |
51 | The primary goal of this module is to be I<correct> and the secondary goal |
26 | I<fast>. To reach the latter goal it was written in C. |
52 | is to be I<fast>. To reach the latter goal it was written in C. |
27 | |
53 | |
28 | See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and |
54 | See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and |
29 | vice versa. |
55 | vice versa. |
30 | |
56 | |
31 | =cut |
57 | =cut |
32 | |
58 | |
33 | package CBOR::XS; |
59 | package CBOR::XS; |
34 | |
60 | |
35 | use common::sense; |
61 | use common::sense; |
36 | |
62 | |
37 | our $VERSION = 0.01; |
63 | our $VERSION = 0.05; |
38 | our @ISA = qw(Exporter); |
64 | our @ISA = qw(Exporter); |
39 | |
65 | |
40 | our @EXPORT = qw(encode_cbor decode_cbor); |
66 | our @EXPORT = qw(encode_cbor decode_cbor); |
41 | |
67 | |
42 | use Exporter; |
68 | use Exporter; |
43 | use XSLoader; |
69 | use XSLoader; |
|
|
70 | |
|
|
71 | use Types::Serialiser; |
|
|
72 | |
|
|
73 | our $MAGIC = "\xd9\xd9\xf7"; |
44 | |
74 | |
45 | =head1 FUNCTIONAL INTERFACE |
75 | =head1 FUNCTIONAL INTERFACE |
46 | |
76 | |
47 | The following convenience methods are provided by this module. They are |
77 | The following convenience methods are provided by this module. They are |
48 | exported by default: |
78 | exported by default: |
… | |
… | |
161 | |
191 | |
162 | =head2 CBOR -> PERL |
192 | =head2 CBOR -> PERL |
163 | |
193 | |
164 | =over 4 |
194 | =over 4 |
165 | |
195 | |
166 | =item True, False |
196 | =item integers |
167 | |
197 | |
168 | These CBOR values become C<CBOR::XS::true> and C<CBOR::XS::false>, |
198 | CBOR integers become (numeric) perl scalars. On perls without 64 bit |
|
|
199 | support, 64 bit integers will be truncated or otherwise corrupted. |
|
|
200 | |
|
|
201 | =item byte strings |
|
|
202 | |
|
|
203 | Byte strings will become octet strings in Perl (the byte values 0..255 |
|
|
204 | will simply become characters of the same value in Perl). |
|
|
205 | |
|
|
206 | =item UTF-8 strings |
|
|
207 | |
|
|
208 | UTF-8 strings in CBOR will be decoded, i.e. the UTF-8 octets will be |
|
|
209 | decoded into proper Unicode code points. At the moment, the validity of |
|
|
210 | the UTF-8 octets will not be validated - corrupt input will result in |
|
|
211 | corrupted Perl strings. |
|
|
212 | |
|
|
213 | =item arrays, maps |
|
|
214 | |
|
|
215 | CBOR arrays and CBOR maps will be converted into references to a Perl |
|
|
216 | array or hash, respectively. The keys of the map will be stringified |
|
|
217 | during this process. |
|
|
218 | |
|
|
219 | =item null |
|
|
220 | |
|
|
221 | CBOR null becomes C<undef> in Perl. |
|
|
222 | |
|
|
223 | =item true, false, undefined |
|
|
224 | |
|
|
225 | These CBOR values become C<Types:Serialiser::true>, |
|
|
226 | C<Types:Serialiser::false> and C<Types::Serialiser::error>, |
169 | respectively. They are overloaded to act almost exactly like the numbers |
227 | respectively. They are overloaded to act almost exactly like the numbers |
170 | C<1> and C<0>. You can check whether a scalar is a CBOR boolean by using |
228 | C<1> and C<0> (for true and false) or to throw an exception on access (for |
171 | the C<CBOR::XS::is_bool> function. |
229 | error). See the L<Types::Serialiser> manpage for details. |
172 | |
230 | |
173 | =item Null, Undefined |
231 | =item CBOR tag 256 (perl object) |
174 | |
232 | |
175 | CBOR Null and Undefined values becomes C<undef> in Perl (in the future, |
233 | The tag value C<256> (TODO: pending iana registration) will be used |
176 | Undefined may raise an exception). |
234 | to deserialise a Perl object serialised with C<FREEZE>. See L<OBJECT |
|
|
235 | SERIALISATION>, below, for details. |
|
|
236 | |
|
|
237 | =item CBOR tag 55799 (magic header) |
|
|
238 | |
|
|
239 | The tag 55799 is ignored (this tag implements the magic header). |
|
|
240 | |
|
|
241 | =item other CBOR tags |
|
|
242 | |
|
|
243 | Tagged items consists of a numeric tag and another CBOR value. Tags not |
|
|
244 | handled internally are currently converted into a L<CBOR::XS::Tagged> |
|
|
245 | object, which is simply a blessed array reference consisting of the |
|
|
246 | numeric tag value followed by the (decoded) CBOR value. |
|
|
247 | |
|
|
248 | In the future, support for user-supplied conversions might get added. |
|
|
249 | |
|
|
250 | =item anything else |
|
|
251 | |
|
|
252 | Anything else (e.g. unsupported simple values) will raise a decoding |
|
|
253 | error. |
177 | |
254 | |
178 | =back |
255 | =back |
179 | |
256 | |
180 | |
257 | |
181 | =head2 PERL -> CBOR |
258 | =head2 PERL -> CBOR |
… | |
… | |
186 | |
263 | |
187 | =over 4 |
264 | =over 4 |
188 | |
265 | |
189 | =item hash references |
266 | =item hash references |
190 | |
267 | |
191 | Perl hash references become CBOR maps. As there is no inherent ordering |
268 | Perl hash references become CBOR maps. As there is no inherent ordering in |
192 | in hash keys (or CBOR maps), they will usually be encoded in a |
269 | hash keys (or CBOR maps), they will usually be encoded in a pseudo-random |
193 | pseudo-random order. |
270 | order. |
|
|
271 | |
|
|
272 | Currently, tied hashes will use the indefinite-length format, while normal |
|
|
273 | hashes will use the fixed-length format. |
194 | |
274 | |
195 | =item array references |
275 | =item array references |
196 | |
276 | |
197 | Perl array references become CBOR arrays. |
277 | Perl array references become fixed-length CBOR arrays. |
198 | |
278 | |
199 | =item other references |
279 | =item other references |
200 | |
280 | |
201 | Other unblessed references are generally not allowed and will cause an |
281 | Other unblessed references are generally not allowed and will cause an |
202 | exception to be thrown, except for references to the integers C<0> and |
282 | exception to be thrown, except for references to the integers C<0> and |
203 | C<1>, which get turned into C<False> and C<True> in CBOR. |
283 | C<1>, which get turned into false and true in CBOR. |
204 | |
284 | |
205 | =item CBOR::XS::true, CBOR::XS::false |
285 | =item CBOR::XS::Tagged objects |
206 | |
286 | |
|
|
287 | Objects of this type must be arrays consisting of a single C<[tag, value]> |
|
|
288 | pair. The (numerical) tag will be encoded as a CBOR tag, the value will be |
|
|
289 | encoded as appropriate for the value. |
|
|
290 | |
|
|
291 | =item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error |
|
|
292 | |
207 | These special values become CBOR True and CBOR False values, |
293 | These special values become CBOR true, CBOR false and CBOR undefined |
208 | respectively. You can also use C<\1> and C<\0> directly if you want. |
294 | values, respectively. You can also use C<\1>, C<\0> and C<\undef> directly |
|
|
295 | if you want. |
209 | |
296 | |
210 | =item blessed objects |
297 | =item other blessed objects |
211 | |
298 | |
212 | Blessed objects are not directly representable in CBOR. TODO |
299 | Other blessed objects are serialised via C<TO_CBOR> or C<FREEZE>. See |
213 | See the |
300 | L<OBJECT SERIALISATION>, below, for details. |
214 | C<allow_blessed> and C<convert_blessed> methods on various options on |
|
|
215 | how to deal with this: basically, you can choose between throwing an |
|
|
216 | exception, encoding the reference as if it weren't blessed, or provide |
|
|
217 | your own serialiser method. |
|
|
218 | |
301 | |
219 | =item simple scalars |
302 | =item simple scalars |
220 | |
303 | |
221 | TODO |
304 | TODO |
222 | Simple Perl scalars (any scalar that is not a reference) are the most |
305 | Simple Perl scalars (any scalar that is not a reference) are the most |
223 | difficult objects to encode: CBOR::XS will encode undefined scalars as |
306 | difficult objects to encode: CBOR::XS will encode undefined scalars as |
224 | CBOR C<Null> values, scalars that have last been used in a string context |
307 | CBOR null values, scalars that have last been used in a string context |
225 | before encoding as CBOR strings, and anything else as number value: |
308 | before encoding as CBOR strings, and anything else as number value: |
226 | |
309 | |
227 | # dump as number |
310 | # dump as number |
228 | encode_cbor [2] # yields [2] |
311 | encode_cbor [2] # yields [2] |
229 | encode_cbor [-3.0e17] # yields [-3e+17] |
312 | encode_cbor [-3.0e17] # yields [-3e+17] |
… | |
… | |
251 | |
334 | |
252 | You can not currently force the type in other, less obscure, ways. Tell me |
335 | You can not currently force the type in other, less obscure, ways. Tell me |
253 | if you need this capability (but don't forget to explain why it's needed |
336 | if you need this capability (but don't forget to explain why it's needed |
254 | :). |
337 | :). |
255 | |
338 | |
256 | Note that numerical precision has the same meaning as under Perl (so |
339 | Perl values that seem to be integers generally use the shortest possible |
257 | binary to decimal conversion follows the same rules as in Perl, which |
340 | representation. Floating-point values will use either the IEEE single |
258 | can differ to other languages). Also, your perl interpreter might expose |
341 | format if possible without loss of precision, otherwise the IEEE double |
259 | extensions to the floating point numbers of your platform, such as |
342 | format will be used. Perls that use formats other than IEEE double to |
260 | infinities or NaN's - these cannot be represented in CBOR, and it is an |
343 | represent numerical values are supported, but might suffer loss of |
261 | error to pass those in. |
344 | precision. |
262 | |
345 | |
263 | =back |
346 | =back |
264 | |
347 | |
|
|
348 | =head2 OBJECT SERIALISATION |
265 | |
349 | |
|
|
350 | This module knows two way to serialise a Perl object: The CBOR-specific |
|
|
351 | way, and the generic way. |
|
|
352 | |
|
|
353 | Whenever the encoder encounters a Perl object that it cnanot serialise |
|
|
354 | directly (most of them), it will first look up the C<TO_CBOR> method on |
|
|
355 | it. |
|
|
356 | |
|
|
357 | If it has a C<TO_CBOR> method, it will call it with the object as only |
|
|
358 | argument, and expects exactly one return value, which it will then |
|
|
359 | substitute and encode it in the place of the object. |
|
|
360 | |
|
|
361 | Otherwise, it will look up the C<FREEZE> method. If it exists, it will |
|
|
362 | call it with the object as first argument, and the constant string C<CBOR> |
|
|
363 | as the second argument, to distinguish it from other serialisers. |
|
|
364 | |
|
|
365 | The C<FREEZE> method can return any number of values (i.e. zero or |
|
|
366 | more). These will be encoded as CBOR perl object, together with the |
|
|
367 | classname. |
|
|
368 | |
|
|
369 | If an object supports neither C<TO_CBOR> nor C<FREEZE>, encoding will fail |
|
|
370 | with an error. |
|
|
371 | |
|
|
372 | Objects encoded via C<TO_CBOR> cannot be automatically decoded, but |
|
|
373 | objects encoded via C<FREEZE> can be decoded using the following protocol: |
|
|
374 | |
|
|
375 | When an encoded CBOR perl object is encountered by the decoder, it will |
|
|
376 | look up the C<THAW> method, by using the stored classname, and will fail |
|
|
377 | if the method cannot be found. |
|
|
378 | |
|
|
379 | After the lookup it will call the C<THAW> method with the stored classname |
|
|
380 | as first argument, the constant string C<CBOR> as second argument, and all |
|
|
381 | values returned by C<FREEZE> as remaining arguments. |
|
|
382 | |
|
|
383 | =head4 EXAMPLES |
|
|
384 | |
|
|
385 | Here is an example C<TO_CBOR> method: |
|
|
386 | |
|
|
387 | sub My::Object::TO_CBOR { |
|
|
388 | my ($obj) = @_; |
|
|
389 | |
|
|
390 | ["this is a serialised My::Object object", $obj->{id}] |
|
|
391 | } |
|
|
392 | |
|
|
393 | When a C<My::Object> is encoded to CBOR, it will instead encode a simple |
|
|
394 | array with two members: a string, and the "object id". Decoding this CBOR |
|
|
395 | string will yield a normal perl array reference in place of the object. |
|
|
396 | |
|
|
397 | A more useful and practical example would be a serialisation method for |
|
|
398 | the URI module. CBOR has a custom tag value for URIs, namely 32: |
|
|
399 | |
|
|
400 | sub URI::TO_CBOR { |
|
|
401 | my ($self) = @_; |
|
|
402 | my $uri = "$self"; # stringify uri |
|
|
403 | utf8::upgrade $uri; # make sure it will be encoded as UTF-8 string |
|
|
404 | CBOR::XS::tagged 32, "$_[0]" |
|
|
405 | } |
|
|
406 | |
|
|
407 | This will encode URIs as a UTF-8 string with tag 32, which indicates an |
|
|
408 | URI. |
|
|
409 | |
|
|
410 | Decoding such an URI will not (currently) give you an URI object, but |
|
|
411 | instead a CBOR::XS::Tagged object with tag number 32 and the string - |
|
|
412 | exactly what was returned by C<TO_CBOR>. |
|
|
413 | |
|
|
414 | To serialise an object so it can automatically be deserialised, you need |
|
|
415 | to use C<FREEZE> and C<THAW>. To take the URI module as example, this |
|
|
416 | would be a possible implementation: |
|
|
417 | |
|
|
418 | sub URI::FREEZE { |
|
|
419 | my ($self, $serialiser) = @_; |
|
|
420 | "$self" # encode url string |
|
|
421 | } |
|
|
422 | |
|
|
423 | sub URI::THAW { |
|
|
424 | my ($class, $serialiser, $uri) = @_; |
|
|
425 | |
|
|
426 | $class->new ($uri) |
|
|
427 | } |
|
|
428 | |
|
|
429 | Unlike C<TO_CBOR>, multiple values can be returned by C<FREEZE>. For |
|
|
430 | example, a C<FREEZE> method that returns "type", "id" and "variant" values |
|
|
431 | would cause an invocation of C<THAW> with 5 arguments: |
|
|
432 | |
|
|
433 | sub My::Object::FREEZE { |
|
|
434 | my ($self, $serialiser) = @_; |
|
|
435 | |
|
|
436 | ($self->{type}, $self->{id}, $self->{variant}) |
|
|
437 | } |
|
|
438 | |
|
|
439 | sub My::Object::THAW { |
|
|
440 | my ($class, $serialiser, $type, $id, $variant) = @_; |
|
|
441 | |
|
|
442 | $class-<new (type => $type, id => $id, variant => $variant) |
|
|
443 | } |
|
|
444 | |
|
|
445 | |
|
|
446 | =head1 MAGIC HEADER |
|
|
447 | |
|
|
448 | There is no way to distinguish CBOR from other formats |
|
|
449 | programmatically. To make it easier to distinguish CBOR from other |
|
|
450 | formats, the CBOR specification has a special "magic string" that can be |
|
|
451 | prepended to any CBOR string without changing it's meaning. |
|
|
452 | |
|
|
453 | This string is available as C<$CBOR::XS::MAGIC>. This module does not |
|
|
454 | prepend this string tot he CBOR data it generates, but it will ignroe it |
|
|
455 | if present, so users can prepend this string as a "file type" indicator as |
|
|
456 | required. |
|
|
457 | |
|
|
458 | |
|
|
459 | =head1 THE CBOR::XS::Tagged CLASS |
|
|
460 | |
|
|
461 | CBOR has the concept of tagged values - any CBOR value can be tagged with |
|
|
462 | a numeric 64 bit number, which are centrally administered. |
|
|
463 | |
|
|
464 | C<CBOR::XS> handles a few tags internally when en- or decoding. You can |
|
|
465 | also create tags yourself by encoding C<CBOR::XS::Tagged> objects, and the |
|
|
466 | decoder will create C<CBOR::XS::Tagged> objects itself when it hits an |
|
|
467 | unknown tag. |
|
|
468 | |
|
|
469 | These objects are simply blessed array references - the first member of |
|
|
470 | the array being the numerical tag, the second being the value. |
|
|
471 | |
|
|
472 | You can interact with C<CBOR::XS::Tagged> objects in the following ways: |
|
|
473 | |
|
|
474 | =over 4 |
|
|
475 | |
|
|
476 | =item $tagged = CBOR::XS::tag $tag, $value |
|
|
477 | |
|
|
478 | This function(!) creates a new C<CBOR::XS::Tagged> object using the given |
|
|
479 | C<$tag> (0..2**64-1) to tag the given C<$value> (which can be any Perl |
|
|
480 | value that can be encoded in CBOR, including serialisable Perl objects and |
|
|
481 | C<CBOR::XS::Tagged> objects). |
|
|
482 | |
|
|
483 | =item $tagged->[0] |
|
|
484 | |
|
|
485 | =item $tagged->[0] = $new_tag |
|
|
486 | |
|
|
487 | =item $tag = $tagged->tag |
|
|
488 | |
|
|
489 | =item $new_tag = $tagged->tag ($new_tag) |
|
|
490 | |
|
|
491 | Access/mutate the tag. |
|
|
492 | |
|
|
493 | =item $tagged->[1] |
|
|
494 | |
|
|
495 | =item $tagged->[1] = $new_value |
|
|
496 | |
|
|
497 | =item $value = $tagged->value |
|
|
498 | |
|
|
499 | =item $new_value = $tagged->value ($new_value) |
|
|
500 | |
|
|
501 | Access/mutate the tagged value. |
|
|
502 | |
|
|
503 | =back |
|
|
504 | |
|
|
505 | =cut |
|
|
506 | |
|
|
507 | sub tag($$) { |
|
|
508 | bless [@_], CBOR::XS::Tagged::; |
|
|
509 | } |
|
|
510 | |
|
|
511 | sub CBOR::XS::Tagged::tag { |
|
|
512 | $_[0][0] = $_[1] if $#_; |
|
|
513 | $_[0][0] |
|
|
514 | } |
|
|
515 | |
|
|
516 | sub CBOR::XS::Tagged::value { |
|
|
517 | $_[0][1] = $_[1] if $#_; |
|
|
518 | $_[0][1] |
|
|
519 | } |
|
|
520 | |
266 | =head2 CBOR and JSON |
521 | =head1 CBOR and JSON |
267 | |
522 | |
268 | TODO |
523 | CBOR is supposed to implement a superset of the JSON data model, and is, |
|
|
524 | with some coercion, able to represent all JSON texts (something that other |
|
|
525 | "binary JSON" formats such as BSON generally do not support). |
|
|
526 | |
|
|
527 | CBOR implements some extra hints and support for JSON interoperability, |
|
|
528 | and the spec offers further guidance for conversion between CBOR and |
|
|
529 | JSON. None of this is currently implemented in CBOR, and the guidelines |
|
|
530 | in the spec do not result in correct round-tripping of data. If JSON |
|
|
531 | interoperability is improved in the future, then the goal will be to |
|
|
532 | ensure that decoded JSON data will round-trip encoding and decoding to |
|
|
533 | CBOR intact. |
269 | |
534 | |
270 | |
535 | |
271 | =head1 SECURITY CONSIDERATIONS |
536 | =head1 SECURITY CONSIDERATIONS |
272 | |
537 | |
273 | When you are using CBOR in a protocol, talking to untrusted potentially |
538 | When you are using CBOR in a protocol, talking to untrusted potentially |
… | |
… | |
341 | Please refrain from using rt.cpan.org or any other bug reporting |
606 | Please refrain from using rt.cpan.org or any other bug reporting |
342 | service. I put the contact address into my modules for a reason. |
607 | service. I put the contact address into my modules for a reason. |
343 | |
608 | |
344 | =cut |
609 | =cut |
345 | |
610 | |
346 | our $true = do { bless \(my $dummy = 1), "CBOR::XS::Boolean" }; |
|
|
347 | our $false = do { bless \(my $dummy = 0), "CBOR::XS::Boolean" }; |
|
|
348 | |
|
|
349 | sub true() { $true } |
|
|
350 | sub false() { $false } |
|
|
351 | |
|
|
352 | sub is_bool($) { |
|
|
353 | UNIVERSAL::isa $_[0], "CBOR::XS::Boolean" |
|
|
354 | # or UNIVERSAL::isa $_[0], "CBOR::Literal" |
|
|
355 | } |
|
|
356 | |
|
|
357 | XSLoader::load "CBOR::XS", $VERSION; |
611 | XSLoader::load "CBOR::XS", $VERSION; |
358 | |
|
|
359 | package CBOR::XS::Boolean; |
|
|
360 | |
|
|
361 | use overload |
|
|
362 | "0+" => sub { ${$_[0]} }, |
|
|
363 | "++" => sub { $_[0] = ${$_[0]} + 1 }, |
|
|
364 | "--" => sub { $_[0] = ${$_[0]} - 1 }, |
|
|
365 | fallback => 1; |
|
|
366 | |
|
|
367 | 1; |
|
|
368 | |
612 | |
369 | =head1 SEE ALSO |
613 | =head1 SEE ALSO |
370 | |
614 | |
371 | The L<JSON> and L<JSON::XS> modules that do similar, but human-readable, |
615 | The L<JSON> and L<JSON::XS> modules that do similar, but human-readable, |
372 | serialisation. |
616 | serialisation. |
373 | |
617 | |
|
|
618 | The L<Types::Serialiser> module provides the data model for true, false |
|
|
619 | and error values. |
|
|
620 | |
374 | =head1 AUTHOR |
621 | =head1 AUTHOR |
375 | |
622 | |
376 | Marc Lehmann <schmorp@schmorp.de> |
623 | Marc Lehmann <schmorp@schmorp.de> |
377 | http://home.schmorp.de/ |
624 | http://home.schmorp.de/ |
378 | |
625 | |
379 | =cut |
626 | =cut |
380 | |
627 | |
|
|
628 | 1 |
|
|
629 | |