Interaction showing the problem
$ guile
GNU Guile 2.2.6
Copyright (C) 1995-2019 Free Software Foundation, Inc.
Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c'
Excellent, and thank you all! I've been WIndowsless for a few weeks, but
that should change again soon.
On Sun, Feb 16, 2020 at 6:23 PM Mike Gran wrote:
> On Fri, Feb 14, 2020 at 09:46:04AM -0800, Charles Stanhope wrote:
> > Andy, I don't know if you'd want to continue this here or on
> > light
On Mon, Feb 3, 2020 at 5:11 PM szgyg wrote:
On Fri, Jan 31, 2020 at 09:23:19AM -0500, John Cowan wrote:
> > Aaaand... Cygwin doesn't do core dumps. Under the skin it's WIndows,
> after
> > all. This is what I get when I specify ulimit -c unlimited and rebuild:
&g
0\libguile\.libs\guile.exe,
pid 62833, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
I can't imagine what you can make of that.
On Sat, Jan 25, 2020 at 10:54 AM John Cowan wrote:
>
>
> On Sat, Jan 25, 2020 at 8:51 AM Ludovic Courtès wrote:
>
>
>> That I un
which I barely understand.
"All problems are config problems."
John Cowan http://vrici.lojban.org/~cowanco...@ccil.org
We are lost, lost. No name, no business, no Precious, nothing. Only empty.
Only hungry: yes, we are hungry. A few little fishes, nassty bony little
fis
readline.la
Undefined symbols for architecture x86_64:
"_rl_get_keymap_name", referenced from:
_scm_init_readline in readline.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
On Thu, Jan 23, 2020
I'm no longer talking about Cygwin (which builds fine without JIT). I'm
now talking about MacOS Catalina, which needs a core dump to debug, but on
which nobody seems to know how to enable core dumps.
On Tue, Jan 21, 2020 at 1:41 PM szgyg wrote:
> On Tue, Jan 21, 2020 at 10:01:58AM +0100, Ludovi
SIGSEGV on
running processes and no dumps appear in /cores.
On Tue, Jan 21, 2020 at 4:02 AM Ludovic Courtès wrote:
> Hello,
>
> John Cowan skribis:
>
> > Yes, gladly, but I don't know how to get one in this context.
>
> You would unpack, configure, and build like you d
Elisp symbolp does not think nil is a symbol, which it is in Emacs Elisp.
Fixing this should not affect Scheme's symbol? predicate.
The writer in modules/language/elisp/spec.scm specifies Scheme's write as
the REPL writer, so that entering nil at the Elisp prompt prints out #nil,
which is meaningless to Elisp users. Likewise, (print nil) does the same
thing. A proper Elisp writer is needed.
Yes, gladly, but I don't know how to get one in this context. Do I need to
add some flags to the Makefile, and if so, where? (It's a twisty maze of
passages, all different.) . Note that this *is* a build with JIT enabled;
when I disable it using the env variable, there are no errors and 3.0.0
wor
Okay, with GUILE_JIT_THRESHOLD set to -1 in the environment, I can build
Guile under Cygwin. There are two test failures which probably reflect
differences between newlib and glibc:
ERROR: time.test: strptime: GNU %s format: strftime fr_FR.utf8 - arguments:
((system-error "strptime" "~A" ("Invali
/guile-2.9.9'
make: *** [Makefile:1735: all] Error 2
All previous problems (which were easy to work around) have gone away in
this release, which is progress, but it doesn't get me past Guile 2.2.
John Cowan http://vrici.lojban.org/~cowanco...@ccil.org
Your worships wil
While I esteem Marc's work highly, I have to say that his message above is
incomplete and tendentious. He links to SRFI 150, written by him, in which
he links to a message by Alex Shinn (R7RS-small editor and Chibi
implementer) in support of this view. This is a single message in the
thread <
htt
That makes three different operating environments exposing this exact build
failure: MacOS, Cygwin, Ubuntu Xenial.
On Sat, Dec 14, 2019 at 1:17 AM Aleix Conchillo Flaqué
wrote:
> Hi there!
>
> Trying to build 2.9.7 on OS X and getting the error below.
>
> I'd be happy to try more things if you
should not be a character. You nowhere state what purpose such a read
syntax would serve. Do you wish to be able to use read to input a list of
EOF objects, for instance? What would you do with them?
John Cowan http://vrici.lojban.org/~cowanco...@ccil.org
Pour moi, les villes du
On Sat, Nov 16, 2019 at 3:42 PM Andy Wingo wrote:
> The expected result is "μέλοσ"; see R6RS libraries section 1.2. However
> instead Guile's result is "μέλος". Note that although Σ usually
> downcases to σ, at the end of a string it's ς.
More precisely, it downcases to σ if a letter follows
I don't see where the incompatibility comes in, although more lookahead
would be required. Per the Guile documentation, neither #n# nor #n= (where
n is a sequence of digits) is a valid array tag.
On Sat, Nov 16, 2019 at 3:50 PM Andy Wingo wrote:
> R7RS defines a lexical feature called "datum la
bly not directly relevant. I'd appreciate review comments at
co...@ccil.org anyway. Thanks.
John Cowan http://vrici.lojban.org/~cowanco...@ccil.org
Is a chair finely made tragic or comic? Is the portrait of Mona Lisa
good if I desire to see it? Is the bust of Sir Philip Crampt
n-us/windows/desktop/api/Winnls/nf-winnls-enumcalendarinfoexex>,
and the constants that specify particular pieces of information at <
https://docs.microsoft.com/en-us/windows/desktop/Intl/calendar-type-information>.
(I have never used these interfaces myself.)
I hope this is he
That's a mug's game: I've been there and tried it (not in Scheme). I
recommend writing a strftime in Scheme from scratch. It's not that hard;
the most annoying thing is getting into the locale files to handle the
locale-sensitive directives (month name, weekday name, AM/PM, and the
ordering of dat
t; namespace declarations would not apply? (e.g. documents with a PI
> element and two separate XML trees)
>
That's not well-formed: you can only have a single element tree per XML
document, although you can have any number of PIs, comments, and
whitespace (which is nor
dmit that I'm not an expert on time
> >standards,
>
> I am.
>
He is.
--
John Cowan http://vrici.lojban.org/~cowanco...@ccil.org
There is no real going back. Though I may come to the Shire, it will
not seem the same; for I shall not be the same. I am wounde
+
So as you see leap seconds are included in both the TAI and the UTC count,
but not in the Posix count.
--
John Cowan http://vrici.lojban.org/~cowanco...@ccil.org
I could dance with you till the cows com
tra seconds have no
> > representation in time-utc. They only have representations in time-tai
> > and time-monotonic.
>
Same story. Leap seconds have no representation in Posix time, but they
do in UTC time.
> As you can see, 1973-12-31T23:59:60Z and 1974-01-01T00:00:00
long time
> periods, with the leap seconds taken into account, UTC seconds are equal
> to UT seconds.
>
No, in the long run UTC time is equal to UT1 time. That's not the same
thing at all.
--
John Cowan http://vrici.lojban.org/~cowanco...@ccil.org
I am expressing
in a slightly different way to UTC, but they have little meaning for
TAI.
--
John Cowan http://vrici.lojban.org/~cowanco...@ccil.org
"Mr. Lane, if you ever wish anything that I can do, all you will have
to do will be to send me a telegram asking and it will be do
On Mon, Oct 22, 2018 at 1:54 AM Mark H Weaver wrote:
> This means that TAI-UTC = 4.2131700 + (MJD - 39126) * 0.002592, where
> MJD is the modified julian day of the desired TAI-UTC delta. In this
> case, the MJD (modified julian day) of midnight UTC January 1, 1970 is
> 40587, and plugging that
a UTC clock, never for a Posix
clock.
This error is repeated in a number of your later messages, but I'll respond
only to this one.
--
John Cowan http://vrici.lojban.org/~cowanco...@ccil.org
Tautology is something that is tautological. --Francois-Rene Rideau
What is more, there are no TAI<->UTC conversion tables from before 1961
(when UTC began) and probably never will be. There was heated debate in
the R7RS-small working group, and we finally settled on a compromise:
(current-second) [r]eturns an inexact number representing the current time
on the I
se does and ignore the issue in
JIS-based encodings, of which Shift_JIS is the only one in practical use
(and it _is_ heavily used in Japan, where it is almost the only encoding
for documents on desktops). Just ignoring the encoding is not an option
in Japan: see the comments by Joel Rees, Norman Di
;Salem")
> (cons "Florida" "Miami")))
>
More simply, you can wrap the literal in a call to copy-tree. This returns
a deep copy of the literal that is fully mutable.
--
John Cowan http://vrici.lojban.org/~cowanco...@ccil.
The error is valid, because you are attempting to mutate a program
literal. Scheme makes that an error, and Guile enforces it (though many
Schemes do not).
On Tue, Sep 25, 2018 at 4:41 PM Hood, Christopher L. <
christopher.h...@gtri.gatech.edu> wrote:
> This fails with code pulled straight out o
Indeed, I pretty much only go into vi-mode in vi itself to use %; the rest
of the time, I remain an "ex" troglodyte whose only vi-commands are h, j,
k, l (and arrow analogues), x, %, and most importantly gQ. Yes, even when
writing Lisp.
On Thu, Aug 23, 2018 at 12:05 AM Mark H Weaver wrote:
> Hi
34 matches
Mail list logo
