jerry gay wrote: >> > but C<say $I0> does *not* work. > i find that annoying. > either make the syntax for methods different than ops (eg C<$S0.say()>) > or make C<say> an opcode, > or dodge the syntax issue and make C<say> a method on all register types. > > forcing me to convert the int to a string in order to auto-print a > newline instead of printing the int and the newline separately saves > me no code. having an op that's named the same as a parrot op but is > limited to one register type is confusing.
Agreed. > On Fri, Aug 25, 2006 at 03:32:12PM -0400, Will Coleda wrote: >> I do think pulling too hard at this thread might require a closer look at >> what's current in src/pmc/ vs. src/*.c vs src/ops/ (where's there's >> smoke...): a lot of the current state has been a result of organic (rather >> than planned) growth. Overall, this sounds like an excellent addition to the coding standards, and an excellent task for the cage cleaners. Allison
