Skip to content
This repository

Sep 29, 2011

  1. [fix] opatop: ignore package directives instead of failing

    François-Régis Sinot authored

Sep 20, 2011

  1. Rudy Sicard

    [feature] Internationalisation: add @i18n directive and start support…

    … for translation packages
    
    see doc/i18n for more information
    OpaOnWindowsNow authored

Sep 15, 2011

  1. Rudy Sicard

    [enhance] opa syntax: in parser construct, add possibility to directl…

    …y call a subparser with parameter
    OpaOnWindowsNow authored
  2. Rudy Sicard

    [enhance] opa syntax: add an optional slash at the start of sum type …

    …syntax
    OpaOnWindowsNow authored

Sep 12, 2011

  1. [feature] adding: a no_client_calls directive

    [fix] no_client_calls: fix rewriting
    Hugo Heuzard authored
  2. [fix] unicode detection: try LANG if LC_CTYPE not defined

    François-Régis Sinot authored
  3. [contrib] merge: pull request #6 from git://github.com/aszlig/opalang

    François-Régis Sinot authored

Sep 08, 2011

  1. aszlig

    Remove unicode chars from parser errors.

    This causes troubles with non-unicode terminals, so if the LC_CTYPE
    isn't UTF-8 capable a "-->" is printed instead.
    aszlig authored
  2. Frederic Ye

    [fix] parsing: at parsing, the class list were inversed. This should …

    …fix the problem between dev class order and generated class order
    Aqua-Ye authored

Aug 10, 2011

  1. Norman Scaife

    [feature] Badop_light: Attempt at OPA integration (partially successf…

    …ul).
    nrs135 authored Louis Gesbert committed

Jul 29, 2011

  1. fpessaux

    [cleanup] remove chars: compiler

    fpessaux authored François-Régis Sinot committed

Jul 07, 2011

  1. [feature] adding: an @async directive on bindings to perform asynchro…

    …nous calls
    
    both local and remote (only client->server though)
    Valentin Gatien-Baron authored
  2. [cleanup] garbage: collecting some directives

    Valentin Gatien-Baron authored
  3. [cleanup] parser: changing the parsing of directives

    in the hope that error messages would be clearer if we don't interrupt trx while
    it is backtracking
    Valentin Gatien-Baron authored
  4. Mathieu Barbin

    [fix] exception: accept the tmp syntax in release mode too (used now …

    …in the stdlib)
    mbarbin authored

Jul 06, 2011

  1. [enhance] parser: homogenising escape sequences

    Valentin Gatien-Baron authored
  2. [enhance] parser: allowing utf8 escapes and characters

    Valentin Gatien-Baron authored

Jun 30, 2011

  1. [feature] parser: allowing slicing annotations on local functions

    Valentin Gatien-Baron authored
  2. [cleanup] open: remove Base in opalang

    Raja authored
  3. [cleanup] open: remove Base in opaToQml

    Raja authored
  4. [cleanup] Base: remove sprintf

    Raja authored
  5. [cleanup] Base: remove error

    Raja authored

Jun 27, 2011

  1. fpessaux

    [fix] stdlib: Ticket OPA-608. Value restriction issue no CSS.

    The origin of the problem is that
      id_gui_area = "foo"
      default_css = css #{id_gui_area} { } ;
    is rewritten into an application expression. so it is considered expansive
    and can't be generalized. The type of the expression is
      ordered_map(Css.entry, map(string, 'v0), Css.order)
    with the 'v0 being not generalizable.
    In fact, the deeper issue is the fact that we are not able to write
    in Opa the type of Map_make showing the type of values of the map.
    So we are not able to force these values to have a constrained type.
    We would like to be able to have a "'value Map('key, 'order)" or
    something like that.
    So, to workaround, we added a field to the module Css_private and a
    constraint on this field stating that values are of type
    list(Css.prop_value_item). Hence, this constraint gets propagated and
    the type of the module contains no more type variables.
    The added field "renames" (is an alias on) the field "empty" of maps and
    is the one used in parsers_utils.trx to rewrite CSS constructs.
    fpessaux authored

Jun 22, 2011

  1. [update] parser: the rules for parser expr and types were broken

    for quite some time, actually
    Valentin Gatien-Baron authored

Jun 21, 2011

  1. Initial open-source release

    MLstate authored
Something went wrong with that request. Please try again.