Hello,
Kuba Ober wrote:
What would make me switch: a way to highlight the error when compiling,
highlighting the line, a stronger highlight for the character range
reported by the compiler, taking in consideration the tab mode used (real
tab, n spaces) to interpret the value returned by the comp
That's actually nearly what Camelia has right now. Right now Camelia
insists on not dealing with tabs at all -- it converts them all to
spaces. This "feature" has to go obviously, and it's a few-liner to
convert between characters (which include tabs) and columns.
What do you mean with this? Rea
I would prefer to not have an editor which modify completely the file I am
working on (ie. automatically replace tab by spaces). When working on big
project, you cannot assume that everybody use spaces-based editor, and you
still want to minimize the diff size of your patches.
Thomas
2008/10/23 R
Thomas Gazagnaire wrote:
I would prefer to not have an editor which modify completely the file I
am working on (ie. automatically replace tab by spaces). When working on
big project, you cannot assume that everybody use spaces-based editor,
and you still want to minimize the diff size of your p
Federated Conference on Rewriting, Deduction, and Programming
RDP'09
28/6/2009 - 3/7/2009, Brasilia, Brazil
Second Call For Workshop Proposals
RDP'09 is a federated event comprising two major conferences:
> I agree. There are many different use cases, different types of developers
> with different goals and styles. Putting most of the heavy lifting into
> external tools so that can be integrated into any editor would be a great
> boon across the board.
>
> Actually, how did ocamlwizard go? I seem
On Thu, Oct 23, 2008 at 12:01:00PM +0100, Hugo Ferreira wrote:
> Thomas Gazagnaire wrote:
>> I would prefer to not have an editor which modify completely the file I
>> am working on (ie. automatically replace tab by spaces). When working
>> on big project, you cannot assume that everybody use spa
tab has no length. projects tab-indented (not talking about alignment here),
is the only consistant choice that permit everyone in this same project
to use any *representation* they want for their indentation (8 spaces, 2
spaces, 4 spaces, 11 spaces, ...) without making a mess.
Sure, this would
Am Mittwoch, den 22.10.2008, 13:11 -0700 schrieb Dario Teixeira:
> Hi,
>
> I am using PXP to parse the MathML2 DTD. This is a fairly large DTD,
> which even on a fast machine takes several seconds to parse. I am
> therefore looking at ways to serialise a parsed DTD, in a such a way
> that it ca
Romain Bardou wrote:
let x = List.map (fun z ->
very_long_stuff_blablablablablablablabla)
I tend to write this sort of thing as:
let x =
List.map
(fun z ->
very_long_stuff_blablablablablablablabla)
...
which, as you may notice, still can't be done with tab
Hi,
First, and concerning the more general problem of serialisation:
one often comes across a situation where a library encodes a very
complex and opaque value of type Foobar.t, but offers no dedicated
(de)serialisation functions. The assumption is of course that users
can just use Marshal and be
On Thu, Oct 23, 2008 at 08:34:21AM -0700, Dario Teixeira wrote:
> - ease of use
> - "future-proofness"
> - portability
> - human-readability
>
> Sexplib scores very good on ease of use, future-proofness, and
Does it?
I mean, as long as
On Thu, Oct 23, 2008 at 11:34 AM, Dario Teixeira
<[EMAIL PROTECTED]> wrote:
> Sexplib scores very good on ease of use, future-proofness, and
> portability, and reasonably good on performance and human-readability.
> My guess is that bin-prot has better performance but worse portability
> and future
On Thu, Oct 23, 2008 at 12:37 PM, Stefano Zacchiroli <[EMAIL PROTECTED]> wrote:
> I mean, as long as types are as simples are pairs we will probably
> write down the very same S-expression, but for more complex types you
> hand up having to choose how to encode them in S-expressions. Such
> design
On Wednesday 22 October 2008, you wrote:
> Thanks, I tried it and I love the simplicity vis-a-vis eclipse's
> baroqueness. But am I missing something?
> When I type in a line of caml followed by a CR the cursor lines up all
> the way to the left rather than indenting
> on the next line. Once I'm do
> >> What would make me switch: a way to highlight the error when compiling,
> >> highlighting the line, a stronger highlight for the character range
> >> reported by the compiler, taking in consideration the tab mode used
> >> (real tab, n spaces) to interpret the value returned by the compiler.
>
On Thursday 23 October 2008, Vincent Hanquez wrote:
> On Thu, Oct 23, 2008 at 12:01:00PM +0100, Hugo Ferreira wrote:
> > Thomas Gazagnaire wrote:
> >> I would prefer to not have an editor which modify completely the file I
> >> am working on (ie. automatically replace tab by spaces). When working
>
Hi,
> Bin-prot is settled in its design. We heavily rely on it here
> at Jane Street and store TBs of data in it so there is no way
> it's going to change. I would say it is future-proof.
Thanks for the clarification, Markus, and I will take a closer
look at bin-prot. One question, however: is
On Thu, Oct 23, 2008 at 2:41 PM, Dario Teixeira <[EMAIL PROTECTED]> wrote:
> Thanks for the clarification, Markus, and I will take a closer
> look at bin-prot. One question, however: is it possible to use
> *both* the sexplib and bin-prot syntax extensions on the same
> structure? That way conven
> I mean, as long as types are as simples are pairs we will
> probably write down the very same S-expression, but for more
> complex types you hand up having to choose how to encode them
> in S-expressions. Such design choices can need to be changed
> in the future as more types will be supported.
Hello,
I'm from germany, the only thing I need, is a texvc.exe for my
mediawiki-Internet side.
The Installation of 3.10 was possible.
"ocaml" in the command-line delivers "execption env-error".
The call of gmake under
C:\Inetpub\mslroot\...\math>gmake
delivers the following
ocamlopt -c uti
2008/9/28 David Teller <[EMAIL PROTECTED]>:
>> I hope to put up an example project eventually, but at least you have
>> the source code now.
>
> Symbiosis looks quite interesting. I'm really looking forward to seeing
> an example project!
Batteries also looks interesting - it seems we are attacki
>
> I'm from germany, the only thing I need, is a texvc.exe
> for my mediawiki-Internet side.
> The Installation of 3.10 was possible.
> "ocaml" in the command-line delivers
> "execption env-error".
>
Hi,
Do you really need to run it under Windows? I mean, will
you be hosting the MediaWiki si
Hi,
> Absolutely, both converters are supported simultaneously.
> That's why we had to factor out the type-conv package, because
> some code needs to be shared.
Excellent! I asked because I remember giving it a go some
months ago and running into preprocessor errors. But now I
realise what the
On Thu, Oct 23, 2008 at 12:26:54PM -0700, Dario Teixeira wrote:
> > I mean, as long as types are as simples are pairs we will
> > probably write down the very same S-expression, but for more
> > complex types you hand up having to choose how to encode them
> > in S-expressions. Such design choices
Am Donnerstag, den 23.10.2008, 23:05 +0200 schrieb Mauricio Fernandez:
> I have been working for a while on a self-describing, compact, extensible
> binary protocol, along with an OCaml implementation which I intent to release
> in not too long.
>
> It differs from sexplib and that bin-prot in tw
Hi,
> This protocol definition is fed to the compiler, which
> generates the OCaml type definitions, as well as the
> encoders/decoders and pretty-printers (as you can see,
> the specification uses a mix of OCaml, Haskell and C++
> syntax, but it's pretty clear IMO)
Basically the XDR approach, b
On Fri, Oct 24, 2008 at 12:18:50AM +0200, Gerd Stolpmann wrote:
>
> Am Donnerstag, den 23.10.2008, 23:05 +0200 schrieb Mauricio Fernandez:
> > I have been working for a while on a self-describing, compact, extensible
> > binary protocol, along with an OCaml implementation which I intent to
> > re
On Thu, Oct 23, 2008 at 03:21:01PM -0700, Dario Teixeira wrote:
> Hi,
>
> > This protocol definition is fed to the compiler, which
> > generates the OCaml type definitions, as well as the
> > encoders/decoders and pretty-printers (as you can see,
> > the specification uses a mix of OCaml, Haskell
29 matches
Mail list logo
