From: Edgar Friendly <thelema314@gmail.com>
To: Robert Roessler <roessler@rftp.com>,
caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] GtkSourceView2.0 syntax highlighting
Date: Wed, 30 May 2007 00:30:36 -0500 [thread overview]
Message-ID: <465D0BFC.7040006@gmail.com> (raw)
In-Reply-To: <465C9CFA.4000601@rftp.com>
Robert Roessler wrote:
> Edgar Friendly wrote:
>> The upcoming version of GtkSourceView, the library used by many Gnome
>> text editors for syntax highlighting, supports new and more powerful
>> language parsing. I volunteer to update the language definition for
>> Ocaml, and would like some feedback from the community regarding useful
>> things to highlight.
>
> A "gotcha" to be aware of (if you aren't already handling this): don't
> forget that OCaml comments nest. ;)
>
Yup, that's being handled. Another fun gotcha I found is that comments
aren't comments inside string literals.
> Also, from my OCaml lexer in the Scintilla distribution:
>
> # suggested; more could come from, say, Pervasives
> keywordoptional1.caml= \
> option Some None ignore ref lnot succ pred
>
> # suggested; more could come from, say, user-defined types
> keywordoptional2.caml= \
> array bool char float int list string unit
>
wow, this is going to be a lot of keyword highlighting. people might
run out of colors on their screen.
> The full set (including default coloring values) may be found in the
> caml.properties file in a Scintilla source tree.
>
> Robert Roessler
> roessler@rftp.com
> http://www.rftp.com
>
Thanks for the feedback,
E.
next prev parent reply other threads:[~2007-05-30 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 19:04 Edgar Friendly
2007-05-29 19:47 ` [Caml-list] " Richard Jones
2007-05-29 21:31 ` Edgar Friendly
2007-05-29 21:36 ` Robert Roessler
2007-05-30 5:30 ` Edgar Friendly [this message]
2007-05-30 1:02 ` skaller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=465D0BFC.7040006@gmail.com \
--to=thelema314@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=roessler@rftp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox