> On Dec 27, 2017, at 19:57, Justin Zamora wrote:
>
> There are many characters that have different Unicode values but use the same
> glyphs. Many Cyrillic characters look like their English characters, so they
> appear the same visually, but equal? and eq? reveal that they are actually
> di
If I wanted to build a drag-and-drop, visual programming interface for
programming in DrRacket, is there any prior work I can build on? Ideally,
I'd like to implement this as a DrRacket "snip", so that my students can
make programs that are partially text-based and partially visual. Any
sugge
There are many characters that have different Unicode values but use the
same glyphs. Many Cyrillic characters look like their English characters,
so they appear the same visually, but equal? and eq? reveal that they are
actually distinct. It seems to be that the BOM is just another example on
this
(Interned) symbols that have the same printed form but are not equal
to each other already exist tho; the symbols produced by
string->unreadable-symbol are not equal? to their counterparts
produced by the reader, but nevertheless have the same printed
representation.
Shu-Hung
On Wed, Dec 27, 2017
Okay. I think I understand.
The behavior of "two things print the same but are actually different"
that Racket has seems to be the same as my editor and Web browser
which don't render the BOM as anything unless I fiddle something in
Emacs. Additionally, it seems painful to make it do it a differen
> On Dec 27, 2017, at 19:06, Jay McCarthy wrote:
>
> This seems to be consistent with my Web browser and editor. Are the
> symbols eq? or equal?
Neither. Am I misunderstanding you? Here’s code:
#lang racket
(define bad-symbol (string->symbol "\uFEFFhello"))
(define regular-symbol 'hello)
b
This seems to be consistent with my Web browser and editor. Are the
symbols eq? or equal?
On Wed, Dec 27, 2017 at 3:54 PM, 'John Clements' via Racket Users
wrote:
> I was working with files containing a Byte Order Mark today, and in the
> process of writing a test case, I discovered that
>
> (st
I was working with files containing a Byte Order Mark today, and in the process
of writing a test case, I discovered that
(string->symbol “\uFEFF”)
produces a symbol whose printed representation is
‘hello
… which seems unfortunate; I guess I would have expected something like
‘|\uFEFFhello|
I don't have much to add but wanted to note that the problem appears to be
in rendering grengor's documentation. The package itself may be installed
fine, just not its associated documentation. You can test to verify if
package is installed by querying via raco pkg or just requiring gregor in a
9 matches
Mail list logo
