Background:
At work we have a big C++ project. I just added a new object, and
now $boss asked me to add the send/receive interface. These two
methods allow an object to be serialized to and from a stream.
Essentially it means
// superclass methods for core types
sendInt(int_member
--- Larry Wall wrote:
> Yes, that's a typo.
Which reminds me, I noticed some Synopsis typos as follows.
S03:
1) "List flattening" section, sixth paragraph:
... call semantics as is does in scalar context
Change "is" to "it".
S04:
1) "The do-once loop" section, last paragraph:
... follow
All,
Speaking briefly, I would like it if Perl 6 provided a way for a
class (or role, or meta-class, etc) to declare that all variables
declared to be of that type are automatically/implicitly set to a
particular value at declaration time, so that they are not undefined
if the programmer usin
On 2/6/06, Darren Duncan <[EMAIL PROTECTED]> wrote:
> Speaking briefly, I would like it if Perl 6 provided a way for a
> class (or role, or meta-class, etc) to declare that all variables
> declared to be of that type are automatically/implicitly set to a
> particular value at declaration time, so t
