"ocaml_beginners"::[] Re: Syntax error when evaluating type definition in tuareg-mode

2006/9/12, doug_arro <doug_arroyahoo.com>:

> I appologize for not making myself clear.  No, I
didn't have that
> extra "#".  I typed it this way in an emacs
editor window:
>
> type 'param paired_with_integer = int * 'param ;;
>
> Then I pressed "C-c C-e" to evaluate that
phrase but got the syntax
> error shown above.

This look like a bug in the tuareg mode. Please, report it
to the
writer of the tuareg mode (Albert.Coheninria.fr). Thanks.


Archives up to August 22, 2005 are also downloadable at http://www.connettivo.net/cntprojects/ocaml_beginners/
The archives of the very official ocaml list (the seniors'
one) can be found at http://caml.inria.fr
Attachments are banned and you're asked to be polite, avoid
flames etc. 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http:/
/groups.yahoo.com/group/ocaml_beginners/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    ht
tp://groups.yahoo.com/group/ocaml_beginners/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:ocaml_beginners-digest@yahoogroups.com 
    mailto:ocaml_beginners-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
    ocaml_beginners-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.c
om/info/terms/
 

Hi Jakob,

On 09/12/06 09:44, Jakob Lechner wrote:

> I have written an IDL file and transformed this into a
rdb registry
> and into c header files. I have named the rdb file
"smarttags.rdb" and
> placed it into the program directory of my OOo
installation.
> Up to my ideas every smarttag component has to be
registered in this
> file. Then the smarttag manager can open it and extract
the names of 
> all the registered implemenations of the smarttag
service and
> subsequently create an instance of each implementation.
> I hope this is a reasonable concept.

yes, I think so. But I'd like to discuss this issue with
Juergen Schmidt 
(our expert for these kind of questions), who is currently
attending the 
OOo conference.

> Am Dienstag, den 05.09.2006, 14:58 +0200 schrieb Frank
Meies:
>> 5. For each SmartTagReference in this vector, a
string/action pair is 
>> obtained from the associated SmartTagLibrary, the
strings will appear in 
>> the context menu and the invokeAction function will
be triggered if a 
>> context menu entry is invoked. A UNO textrange
object can be passed as a 
>> parameter of the invokeAction function to enable
the SmartTagLibrary to 
>> change the text etc.
>>
> 
> Currently I'm writing an example component that
implements the smarttag
> service and I have thought again about your proposal to
pass a TextRange
> object to the invokeAction method. Wouldn't it be
better to pass a 
> reference of the whole document as well? May be someone
wants to do
> more complex interactions with the document than just
modifying text.
> 
> In the developers guide I've found a figure about the
Text document 
> model:
> http://api.openoffice.org/docs/Develo
persGuide/Text/Text.xhtml#1_1_Overview
> 
> As far as I have understood the XController service is
the basic service
> that should be passed to provide access to the whole
document in the
> invokeAction method. As far as I've seen there is a
method called
> "getCurrentController" in the
SwXTextDocument class. Probably this
> method could be used to obtain the XController
reference when calling
> the invokeAction method.
 > Are my assumptions correct or completely wrong or is
there are better
 > way to do this?

Yes, you are right. We should pass the TextRange and the
Controller to 
the invokeAction methor. A better way to obtain the
Controller would be 
to use the GetController() method of the SwView object
(which in turn 
inherits it from the SfxViewShell object). This way we make
sure that we 
get the correct controller and do not run into any focus
related issues.

Regards,

Frank


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesw.openoffice.org
For additional commands, e-mail: dev-helpsw.openoffice.org