Such a scheme would have to be optional of course, as I don't think highlighting an obfuscation would be such a good idea (on top of being probably quite difficult!)

BooK did his obfuscation explanations at YAPC::Eu with code tidied by PerlTidy, which seems to colorize it.

Greetz
Beatnik
... Quidquid perl dictum sit, altum viditur.

It sounds like an interesting exercise, but one that wouldn't be particularly nasty: there are already syntax-coloring filters for perl out there (consider that both vim and cooledit have them, and cooledit has the peculiar misfortune of being written in python). It shouldn't require much more than turning the ANSI escape sequences in the syntax-highlighting routines in vim into the corresponding <SPAN> tags in HTML. Getting <SPAN> recognized inside of <CODE> is another matter altogether -- <CODE> is designed to indicate to the browser that as much as possible within the block is to be treated literally.

Spud Zeppelin * spud@spudzeppelin.com

Using <code> tags in your post doesn't actually put a <code> tag in the html output when you view it (check the source). One of the reasons I suggested it is because there's already some kind of magick going on with <code> tags, so I figured that it might be as easy as putting in a sub for the code highlighting along with $code = highlight_code($code) if $user_prefs{'wants_highlighting'} in the bit that deals with the code. (Dammit! I've got <code> on the brain now after using it 16 times in this post. :-)

While we're discussing syntax coloring in editors, Glimmer has syntax coloring since way before it was called Glimmer. But then again, what use is that in the Monastery? Looking into PerlTidy is probably a good thing.

Greetz
Beatnik
... Quidquid perl dictum sit, altum viditur.

Have a look at code2html, it's written in Perl and works fairly well for several languages.

Kev

Kevin O'Rourke

:ru! syntax/2html.vim

Note that it doesn't handle [] constructs; it could easily be made to do so by adding to the 2html.vim file. I've also used perltidy to make HTML; it too would have to be post-filtered.

package XX;

sub _create_accessors
{
    my %orderObjectFields = @_;

    foreach my $field ( keys %orderObjectFields )
    {
        my $default = $orderObjectFields{$field};
        no strict 'refs';
        *{ __PACKAGE__ . "::$field" } = sub
        {
            my $value =
              ( scalar @_ > 1 ? $_<span style="background-color: #f2f2f2"><font color="#ff00ff">0</font></span>->{$field} = $_<span style="background-color: #f2f2f2"><font color="#ff00ff">1</font></span> : $_<span style="background-color: #f2f2f2"><font color="#ff00ff">0</font></span>->{$field} );
            $value = $default unless defined $value;
            $value;
        };
    }
}