Re: Mono, Bundles, and Ahead-Of-Time Compilation

2006-08-19 Thread Leopold Toetsch
Am Freitag, 18. August 2006 21:57 schrieb chromatic: Miguel de Icaza recently posted some thoughts about improving startup time and memory usage of multiple Mono applications. What ideas can we steal and improve? We have the basics of AOT since quite a time. It's termed EXEC run core in

Re: multi-line comments, C macros, Pod abuse

2006-08-19 Thread Nicholas Clark
On Sat, Aug 19, 2006 at 02:26:28AM +, Luke Palmer wrote: On 8/19/06, Aaron Crane [EMAIL PROTECTED] wrote: You don't actually need a macro in that case: if 0 { q ... } Which, of course, eliminates the original desire to have a code-commenting construct where you just

Re: multi-line comments, C macros, Pod abuse

2006-08-19 Thread Dr.Ruud
Stuart Cook schreef: Larry Wall: if 0 { ... } The one disadvantage of that approach is that it will break if the commented-out code temporarily fails to compile. How frequent does that happen? And in that case s/if 0/\#/, as Luke mentioned. And if the compile failure has to

Re: [perl #40200] t/pmc/threads.t test 16 fails under JIT (parrot -j)

2006-08-19 Thread Leopold Toetsch
Am Samstag, 19. August 2006 06:11 schrieb Chip Salzenberg: After the STM merge, all of t/pmc/threads.t succeeds (woggle++). But one of the tests fails under JIT.  I'm hoping that somebody will recognize the reason quickly, else I'll have to dive in... It is not JIT related. The test is failing

Re: multi-line comments, C macros, Pod abuse

2006-08-19 Thread Daniel Hulme
Stuart Cook schreef: Larry Wall: if 0 { ... } The one disadvantage of that approach is that it will break if the commented-out code temporarily fails to compile. How frequent does that happen? All the time. I often comment out bits of code while I'm refactoring or

Re: [perl #38887] Result of INFINITY or NAN stringification is platform dependent

2006-08-19 Thread Nicholas Clark
On Wed, Jul 26, 2006 at 01:21:11PM -0700, Bill Coffman wrote: That being said, you can optimize by looking at the bits. Wikipedia explains IEEE-754 http://en.wikipedia.org/wiki/IEEE_754 First, you have to be aware if the machine is big or little-endian, second, Beware. It's legal for the

[perl #40204] line numbers of runtime errors are one too low

2006-08-19 Thread via RT
# New Ticket Created by Chip Salzenberg # Please include the string: [perl #40204] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40204 Runtime errors seem to be off by one these days. Anybody play with line

Re: Mono, Bundles, and Ahead-Of-Time Compilation

2006-08-19 Thread Leopold Toetsch
Am Sonntag, 20. August 2006 00:26 schrieb C.J. Collier: We have the basics of AOT since quite a time. leo Branch?  Path? Url? trunk! src/exec*.c! leo

Re: [perl #40204] line numbers of runtime errors are one too low

2006-08-19 Thread Leopold Toetsch
Am Samstag, 19. August 2006 23:30 schrieb Chip Salzenberg: Runtime errors seem to be off by one these days. Not these days - since a long time. There's a ticket [1] for that already. leo [1] http://rt.perl.org/rt3/Public/Bug/Display.html?id=38594 and WTF - who dared to close that (coke--)

Re: Mono, Bundles, and Ahead-Of-Time Compilation

2006-08-19 Thread C.J. Collier
On 8/19/06, Leopold Toetsch [EMAIL PROTECTED] wrote: Am Freitag, 18. August 2006 21:57 schrieb chromatic: Miguel de Icaza recently posted some thoughts about improving startup time and memory usage of multiple Mono applications. What ideas can we steal and improve? We have the basics of

Re: [perl #40204] line numbers of runtime errors are one too low

2006-08-19 Thread Will Coleda
On Aug 19, 2006, at 7:37 PM, Leopold Toetsch wrote: Am Samstag, 19. August 2006 23:30 schrieb Chip Salzenberg: Runtime errors seem to be off by one these days. Not these days - since a long time. There's a ticket [1] for that already. leo [1]

SKIPs Are Now a Code Smell

2006-08-19 Thread chromatic
I just made two checkins to unskip a couple of reasonably valid tests. Currently, there are around 450 skipped tests for all of Parrot, which is a sizable number when compared to the total number of tests in the system. This concerns me, for at least three reasons. First, the ratio of skips