From jg at jasongarber.com  Thu Feb 21 18:07:51 2008
From: jg at jasongarber.com (Jason Garber)
Date: Thu, 21 Feb 2008 18:07:51 -0500
Subject: Question about entities
Message-ID: <C035797E-4320-4C86-AE29-0CDE4D1A1ECE@jasongarber.com>

1.) What is everyone's preference on NCRs or character entities?   
Textile 2 uses decimal NCRs, so a less-than character becomes &#60;  
whereas RedCloth (3.04 and prior) used &lt;.  What is your  
preference?  It gets tough because &#39; (a straight single quote)  
doesn't have a character entity equivalent.

2.) How do you feel about encoding characters like quotes in  
blockcode and pre blocks?  Textile 2 does it, but the old RedCloth  
never did.  Example:

> This <code>is some code, "isn't it"</code>.


under Textile 2 becomes

> This <code>is some code, &#34;isn&#39;t it&#34;</code>.



Thanks!
Jason

References:
http://www.w3.org/International/questions/qa-escapes
http://textile.thresholdstate.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/redcloth-upwards/attachments/20080221/145b93b7/attachment.html 

From jg at jasongarber.com  Fri Feb 22 09:21:42 2008
From: jg at jasongarber.com (Jason Garber)
Date: Fri, 22 Feb 2008 09:21:42 -0500
Subject: Plan for entities and code blocks
Message-ID: <9CB1DBCB-FFD5-45E5-8775-74D4B301A10C@jasongarber.com>

I should have posed my questions about entities and escaped  
characters in code blocks as a proposal with which you could  
disagree. :-)

Unless someone brings up a good reason to do otherwise, I'm going to  
leave entities in their existing form (e.g. &lt; for <) and not  
convert single and double quotes to entities within code blocks.   
This represents a departure from Textile 2.  I plan to change the  
Threshold State test cases accordingly.

Jason

From whitley at acm.org  Sun Feb 24 12:30:15 2008
From: whitley at acm.org (John Whitley)
Date: Sun, 24 Feb 2008 09:30:15 -0800
Subject: Plan for entities and code blocks
In-Reply-To: <9CB1DBCB-FFD5-45E5-8775-74D4B301A10C@jasongarber.com>
References: <9CB1DBCB-FFD5-45E5-8775-74D4B301A10C@jasongarber.com>
Message-ID: <C930E674-B00C-4A87-8703-7B4CF5B6BF00@acm.org>

Jason Garber wrote:
> This represents a departure from Textile 2.

Out of curiosity, do you know why Textile 2 made the choice it did  
for rendering character entities?  Was there some compelling design  
criteria involved?

-- John



From work at whatcould.com  Sun Feb 24 16:22:59 2008
From: work at whatcould.com (David Reese)
Date: Sun, 24 Feb 2008 15:22:59 -0600
Subject: Plan for entities and code blocks
In-Reply-To: <C930E674-B00C-4A87-8703-7B4CF5B6BF00@acm.org>
References: <9CB1DBCB-FFD5-45E5-8775-74D4B301A10C@jasongarber.com>
	<C930E674-B00C-4A87-8703-7B4CF5B6BF00@acm.org>
Message-ID: <47C1E033.1000407@whatcould.com>

>
> Out of curiosity, do you know why Textile 2 made the choice it did  
> for rendering character entities?  Was there some compelling design  
> criteria involved?
>
> -- John

Just some speculation...

one of the seminal articles on character entities -- the ALA trouble 
with ems and ens -- said decimal entities (&#8212;, etc) were more 
reliably rendered. It didn't give much detail on why named entitles were 
unreliable, only mentioning that netscape 4 had issues with named 
entities.  That article is why I (and lots of others, I assume) have 
always used numerical entities.

Maybe that's why textile 2 chose numbered entities too?

anyway, my 2 cents -- I assume modern browsers render all the named 
entitles correctly... so i'd agree with Jason for going with named 
entitles, for readability anyway.

david



From lists at ruby-forum.com  Sun Feb 24 17:54:11 2008
From: lists at ruby-forum.com (Hum Plop)
Date: Sun, 24 Feb 2008 23:54:11 +0100
Subject: Install / Build fail on OSX Server 10.5.2
Message-ID: <80c8b9bc31098813e0b45cef8826bf88@ruby-forum.com>

Hello,

I would like to install SuperRedCloth on my server, here is the entire
log :

gem install superredcloth --source http://code.whytheluckystiff.net
Building native extensions.  This could take a while...
ERROR:  Error installing superredcloth:
  ERROR: Failed to build gem native extension.

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
extconf.rb install superredcloth --source
http://code.whytheluckystiff.net
checking for main() in -lc... yes
creating Makefile

make
gcc -I. -I.
-I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin9.0
-I.  -fno-common -arch ppc -arch i386 -Os -pipe -fno-common  -c
superredcloth_inline.c
Out of stack space.
Try running 'ulimit -S -s unlimited' in the shell to raise its limit.
{standard input}:unknown:Undefined local symbol L_rb_hash_aref$stub
{standard input}:unknown:Undefined local symbol L_rb_num2long$stub
{standard input}:unknown:Undefined local symbol L_rb_int2inum$stub
{standard input}:unknown:Undefined local symbol L_rb_hash_aset$stub
{standard input}:unknown:Undefined local symbol L_rb_str_cat$stub
{standard input}:unknown:Undefined local symbol L_rb_str_cat2$stub
Out of stack space.
Try running 'ulimit -S -s unlimited' in the shell to raise its limit.
{standard input}:unknown:Undefined local symbol L_rb_hash_aref$stub
{standard input}:unknown:Undefined local symbol L_rb_num2long$stub
{standard input}:unknown:Undefined local symbol L_rb_int2inum$stub
{standard input}:unknown:Undefined local symbol L_rb_hash_aset$stub
{standard input}:unknown:Undefined local symbol L_rb_str_cat$stub
{standard input}:unknown:Undefined local symbol L_rb_str_cat2$stub
lipo: can't open input file: /var/tmp//cc3JKHGQ.out (No such file or
directory)
make: *** [superredcloth_inline.o] Error 1


Gem files will remain installed in
/Library/Ruby/Gems/1.8/gems/superredcloth-1.160 for inspection.
Results logged to
/Library/Ruby/Gems/1.8/gems/superredcloth-1.160/ext/superredcloth_scan/gem_make.out




The ulimit -S -s unlimited is impossible -> -S don't exists for OSX, and
with ulimit -s I can only go up to 32MB, unlimited is impossible. (the
default value for -s is 8192)

I tried an other method : I have installed ragel and checked out the
trunk of superredcloth, then :

bash-3.2# rake
(in /private/var/root/superredcloth)
ragel ext/superredcloth_scan/superredcloth_scan.rl | rlgen-cd -G2 -o
ext/superredcloth_scan/superredcloth_scan.c
rake aborted!
Command failed with status (1): [ragel
ext/superredcloth_scan/superredcloth...]
/private/var/root/superredcloth/rakefile:122
(See full trace by running task with --trace)


Failed too, so I tried with --trace, but I don't see nothing really
usefull :

bash-3.2# rake --trace
(in /private/var/root/superredcloth)
** Invoke default (first_time)
** Invoke compile (first_time)
** Invoke superredcloth_scan (first_time)
** Invoke ext/superredcloth_scan/Makefile (first_time, not_needed)
** Invoke ext/superredcloth_scan/extconf.rb (first_time, not_needed)
** Invoke ext/superredcloth_scan/superredcloth_scan.bundle (first_time)
** Invoke ext/superredcloth_scan/superredcloth_scan.c (first_time)
** Invoke ext/superredcloth_scan/superredcloth_scan.rl (first_time,
not_needed)
** Invoke ext/superredcloth_scan/superredcloth_common.rl (first_time,
not_needed)
** Invoke ext/superredcloth_scan/superredcloth.h (first_time,
not_needed)
** Execute ext/superredcloth_scan/superredcloth_scan.c
ragel ext/superredcloth_scan/superredcloth_scan.rl | rlgen-cd -G2 -o
ext/superredcloth_scan/superredcloth_scan.c
rake aborted!
Command failed with status (1): [ragel
ext/superredcloth_scan/superredcloth...]
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:899:in `sh'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:906:in `call'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:906:in `sh'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:985:in `sh'
/private/var/root/superredcloth/rakefile:122
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:546:in `call'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:546:in `execute'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:541:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:541:in `execute'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:508:in
`invoke_with_call_chain'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `synchronize'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in
`invoke_with_call_chain'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:518:in
`invoke_prerequisites'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1183:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1183:in `send'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1183:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:515:in
`invoke_prerequisites'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:507:in
`invoke_with_call_chain'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `synchronize'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in
`invoke_with_call_chain'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:518:in
`invoke_prerequisites'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1183:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1183:in `send'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1183:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:515:in
`invoke_prerequisites'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:507:in
`invoke_with_call_chain'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `synchronize'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in
`invoke_with_call_chain'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:518:in
`invoke_prerequisites'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1183:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1183:in `send'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1183:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:515:in
`invoke_prerequisites'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:507:in
`invoke_with_call_chain'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `synchronize'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in
`invoke_with_call_chain'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:518:in
`invoke_prerequisites'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1183:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1183:in `send'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1183:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:515:in
`invoke_prerequisites'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:507:in
`invoke_with_call_chain'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in `synchronize'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:501:in
`invoke_with_call_chain'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:494:in `invoke'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1931:in `invoke_task'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `top_level'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1909:in `top_level'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1948:in
`standard_exception_handling'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1903:in `top_level'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1881:in `run'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1948:in
`standard_exception_handling'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/lib/rake.rb:1878:in `run'
/Library/Ruby/Gems/1.8/gems/rake-0.8.1/bin/rake:31
/usr/bin/rake:19:in `load'
/usr/bin/rake:19





Please help me, I really need superredcloth. Thanks.
-- 
Posted via http://www.ruby-forum.com/.

From jg at jasongarber.com  Mon Feb 25 12:06:35 2008
From: jg at jasongarber.com (Jason Garber)
Date: Mon, 25 Feb 2008 12:06:35 -0500
Subject: Plan for entities and code blocks
In-Reply-To: <47C1E033.1000407@whatcould.com>
References: <9CB1DBCB-FFD5-45E5-8775-74D4B301A10C@jasongarber.com>
	<C930E674-B00C-4A87-8703-7B4CF5B6BF00@acm.org>
	<47C1E033.1000407@whatcould.com>
Message-ID: <41D30396-90AF-4176-90B1-9DA47FDD2C75@jasongarber.com>

I didn't have any idea, John.  Thanks for shedding some light on it,  
David.

Jason

On Feb 24, 2008, at 4:22 PM, David Reese wrote:

>>
>> Out of curiosity, do you know why Textile 2 made the choice it did
>> for rendering character entities?  Was there some compelling design
>> criteria involved?
>>
>> -- John
>
> Just some speculation...
>
> one of the seminal articles on character entities -- the ALA trouble
> with ems and ens -- said decimal entities (&#8212;, etc) were more
> reliably rendered. It didn't give much detail on why named entitles  
> were
> unreliable, only mentioning that netscape 4 had issues with named
> entities.  That article is why I (and lots of others, I assume) have
> always used numerical entities.
>
> Maybe that's why textile 2 chose numbered entities too?
>
> anyway, my 2 cents -- I assume modern browsers render all the named
> entitles correctly... so i'd agree with Jason for going with named
> entitles, for readability anyway.
>
> david
>
>
> _______________________________________________
> Redcloth-upwards mailing list
> Redcloth-upwards at rubyforge.org
> http://rubyforge.org/mailman/listinfo/redcloth-upwards


From gaspard at teti.ch  Wed Feb 27 01:32:33 2008
From: gaspard at teti.ch (Gaspard Bucher)
Date: Wed, 27 Feb 2008 07:32:33 +0100
Subject: remove compilation optimization flag
Message-ID: <7a9f744a0802262232p2fb5913dt24af22d8391b1990@mail.gmail.com>

top output (compilation took about 10 minutes)
  # cc1          8.6%  5:13.31   1    13   365   730M+ 2.45M   519M- 1.13G

time to run all tests (3rd launch):
real    0m2.713s
user    0m1.321s
sys     0m0.306s

Without optimization flag (compilation takes 30 seconds):
# cc1         84.0%  0:17.15   1    13   203   243M+ 4.42M   245M+  435M+

time to run all tests (3rd launch)
real    0m2.560s
user    0m1.323s
sys     0m0.319s

I think it would be a good change, especially when people compile this
on a server with limited memory and shared CPU resources...

PATCH:
Index: ext/superredcloth_scan/extconf.rb
===================================================================
--- ext/superredcloth_scan/extconf.rb	(revision 245)
+++ ext/superredcloth_scan/extconf.rb	(working copy)
@@ -1,9 +1,6 @@
 require 'mkmf'

-if /darwin9/ =~ RUBY_PLATFORM
-  # OSX 10.5 doesn't like the default "-Os"
-  $CFLAGS << " -O1 "
-end
+$CFLAGS << " -O0 " # do not optimize (takes too much memory and
performance gain is negligeable)

 dir_config("superredcloth_scan")
 have_library("c", "main")

From gaspard at teti.ch  Wed Feb 27 01:38:25 2008
From: gaspard at teti.ch (Gaspard Bucher)
Date: Wed, 27 Feb 2008 07:38:25 +0100
Subject: to_latex
Message-ID: <7a9f744a0802262238j54812997id9d89b5e4baa4043@mail.gmail.com>

Hi there !

I needed a 'to_latex' implementation to generate PDF in zena (a CMS
http://zenadmin.org) through LaTeX.

Here is a first draft for a 'to_latex' implementation.

There are some issues with tables, footnotes but the biggest issue is
character escaped to their html entities (&#8217;). I have just
started writing the tests. More to come soon.

I will try to find a way to fix this without modifying too much of
SuperRedCloth.

(the patch applies on SR rev 245).

Gaspard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: to_latex.patch
Type: application/octet-stream
Size: 8463 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/redcloth-upwards/attachments/20080227/ba28630b/attachment-0001.obj 

From jg at jasongarber.com  Wed Feb 27 09:47:59 2008
From: jg at jasongarber.com (Jason Garber)
Date: Wed, 27 Feb 2008 09:47:59 -0500
Subject: to_latex
In-Reply-To: <7a9f744a0802262238j54812997id9d89b5e4baa4043@mail.gmail.com>
References: <7a9f744a0802262238j54812997id9d89b5e4baa4043@mail.gmail.com>
Message-ID: <DD73790D-55A0-4791-9D3B-592C633DE18E@jasongarber.com>

Could you post this as a ticket on http://code.whytheluckystiff.net/ 
redcloth/newticket?  You must create a RubyForge account and give  
yourself access at http://code.whytheluckystiff.net/access/

I'd like to have different formatters for XHTML and HTML, too, so  
yeah, SRC should be as formatter-agnostic as possible.

On Feb 27, 2008, at 1:38 AM, Gaspard Bucher wrote:

> Hi there !
>
> I needed a 'to_latex' implementation to generate PDF in zena (a CMS
> http://zenadmin.org) through LaTeX.
>
> Here is a first draft for a 'to_latex' implementation.
>
> There are some issues with tables, footnotes but the biggest issue is
> character escaped to their html entities (&#8217;). I have just
> started writing the tests. More to come soon.
>
> I will try to find a way to fix this without modifying too much of
> SuperRedCloth.
>
> (the patch applies on SR rev 245).
>
> Gaspard<to_latex.patch>_______________________________________________
> Redcloth-upwards mailing list
> Redcloth-upwards at rubyforge.org
> http://rubyforge.org/mailman/listinfo/redcloth-upwards


From gaspard at teti.ch  Wed Feb 27 12:14:54 2008
From: gaspard at teti.ch (Gaspard Bucher)
Date: Wed, 27 Feb 2008 18:14:54 +0100
Subject: to_latex
In-Reply-To: <DD73790D-55A0-4791-9D3B-592C633DE18E@jasongarber.com>
References: <7a9f744a0802262238j54812997id9d89b5e4baa4043@mail.gmail.com>
	<DD73790D-55A0-4791-9D3B-592C633DE18E@jasongarber.com>
Message-ID: <7a9f744a0802270914i71d75032t2e932d36123017fa@mail.gmail.com>

Done ! http://code.whytheluckystiff.net/redcloth/ticket/35

(I added the code to fix the html entities escaping problem).

2008/2/27, Jason Garber <jg at jasongarber.com>:
> Could you post this as a ticket on http://code.whytheluckystiff.net/
>  redcloth/newticket?  You must create a RubyForge account and give
>  yourself access at http://code.whytheluckystiff.net/access/
>
>  I'd like to have different formatters for XHTML and HTML, too, so
>  yeah, SRC should be as formatter-agnostic as possible.
>
>
>  On Feb 27, 2008, at 1:38 AM, Gaspard Bucher wrote:
>
>  > Hi there !
>  >
>  > I needed a 'to_latex' implementation to generate PDF in zena (a CMS
>  > http://zenadmin.org) through LaTeX.
>  >
>  > Here is a first draft for a 'to_latex' implementation.
>  >
>  > There are some issues with tables, footnotes but the biggest issue is
>  > character escaped to their html entities (&#8217;). I have just
>  > started writing the tests. More to come soon.
>  >
>  > I will try to find a way to fix this without modifying too much of
>  > SuperRedCloth.
>  >
>  > (the patch applies on SR rev 245).
>  >
>
> > Gaspard<to_latex.patch>_______________________________________________
>  > Redcloth-upwards mailing list
>  > Redcloth-upwards at rubyforge.org
>  > http://rubyforge.org/mailman/listinfo/redcloth-upwards
>
>  _______________________________________________
>  Redcloth-upwards mailing list
>  Redcloth-upwards at rubyforge.org
>  http://rubyforge.org/mailman/listinfo/redcloth-upwards
>

From jg at jasongarber.com  Wed Feb 27 12:22:54 2008
From: jg at jasongarber.com (Jason Garber)
Date: Wed, 27 Feb 2008 12:22:54 -0500
Subject: remove compilation optimization flag
In-Reply-To: <7a9f744a0802262232p2fb5913dt24af22d8391b1990@mail.gmail.com>
References: <7a9f744a0802262232p2fb5913dt24af22d8391b1990@mail.gmail.com>
Message-ID: <7B41563C-5E1B-4505-AA37-B1B54F6182FC@jasongarber.com>

Gaspard:
Hey, wow!  You're my new favorite person.  I'd been commenting out  
nonessentials when I was working on something specific and just  
waiting the 10 minutes when I wanted to see the whole thing work.

I'm committing this change.  Johan, since you're the one who  
requested the -O1 flag, would you verify it still works for you in  
Leopard?

If anyone knows a reason it's bad to compile with -O0, now's the time  
to speak up.

Great work, Gaspard!  Thanks!

Jason

On Feb 27, 2008, at 1:32 AM, Gaspard Bucher wrote:

> top output (compilation took about 10 minutes)
>   # cc1          8.6%  5:13.31   1    13   365   730M+ 2.45M    
> 519M- 1.13G
>
> time to run all tests (3rd launch):
> real    0m2.713s
> user    0m1.321s
> sys     0m0.306s
>
> Without optimization flag (compilation takes 30 seconds):
> # cc1         84.0%  0:17.15   1    13   203   243M+ 4.42M   245M+   
> 435M+
>
> time to run all tests (3rd launch)
> real    0m2.560s
> user    0m1.323s
> sys     0m0.319s
>
> I think it would be a good change, especially when people compile this
> on a server with limited memory and shared CPU resources...
>
> PATCH:
> Index: ext/superredcloth_scan/extconf.rb
> ===================================================================
> --- ext/superredcloth_scan/extconf.rb	(revision 245)
> +++ ext/superredcloth_scan/extconf.rb	(working copy)
> @@ -1,9 +1,6 @@
>  require 'mkmf'
>
> -if /darwin9/ =~ RUBY_PLATFORM
> -  # OSX 10.5 doesn't like the default "-Os"
> -  $CFLAGS << " -O1 "
> -end
> +$CFLAGS << " -O0 " # do not optimize (takes too much memory and
> performance gain is negligeable)
>
>  dir_config("superredcloth_scan")
>  have_library("c", "main")
> _______________________________________________
> Redcloth-upwards mailing list
> Redcloth-upwards at rubyforge.org
> http://rubyforge.org/mailman/listinfo/redcloth-upwards


From why at hobix.com  Thu Feb 28 10:48:48 2008
From: why at hobix.com (why the lucky stiff)
Date: Thu, 28 Feb 2008 09:48:48 -0600
Subject: remove compilation optimization flag
In-Reply-To: <7B41563C-5E1B-4505-AA37-B1B54F6182FC@jasongarber.com>
References: <7a9f744a0802262232p2fb5913dt24af22d8391b1990@mail.gmail.com>
	<7B41563C-5E1B-4505-AA37-B1B54F6182FC@jasongarber.com>
Message-ID: <20080228154847.GP47128@beekeeper.hobix.com>

On Wed, Feb 27, 2008 at 12:22:54PM -0500, Jason Garber wrote:
> I'm committing this change.  Johan, since you're the one who  
> requested the -O1 flag, would you verify it still works for you in  
> Leopard?

I agree, nice tweak!  I'm playing with the Ragel flags and noticing
wildly different behaviors as well.  (Using -G0, -T0, -T1, etc.
instead of -G2.)  I'd really like to assemble a rake tasks that
would go through and try permutations of Ragel flags with GCC flags
and determine the most optimal settings.

For sure, though, compilation time was getting ridiculous.

_why

From gaspard at teti.ch  Thu Feb 28 11:24:18 2008
From: gaspard at teti.ch (Gaspard Bucher)
Date: Thu, 28 Feb 2008 17:24:18 +0100
Subject: remove compilation optimization flag
In-Reply-To: <20080228154847.GP47128@beekeeper.hobix.com>
References: <7a9f744a0802262232p2fb5913dt24af22d8391b1990@mail.gmail.com>
	<7B41563C-5E1B-4505-AA37-B1B54F6182FC@jasongarber.com>
	<20080228154847.GP47128@beekeeper.hobix.com>
Message-ID: <7a9f744a0802280824l7987fe60r4fee4eea2f2070e0@mail.gmail.com>

While trying ragel optimization settings, it would be good to record
the size of the output files, since I think it would be nice to
include these files in the gem in order to avoid ragel dependency for
those not modifying the gem.

Gaspard

2008/2/28, why the lucky stiff <why at hobix.com>:
> On Wed, Feb 27, 2008 at 12:22:54PM -0500, Jason Garber wrote:
>  > I'm committing this change.  Johan, since you're the one who
>  > requested the -O1 flag, would you verify it still works for you in
>  > Leopard?
>
>
> I agree, nice tweak!  I'm playing with the Ragel flags and noticing
>  wildly different behaviors as well.  (Using -G0, -T0, -T1, etc.
>  instead of -G2.)  I'd really like to assemble a rake tasks that
>  would go through and try permutations of Ragel flags with GCC flags
>  and determine the most optimal settings.
>
>  For sure, though, compilation time was getting ridiculous.
>
>
>  _why
>
> _______________________________________________
>  Redcloth-upwards mailing list
>  Redcloth-upwards at rubyforge.org
>  http://rubyforge.org/mailman/listinfo/redcloth-upwards
>