gmane.lisp.scheme.bigloo

Re: Bigloo object system : default values ?

Saul Malesac — 2008-11-27T21:56:42

2008/11/27 Florian Loitsch sophia.inria.fr>: Thank you very much. Saul

Re: Bigloo object system : default values ?

Florian Loitsch — 2008-11-27T14:11:56

you have to use instantiate::Class instead of make-Class 1:=> (module toto (export (class test (i::elong (default #e0))))) #unspecified 1:=> (instantiate::test) #|test [i: #e0]| usually instantiate takes care of that (as default-values do not need to be filled in any more). Unfortunately (at AFAIK) there is no way to add a default value for an inherited class. 1:=> (module toto (export (class A i) (class B::A (i (default 'foo))))) *** ERROR:eval: Illegal duplicate field -- i 0.interp, Engine/interp.scm:48 1.engine, Engine/engine.scm:35 2.main, Init/main.scm:45 However, using the instantiate-form the name of each field is explicitly given, which makes it less troublesome. mfg, // florian

Bigloo object system : default values ?

Saul Malesac — 2008-11-27T13:21:51

Hi, Still more newbie questions : - How do default values work with classes ? $bigloo 1:=> (module toto (export (class test (i::elong (default #e0))))) #unspecified 1:=> (make-test) *** ERROR:eval: Wrong number of arguments: 1 expected, 0 provided -- ... make-test 0.... make-test 1:=> (define z (make-test (unspecified))) z 1:=> (test-i z) #unspecified So, I could not understand from the documentation when or how these default values are used. - my second question is about constructors and inheritance : constructors of subclasses seem to have as many parameters as the sum of all the inherited fields. This may become cumbersome (and hard to follow) with huge class hierarchies. How do you cope with this ? Sincerely yours, Saul

Re: compilation of Bigloo program under Windows XP

Yannis BRES — 2008-11-27T10:36:26

Yup. Unfortunately, this gives a hint for the reason why I couldn't cope with recent versions... Maybe, one of these days... Yannis ====================================================================== http://www.yaya.fr +33 (0) 6 60 38 79 52 ======================================================================

Re: compilation of Bigloo program under Windows XP

Laurent Bloch — 2008-11-27T10:18:14

Le jeudi 27 novembre 2008 Yannis BRES a écrit ceci : But I stay full of admiration for the tremendous effort of porting Bigloo natively to Windows! My little attempts showed how painfull it should have been! Cheers.

Re: compilation of Bigloo program under Windows XP

Yannis BRES — 2008-11-27T09:26:45

Cygwin is one of the first software I install on a fresh Windows... ;-) Yannis ====================================================================== http://www.yaya.fr +33 (0) 6 60 38 79 52 ======================================================================

Re: compilation of Bigloo program under Windows XP

Laurent Bloch — 2008-11-26T23:17:24

Le mercredi 26 novembre 2008 Dean Ferreyra a écrit ceci : Thank you, Yannis, Dean, for your suggestions, surely they give the solution. But I'm too lazy to write all these things by hand without a decent editor :-( and I switched to Cygwin. Sorry, but Windows is definitely too hard for me, I'm afraid.

Re: compilation of Bigloo program under Windows XP

Dean Ferreyra — 2008-11-26T15:09:39

Right, LIB should hold the paths to the library files for link-time, and INCLUDE should hold the paths to the include files for compile time. (There also appears to be a LIBPATH for .NET development, but I haven't used bigloo for that.) Dean

Re: compilation of Bigloo program under Windows XP

Dean Ferreyra — 2008-11-26T14:40:20

I think every Microsoft Visual Studio installation includes a batch file that will add/modify all the appropriate environment variables in your command prompt. For example, in my installation of Visual Studio .NET 2003 it's in at least two places: c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\vcvars32.bat c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\vsvars32.bat and in my Visual Studio 9.0 it's here: c:\Program Files\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat c:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat You can run one of these from the command prompt where you intend to run bigloo. Or you can view one in an editor and manually make the appropriate changes to your Windows environment variables. Or you can make a Windows shortcut to bring up a command prompt and automatically run the right batch file for you. Good luck! Dean

Re: compilation of Bigloo program under Windows XP

Yannis BRES — 2008-11-26T14:14:30

Hi ! There's another environment variable for that... Something regarding "LIB", I don't remind precisely... I sincerely doubt... How could the installer be aware of which C compiler you're using (C compiler, linker, option prefixes, etc. can actually even be changed in the registry, in case you want to use something else than MS compiler), where you've installed it, etc. ? This "issue" is OS agnostic : Bigloo won't work either if the gnu C compiler isn't in the PATH... Best regards, Yannis ====================================================================== http://www.yaya.fr +33 (0) 6 60 38 79 52 ======================================================================

Re: compilation of Bigloo program under Windows XP

Laurent Bloch — 2008-11-26T13:48:54

Hi, Le mardi 25 novembre 2008 Yannis BRES a écrit ceci : Thanks for your fast answer. We didn't have a doubt about you were alive :-) After some struggle with Microsoft Visual C++ Toolkit 2005 installation (it was in fact not completed) and PATH completion in order to find cl.exe and mspdb80.dll : C:\Program Files\Microsoft Visual Studio 8\VC\bin;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE now the problem is with stdio.h Couldn't all that manual configuration be avoided? Or am'I missing something, I am not a MS specialist at all. Cheers.

Re: BUG? (Re: Question srfi-9 and Bigloo and srfi-63)

2008-11-26T10:45:23

Hello Siegfried, This is a bug that I have just fixed. The new 3.2a alpha will be correct with respect to this problem. Sorry about that. Cheers,

Re: Yet another question

Saul Malesac — 2008-11-25T21:06:20

2008/11/25 Florian Loitsch sophia.inria.fr>: Actually, Bigloo is fine for me. Thank you for your example. Being used to other functional languages, where deep-copying of values is the norm, lead me to misunderstand the way Bigloo/scheme works on variables. Thanks, Saul

Re: compilation of Bigloo program under Windows XP

Yannis BRES — 2008-11-25T17:37:10

Hi ! (Yes, I'm alive, although I never took time to answer to recent emails asking about the status of the Windows distribution of Bigloo... ;-)) Is cl.exe accessible from the current PATH environment variable ? Best regards, Yannis ====================================================================== http://www.yaya.fr +33 (0) 6 60 38 79 52 ======================================================================

Re: Yet another question

Florian Loitsch — 2008-11-25T17:23:38

Scheme or Bigloo...? I'm not entirely sure if I understood your problem, but I do not see any problems having several structures (be it lists, Bigloo-objects, structs, ...) to the same object (the common PDF-structure) and thus sharing it. The "Scheme Way" (C) would be to use lists ore 'define-struct' for holding the data-structures. In Bigloo one would/should create classes instead. ex: (module (export (class PDF-Document toc cross-reference ...) (abstract-class PDF-Element (document::PDF-Document read-only)) (class PDF-Chapter::PDF-Element title::bstring ...) ...))) and then generics and methods to work with them. should not be necessary. Currently I do not have the time to have a look at it... mfg, // florian

compilation of Bigloo program under Windows XP

2008-11-25T17:12:20

Hi, After installation of Yannis Brès Windows port of Bigloo 2.8c ( http://www.yaya.fr/Bigloo/ ), interpreter is OK, but any attempt to compile anything results in : *** ERROR:run-process: Specified file not found -- cl 0.win32-cc 1.cc 2.cc-compiler 3.backend-link 4.backend-walk 5.compiler 6.engine 7.main The free Microsoft Visual C++ Toolkit 2005 is installed. Any hint will be appreciated. Thanks.

Sorry

Saul Malesac — 2008-11-25T16:39:03

Hi, Please excuse me for the last two mails I sent to this mail address : they were intended to be sent to the mailing list, but I have fumbled with my contacts. Sincerely yours, Saul

Yet another question

Saul Malesac — 2008-11-25T16:37:26

Hello all, I have a (may be stupid) question about Scheme programming or, let's say, programming pattern : still struggling with the PDF format, I'm currently wondering about how to implement the "right" "PDF structure". I mean, PDF objects are somewhat like XML nodes, in the sense that most of them have attributes that only make sense within the context of a PDF structure : parents objects, a cross-reference table shared between all the PDF objects, inherited attributes, etc. My first call would be to include, in a PDF object, something like a "pointer" to the common PDF structure, but I'm looking for a way to do this in Scheme without having multiple copies (one "in" each object) wandering around, especially because the shared data may be large (it's more or less the whole PDF file). I do not want to have a shared global variable, neither. Of course, there is still the option to have two args for each function on the PDF objects (one arg. for the object, one arg. for the shared PDF structure), which would, by the way, lead me to see whether that could be written in a monadic-style way in Scheme (I hope I'm clear here), but I would prefer not doing this. Do you guys know if there is a "standard" coding pattern in Scheme for that kind of situation ? (I've read Oleg's paper on pointers in SXML) Sincerely yours, Saul

Yet another question

Saul Malesac — 2008-11-25T16:36:00

Re: Package Bigloo

2008-11-24T15:56:55

Hello David, Hello Yann, Having a Debian package is, I think, very important for Bigloo. This means that although I don't have the time to maintain that package myself, I'm really willing to help as much as possible anyone who will be in charge of maintaining it. I don't know what the bugs that have conducted Bigloo to be removed from the Debian distro are. Of course, I will work to fixing them as soon as possible (the only limit is the GC that I won't fix by myself).

BUG? (Re: Question srfi-9 and Bigloo and srfi-63)

Siegfried Gonzi — 2008-11-20T08:49:48

Hello; Your idea of an f64 array class seems to be very cool. However, not sure if the following is a bug in Bigloo? == (module read-bin (static (class f64array v::f64vector dimension-x::bint dimension-y::bint))) == gives the following compile error: == *** ERROR:f64array: Illegal slot type `f64vector' -- v == The following wouldn't work either: == (module read-bin (static (class f64array v::vector dimension-x::bint dimension-y::bint))) (define a (instantiate::f64array (v (make-f64vector 9)) (dimension-x 3) (dimension-y 3))) == gives == #(a (instantiate::f64array (v (make-f64vector 9)) (dimension-x 3) (dimension-y 3))) # ^ # *** WARNING:bigloo:toplevel-init Type error -- `vector' expected, `f64vector' provided ld64: warning: option -s is obsolete and being igno == the following would work though: == (module read-bin (static (class f64array v dimension-x::bint dimension-y::bint))) (define a (instantiate::f64array (v (make-f64vector 9)) (dimension-x 3) (dimensions-y 3))) == Yhe following will also work: == (define test (a::f64vector) (print (f64vector? a))) (test (make-f64vector 4)) == Thanks, Siegfried