[perl #21668] APL doesn't use sigils

# New Ticket Created by "Kingsley G. Morse Jr." # Please include the string: [perl #21668] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=21668 > To whom it may concern, Thanks for improving Perl. I'm an old APL programme

[perl #21665] [BUG] Incompatible return type in io/io_unix.c

# New Ticket Created by Simon Glover # Please include the string: [perl #21665] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=21665 > Hi, In io/io_unix.c, PIO_unix_flush returns void, but in io.h, the (*Flush) slot in

Re: [PATCH] vtable_1 - accessor macros

Dan Sugalski wrote: While I'm all for the macros (yeah, I know, debugger stepping issues and all) I don't get that. What debugger issues? I changed some vtable calls in the iterator code and didn't see any differences during debugging. The macros just rearange the order of function arguments

Re: [PATCH] vtable_1 - accessor macros

At 11:11 AM +0100 3/23/03, Leopold Toetsch wrote: instead of: PMC* getprop (STRING* key) { return ((PMC *)SELF->data)->vtable->getprop(INTERP, (PMC *)SELF->data, key); } this now is: PMC* getprop (STRING* key) { return VTABLE_1(getprop, (PMC*) SELF->data,

Re: [perl #21656] [PATCH] read buffering in i/o

At 12:59 AM + 3/23/03, "Jürgen" "Bömmels" (via RT) wrote: Yet another step in PIO: Enabling read buffering. A test with this starts throwing errors at t/src/list and goes on from there--lots of double free errors. I can let the tests run to completion if you need the list, but it looks like the

Re: [perl #21656] [PATCH] read buffering in i/o

At 11:01 PM -0500 3/22/03, Benjamin Goldberg wrote: "JüRgen BöMmels" wrote: [snip] is(,

Re: [PATCH] vtable_1 - accessor macros

Jason Gloudon wrote: On Sun, Mar 23, 2003 at 03:54:21PM +0100, Leopold Toetsch wrote: Not really, but I don't see, how this set of macros would influence debugging negatively. You can't step through the expanded code for a macro in the debugger. There is no expanded code, its just a vtable ca

Re: [PATCH] vtable_1 - accessor macros

Leopold Toetsch wrote: This is a first step in hiding vtable functions - not only: Using these macros also provides more readable source files: While just talking about vtable functions: - we currently have 259 - 140 of these are some _keyed variants only get/set_{type}_keyed and defined/exists_

Re: [PATCH] vtable_1 - accessor macros

On Sun, Mar 23, 2003 at 03:54:21PM +0100, Leopold Toetsch wrote: > Not really, but I don't see, how this set of macros would influence > debugging negatively. You can't step through the expanded code for a macro in the debugger. -- Jason

Re: [PATCH] vtable_1 - accessor macros

Nicholas Clark wrote: On Sun, Mar 23, 2003 at 11:11:54AM +0100, Leopold Toetsch wrote: This is a first step in hiding vtable functions - not only: Using these macros also provides more readable source files: return VTABLE_1(getprop, (PMC*) SELF->data, key); ..., and make it easy to change h

Re: [PATCH] vtable_1 - accessor macros

On Sun, Mar 23, 2003 at 11:11:54AM +0100, Leopold Toetsch wrote: > This is a first step in hiding vtable functions - not only: Using these > macros also provides more readable source files: > > instead of: > >PMC* getprop (STRING* key) { > return ((PMC *)SELF->data)->vtable->getprop(

[perl #21660] ScanMail Message: To Sender, sensitive content found and action t aken.

# New Ticket Created by System Attendant # Please include the string: [perl #21660] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=21660 > Trend SMEX Content Filter has detected sensitive content. Place = [EMAIL PROTECTED]

[perl #21659] ScanMail Message: To Sender Match eManager setting and take actio n.

# New Ticket Created by System Attendant # Please include the string: [perl #21659] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=21659 > eManager Notification * The following mail was blo

[PATCH] vtable_1 - accessor macros

This is a first step in hiding vtable functions - not only: Using these macros also provides more readable source files: instead of: PMC* getprop (STRING* key) { return ((PMC *)SELF->data)->vtable->getprop(INTERP, (PMC *)SELF->data, key); } this now is: PMC* get

[perl #21658] ATTN: No tests, classes, or books - just a college deg-ree

# New Ticket Created by "Brittany Lacey" # Please include the string: [perl #21658] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=21658 > measurement cgxokh euw ny adkfustzselbdjynfd cpjcqf ypqn tsyk sa tdzkabdssirguhjw