caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Edgar Friendly <thelema314@gmail.com>
Cc: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] GtkSourceView2.0 syntax highlighting
Date: Wed, 30 May 2007 11:02:12 +1000	[thread overview]
Message-ID: <1180486932.6252.26.camel@rosella.wigram> (raw)
In-Reply-To: <465C7954.1060208@gmail.com>

On Tue, 2007-05-29 at 14:04 -0500, Edgar Friendly wrote:

> The reasonably large list of keywords has been broken into four
> sections.  (I encourage comments on this division.)
> 
> 1) booleans
> 	true	false
> 
> 2) flow control & common keywords
> 	and	assert	begin	do	done	downto	else
> 	end	for	fun	function	if	in
> 	let	match	rec	then	to	try	val
> 	when	while	with
> 
> 3) types, objects & modules
> 	as	class	constraint	exception	external
> 	functor	include	inherit	initializer	method	module
> 	mutable	new	object	of	open	private	struct
> 	sig	type	virtual
> 
> 4) function-like keywords
> 	asr	land	lazy	lor	lsl	lsr	lxor
> 	mod	or
> 


I would do this slightly differently. The 'most important'
keywords are used in binders which often denote something
part of an interface: These are (roughly):

type, let, module, class, and, in, rec, val, exception
external functor

and these should be in a heavy font. Flow control is an implementation
detail and should be lighter weight. inherit, include, and open are
"directives", perhaps a weak color (boring houskeeping ..)



-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net


      parent reply	other threads:[~2007-05-30  1:02 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
2007-05-30  1:02 ` skaller [this message]

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=1180486932.6252.26.camel@rosella.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@yquem.inria.fr \
    --cc=thelema314@gmail.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;
as well as URLs for NNTP newsgroup(s).