[Nitro] [PATCH] tags

Bryan Soto bryan.a.soto at gmail.com
Mon Apr 10 02:15:47 EDT 2006

No worries, manveru. :)

As I said, it was just something that came up on the list before.
George liked the idea but, just as you, wanted to benchmark. From that
I gather if it's done, it'd just be for hot spots.


On 4/9/06, Michael Fellinger <m.fellinger at gmail.com> wrote:
> just wondering, but how exactly will having C in the repo work withpulling? do we have to compile it all again everytime... ? (and yes, ido hate compiling)I think before we are writing something in C we should first try tobenchmark nitro... I found this an impossible task due to thekernel#autoreload - it causes some really bad failures.However, if we could benchmark the whole application we could justsave us a bit of work and find out where exactly the problems arelurking, right? :)
> On 4/10/06, Kashia Buch <kashia at vfemail.net> wrote:> Hi,>> > Pointers aren't that bad. Just a different way of thinking.> > (Disclaimer: I'm a C programmer :)>> Pointers are nice, in a perfect world ;)> But things stop working nice, when something totally unrelated can> break everything, just because I myself am not fully able to "feel> the flow" of the C++ program.>> > Well, do it for Nitro then. There was talk a while back of speeding> > things up by rewriting portions in C. Might be an investment in> > Nitro's future. :)>> This is a good idea, and I thought about the same thing when I saw> the Template compiling.>> Horrible! I almost broke into tears ;/>> if you change the template string in tc_template.rb to:>>      template = %q{>        Hello #{user}>>        dont forget the following ^ todo ^ items:>>        <?r for item in items ?>>          <li>#{item}</li>>        <?r end ?>>>        <?r out << "teasdfasdfasdft ?>" ?>>        <?r #puts "no way in hell" ?>>        #!
> {"asdf \t...".to_s.squeeze("\s").gsub!(/<[^>]+?>/, '')}>        <include href=|asdf/asddd| /> now this .. <br />>      }>> There are at least 7 serious problems going on here, which all> originate from template.rb, and not all are easyly spotted.....>> So, writing a real parser for the nhtml's (nitro xhtmls :P) would> be a very beneficial task... (the current ... hacks? are.. I can't> really describe it..)>> This post is not intended to hurt any feelings or to bash George> for it. The current implementation works and is ok for now, but> some day, some things will have to be done :)> Maybe this will end in me writing something in C to address it,> but that'll be in another lightyear or two (I'm aware that light-> year is not used for time measurment ;))>> Kashia>> --> Feel the love> http://pinkjuice.com/pics/ruby.png> _______________________________________________> Nitro-general mailing list> Nitro-general at rubyforge.org> http://rubyforge.org/mailman/listinfo/nitro-general>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general

"Never tell people how to do things. Tell them what to do and they
will surprise you with their ingenuity." —General George S. Patton

More information about the Nitro-general mailing list