On 2008-Nov-1, at 01:39, Shawn Rutledge wrote:
Did you succeed yet? I just got around to trying this. qt.setup only
uses QTDIR to find qmake, so you can set QTDIR to /usr. But the
next problem is that qmake generates an XCode project rather than a
Makefile.
Actually, I made no progress
I neglected to thank Shawn for getting back to me on this! My
apologies -- v
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
On 2008-Oct-26, at 11:50, Peter Bex wrote:
It would be better to make the behaviour be system-specific, instead
of
adding flags. On Windows, *always* treat slashes as backslashes. On
Unix,
*only* accept slashes with no additional translation steps. (I'm not
sure
Windows doesn't allow
Can someone walk me through the installation of the qt egg on OS X?
I've installed the
binary distribution from Trolltech's website (qt-mac-
opensource-4.4.1.dmg). My main problem
is figuring out what to set QTDIR to, as there doesn't seem to be a
`Qt' directory as such.
Any help would be
On 2008-Aug-18, at 13:22, Graham Fawcett wrote:
On Sun, Aug 10, 2008 at 9:42 PM, Vincent Manis [EMAIL PROTECTED]
wrote:
CPython uses a Global Interpreter Lock (GIL) to implement critical
sections
in the interpreter, thus rendering native
threads in that system impossible. Some version
On 2008-Aug-10, at 11:44, Elf wrote:
NO KNOWN MULTIPLATFORM LANGUAGE IMPLEMENTATIONS HAVE WORKING NATIVE
THREADING.
NO KNOWN MULTIPLATFORM LIBRARY IMPLEMENTATIONS HAVE WORKING NATIVE
THREADING.
Seconding Elf's comments. A shared garbage-collected memory is only
one of the factors that
On 2008-Aug-9, at 04:23, Jörg F. Wittenberger wrote:
If the postulated programmer had just found mygreatprogram on the net
and want's to run it, is it a good thing for said programmer to find
chicken unable to run it until a patch is applied?
And what mygreatprogram is written in R6RS
On 2008-Aug-7, at 19:53, John Cowan wrote:
1) Run it in a separate process, which you can kill without damaging
yourself.
2) Use a modified version of eval to execute it that counts ticks.
3) Use a modified version of eval that polls for a thread termination
request.
I'd actually go
On 2008-Aug-8, at 16:30, Kon Lovett wrote:
My 2 cents.
The SRFI document is clear about the danger. The Chicken mail
archive is clear about the danger. Standards Practices is clear
about the danger.
Who are we protecting?
Well, I spent several years teaching concurrency (along with
On 2008-Aug-7, at 06:04, felix winkelmann wrote:
It must be added that `thread-terminate!' is a problematic
function: terminating a thread forcefully destroy an execution
context that doesn't necessarily expect to be terminated and
may leave any kind of system in an inconsistent state.
In fact,
On 2008-Aug-2, at 06:37, Peter Bex wrote:
Why not make irregex part of core and create a PCRE egg? That gives
us
the best of both worlds, IMHO.
+1 if irregex meets Felix's criteria of performance and reliability.
___
Chicken-users mailing list
On 2008 Apr 06, at 22:59, Elf wrote:
And as I believe I heard someone say on #scheme the other day, if
your program involves EVAL, it's probably broken. Even if the
EVAL is hidden behind something else.
This sentence makes no sense to me, as this would imply that all
programs are always
Some time ago, I posted a draft of a rework of Chapter 1 of the
manual, at
http://chicken.wiki.br/new-chapter1. A number of you made changes and
additions,
and today I made my final set of revisions, so I now declare this to be
Ready To Go.
I'm not sure of the exact mechanism for doing this,
...on srfi-29. So I'm not sure if stream-cgi and stream-wiki are in
error, or if srfi-29
mysteriously vanished from the repository.
-- vincent
___
Chicken-users mailing list
Chicken-users@nongnu.org
On 2008 Mar 12, at 20:13, Kon Lovett wrote:
Hi Vincent,
Thank you for the list. Some points:
SRFI 48 is supported except for ~W (write circular) by both the
format format-modular eggs.
SRFI 58 is supported by the array-lib egg except for the
#dimensions... form (to be released).
SRFI
On 2008 Mar 06, at 01:01, felix winkelmann wrote:
On Wed, Mar 5, 2008 at 10:09 PM, Vincent Manis [EMAIL PROTECTED]
wrote:
A couple of weeks ago, I posted a draft of a new version of Chapter
1 of
the manual, and asked for comments. There have been a few things
added,
and I think
On 2008 Mar 06, at 09:08, Ashley Bone wrote:
I'd suggest combining the paragrapsh on the MinGW/msys builds and
just noting that makefiles exist for cmd.exe and msys.
Done.
John Cowan asked what the point of having both flavors. Back when I
was doing
Windows stuff, I normally built things
On 2008 Mar 06, at 21:22, John Cowan wrote:
Quite so, which is why I'd suggest that the msys version be scrapped
and that everyone on Windows use either the cygwin or the mingw
version.
Well, I actually don't care one way or the other. I'll change the
documentation
if a consensus
My top two votes would be:
- top priority: module system, along the lines of the (still-
emerging)
ERR5RS `libraries' proposal
- polishing an `official' OO extension (maybe that's just tinyclos or
meroon or goops or ??? ...)
Just grist for the mill :-) -- v
On 2008 Feb 27, at 10:45, Graham Fawcett wrote:
... So if you're going RDBMS,
I'd pick one database and stick with it, or help write a common dbapi
framework.
This seems a meritorious project, and not very difficult (just steal the
Python API, and Scheme-ize it). Is there any interest in
On 2008 Feb 27, at 12:11, John Cowan wrote:
In reality, though, I think portability between databases is more
hypothetical than real. Projects typically start with one database
and
stick to it, for moving between databases *even if a portability layer
is in use* turns out to be hard -- all
\begin{rant}
On the subject of using void as a return value (rather than to
indicate that
a function or method doesn't return anything), E.
Please, please, don't ever write functions that return void as
anything other
than an indication that no value was returned.
#;44 (car
On 2008 Feb 26, at 16:04, Tobia Conforto wrote:
Well, the value returned by mutex-state can be either:
locked by this thread
In this case there can be no race condition, as we own
the mutex and nothing is going to take it away from us.
locked by another thread
abandoned
On 2008 Feb 25, at 00:19, Daishi Kato wrote:
Hi,
SRFI-18 states,
The mutex primitives specified in this SRFI do not implement
recursive mutex semantics; an attempt to lock a mutex that is
locked implies that the current thread must wait even if the mutex
is owned by the current thread
On 2008 Feb 25, at 17:11, Alejandro Forero Cuervo wrote:
I just wrote a Vim syntax file for svnwiki, mainly to learn how to
write a Vim syntax file :-) and to help editing Wiki pages too.
Thank you, Tobia, I can't wait to begin using it! :-)
Care to send it to the Vim-people (I don't know
On 2008 Feb 25, at 17:19, Jeremy Sydik wrote:
+1 -- There's no reason -hackers couldn't be brought back if the
need arose, right?
--Jeremy
On Feb 25, 2008, at 7:08 PM, Ivan Raikov wrote:
Cross-posting is quite annoying, I agree. Either we should
discourage cross-posting, or not use
On 2008 Feb 22, at 01:08, felix winkelmann wrote:
On Thu, Feb 21, 2008 at 11:44 PM, Ashley [EMAIL PROTECTED]
games.com wrote:
The build runs on msys with no problems. Tomorrow I plan to add
a setup for cmd.exe, so a user only needs to have gnu make installed
to build chicken for visual c.
On 2008 Feb 21, at 23:57, Alejandro Forero Cuervo wrote:
As such, I will need more convincing before implementing support for
indexentry. I don't see what it adds that we can't already do. Ok,
I see that it would allow arbitrary pages to declare sub-topics of a
given topic, but I don't think
On 2008 Feb 21, at 03:38, Alejandro Forero Cuervo wrote:
Sure, good thinking. I've created this document:
http://chicken.wiki.br/wiki-syntax-chicken
...
Suggestions would be appreciated. :-)
The page is much appreciated, and I now have a much better vision of
how the markup is
going.
I was offline for almost all of the documentation discussion, so
please pardon
my beating a somewhat dead horse. I'd like to make the following
points, which
(mostly) haven't been raised.
1. Total agreement that the first item of business is to fix the small
stuff,
and that no Grand
Just as an irrelevant data point, I happened to build the opengl egg
today on MacOS X 10.5, with the Feb 1 version of 3.0.0. It built fine,
tho so far I have only tried the gears example with it. I don't know
if that's of any interest, but I thought I'd pass it on. -- v
31 matches
Mail list logo
