Hello,
thank you very much. I read that line, but I couldn't figure out what the
"symbol-appending the write form of a submodule path ..." would look like. I
tried xsub and x-sub and searching the documentation, but couldn't find it.
Thanks again,
Bert
> From: mfl...@cs.utah.edu
> To: bed..
>From a sheer PL research and design perspective, our module
system is fantastic. From a disciplined approach to SE, it
lacks (1) tool support (show me all exports, their contracts, etc)
and/or (2) linguistic support for disciplined exports such as
the (wonderful) suggestion you came up with fo
Sorry for the long delay! I hope this answer is still useful.
Buried in the very long documentation for `create-embedding-executable`
is the note
When submodules are available and included, the submodule is given a
name by symbol-appending the write form of submodule path to the
enclosing modu
Now that we have packages, they provide a natural boundary. The
relative placement of files from different packages shouldn't matter,
since packages don't have a fixed installation location relative to
each other. So, I've changed `raco distribute` to preserve relative
locations only among files fr
Yes!
On Wednesday, April 30, 2014, Matthew Flatt wrote:
> It would make sense for a document to be accompanied by a library that
> exports the document's module path and tag names, so that the path and
> tags could change. Even better, the module could export `secref`-like
> functions to refer t
>> The reason is because certain Strings can't be represented in the Text
>> node of XML documents. We ran across this problem in practice when
>> students started writing programs and copying and pasting content from
>> the web, which introduced characters like vertical tabs and other
>> characte
I've written 75% of a patch for this, so hopefully we'll have it soon.
Sam
On Wed, Apr 30, 2014 at 4:50 PM, Matthew Flatt wrote:
> I think `prop:object-name` would be a good addition, but it doesn't
> exist right now.
>
> At Wed, 30 Apr 2014 16:35:06 -0400, "Alexander D. Knauth" wrote:
>> What d
To digress
> The reason is because certain Strings can't be represented in the Text
> node of XML documents. We ran across this problem in practice when
> students started writing programs and copying and pasting content from
> the web, which introduced characters like vertical tabs and other
>
I think `prop:object-name` would be a good addition, but it doesn't
exist right now.
At Wed, 30 Apr 2014 16:35:06 -0400, "Alexander D. Knauth" wrote:
> What do you mean? I tried it and it didn’t affect the object-name.
>
> And what I’m looking for is something that could be different for diffe
What do you mean? I tried it and it didn’t affect the object-name.
And what I’m looking for is something that could be different for different
instances of the same structure type, for example:
(struct thing (name) #:property prop:object-name (struct-field-index name))
(struct proc-with-strin
> XML is harder for almost everyone to deal with than JSON is. Sometimes it
> seems like almost no one designing XML schemas (mainly ad-hoc) uses XML in a
> way more sophisticated than they'd use JSON. And XML has a bunch of
> overbearing baggage. I only use XML when it's required by legacy
> in
Alejandro Zamora Fonseca wrote at 04/30/2014 09:08 AM:
Well I want to write a game for programmers that listen input for
programs written in any language, I'm still in the "general" modeling
phase, but I think the I/O would be based in XML and/or JSON.
If you want it most easily usable from We
It would make sense for a document to be accompanied by a library that
exports the document's module path and tag names, so that the path and
tags could change. Even better, the module could export `secref`-like
functions to refer to various sections of the document, where the
functions map to the
Yes, that sounds right to me.
At Wed, 30 Apr 2014 11:09:54 -0700, Matthew Butterick wrote:
> Seems like the most straightforward way would be to expose cross-reference
> hooks within the rendered docs themselves. So when you find something you
> want
> to cross-reference, you can immediately cl
Well I want to write a game for programmers that listen input for programs
written in any language, I'm still in the "general" modeling phase, but I think
the I/O would be based in XML and/or JSON.
So, thanks for the advices.
Best regards
Alejandro
Good, glad to hear it works.
If you can av
At Wed, 30 Apr 2014 22:23:25 +0400, Dmitry Pavlov wrote:
> > Assuming so, could you look for "rUnTiMe-paths" in the initial ".exe"
> > and the distribution ".exe" to try to tell whether the strategy of
> > using a fixed number of additional "."s is really enough?
>
> I did not notice anything p
Good, glad to hear it works.
If you can avoid dealing with raw sockets and use a standard protocol
for communication, that might allow you to write your network code at
a nicer level of abstraction. What kind of network application are
you trying to write?
In retrospect, perhaps that should have
Matthew,
> You can make things work by changing "collects/compiler/embed.rkt" to
> replace #"." with more than 17 dots.
Thank you! I put extra three dots, and all went well.
> Assuming so, could you look for "rUnTiMe-paths" in the initial ".exe"
> and the distribution ".exe" to
Thanks a lot!
Finally it works for my purposes.
greetings
Alejandro
> Thanks, with sendall it works nicely.
> But when I try the reverse flow(that is, Racket to Python) making:
> ;...
> (display "Hello" s-out)
> ;or with 'print
> Python doesn't read with
> > > >
> > > > recv(500)
>
> it locks th
Seems like the most straightforward way would be to expose cross-reference
hooks within the rendered docs themselves. So when you find something you want
to cross-reference, you can immediately click & pick up the information you
need to embed that cross-reference into your own .scrbl source.
I think we are discovering a weakness in our language-oriented programming
approach.
Scribble benefits from linguistic inheritance from modules but our interface
story for modules is under-developed. We don't write down provides for sections
and their references, which we should if others sho
Does the #:extra-constructor-name keyword argument to struct do what you're
looking for?
On Apr 29, 2014 9:31 PM, "Alexander D. Knauth" wrote:
> I’m just curious is there something like a prop:object-name that the
> object-name function would use when returning the object name of a struct
> with
--
CALL FOR TALK PROPOSALS
HOPE 2014
The 3rd ACM SIGPLAN Workshop on
Higher-Order Programming with Effects
August 31, 2014
23 matches
Mail list logo
