Re: [racket] serializable structs and portability

2011-03-29 Thread Eric Tanter
In the meantime I figured out that the structures that were defined not in main.rkt file but in another one got serialized properly. So I moved all definitions in a separate file, and now it works. (running from DrRacket) ((2) 5 (((lib "bibdcc/structs.rkt") . deserialize-info:order-v0) ((lib "

Re: [racket] serializable structs and portability

2011-03-29 Thread Matthew Flatt
Are you starting the program by running "main.rkt" in DrRacket or with something like racket main.rkt [in the "bibdcc" directory] ? If so, do you get a different result using racket -l bibdcc ? At Tue, 29 Mar 2011 14:16:33 -0400, Eric Tanter wrote: > Sorry I still don't get it. > > Her

Re: [racket] serializable structs and portability

2011-03-29 Thread Eric Tanter
Sorry I still don't get it. Here's what I've tried: - moved my application files to the user collects directory of my system. - made the proper dir/subdir structure - use only (require myapp/mod1) kind of requires (It works ok) Now if I serialize some structures in a file, they still get absolu

Re: [racket] serializable structs and portability

2011-03-28 Thread Matthew Flatt
At Mon, 28 Mar 2011 18:28:02 -0400, Eric Tanter wrote: > I'm not sure I understand what you mean by "collection-based library". > > The structs are part of an app I'm building from scratch. > For now I have a couple of .rkt files, some of which define the structs in > question, and I import them

Re: [racket] serializable structs and portability

2011-03-28 Thread Eric Tanter
I'm not sure I understand what you mean by "collection-based library". The structs are part of an app I'm building from scratch. For now I have a couple of .rkt files, some of which define the structs in question, and I import them in the main module with (require "foo.rkt"), etc. Suggestions?

Re: [racket] serializable structs and portability

2011-03-28 Thread Matthew Flatt
At Mon, 28 Mar 2011 17:36:22 -0400, Eric Tanter wrote: > I'm playing with serializable structs and noticed that the absolute path of > the source rkt definition is inserted in the representation (I'm writing > structs out to a file). > The problem is that if I then move my application to a serve

[racket] serializable structs and portability

2011-03-28 Thread Eric Tanter
Hi, I'm playing with serializable structs and noticed that the absolute path of the source rkt definition is inserted in the representation (I'm writing structs out to a file). The problem is that if I then move my application to a server for deployment, all serialized structs cannot be deseri