It sounds like it's mostly a backwards-compatibility issue. So when
teaching students from scratch about regular expressions, is it
reasonable to only mention pregexps? Is there anything lost by doing
that?
_
For list-related administrative tasks:
Begin forwarded message:
> From: Tobias Wrigstad
> Date: November 2, 2010 7:20:51 PM EDT
> To: ea...@jiscmail.ac.uk
> Subject: STOP'11 CFP -- Extended Deadline Nov 8th
> Reply-To: Tobias Wrigstad
>
> Deadline extended to Nov. 8th
>
> Call for Papers
5 minutes ago, Mark Engelberg wrote:
> As far as I can tell, pregexp functionality is a superset of regexp
> functionality. Furthermore, the added functionality uses patterns
> that are unlikely to occur by accident in normal regular
> expressions. So is there any advantage to using regexp over
>
It would be a significant amount of work to remove regexps because
there is a lot of code that uses them that would have to be rewritten.
In the cases where a literal regexp is used, one could probably write
a script to make it work, but cases where the function 'regexp' was
used would probably all
As far as I can tell, pregexp functionality is a superset of regexp
functionality. Furthermore, the added functionality uses patterns
that are unlikely to occur by accident in normal regular expressions.
So is there any advantage to using regexp over pregexp? Why is there
a need for both to coexi
Try just using frame:standard-menus% in place of frame%. You will need
to change the parents of any panels you create from the frame to the
result of calling the get-area-container method (you'll get an error
that points you in the right direction).
That may not be exactly all of the right menus,
Hi,
I have made a lambda function that draws a frame with several panels. Now,
I've been trying to figure out how to embed DrRacket's GUI/functionality
inside one of these panels, so I could show/hide it as needed. The way
DrRacket gathers all bits and mixins in the initializing process, seems
ov
Thanks Noel - the scale would be meters rather, but I somehow assumed that this
might be too small-scale for GPS ...
I guess I really ought to compare both measures, but for the GPS part, I wonder
what would be the most "architecturally adequate" way to adapt 'world-updater'
s contract to handl
I don't /really/ know, but isn't one reading from the accelerometer
and the other from GPS? The answer depends, I think, on the distance
over which you want to operate. If you want velocity from, e.g., hand
movements, the accelerometer is the way to go. If you want velocity
over large scale (metres
On Nov 1, 2010, at 6:55 PM, Harry Spier wrote:
>
>
> Dear list members,
>
> Can someone direct me to where in the documentation there is a list of the
> language identifiers i.e. what I put after #lang in the upper panel in
> DrRacket for the various languages recognized by DrRacket, in part
Ha, but for all we know, his solution is buggy!
On Nov 2, 2010 12:49 PM, "Nadeem Abdul Hamid" wrote:
Please don't post solutions to problems on the public mailing list. I
just assigned this problem to my students this past week and it's
rather annoying to have the solution easily available on th
Dear list members,
Can someone direct me to where in the documentation there is a list of the
language identifiers i.e. what I put after #lang in the upper panel in DrRacket
for the various languages recognized by DrRacket, in particular for the
teaching languages. Or list them in the list f
Hi,
I am wondering how best to calculate velocity in a moby/phonegap/android
application.
In general, would anyone have experience (or intuition) whether velocity might
better be calculated from the acceleration values delivered by phonegap's
Acceleration object, or directly be extracted from t
Please don't post solutions to problems on the public mailing list. I
just assigned this problem to my students this past week and it's
rather annoying to have the solution easily available on the public
group page!
Thanks,
--- nadeem
On Tue, Nov 2, 2010 at 11:57 AM, Sam Griff wrote:
> Here is my
Here is my solution to a modified version of DNAprefix from exercise
17.6.6. I feel like it *should* be able to be written more
clearly/simply but I can't think of the logic to make it work properly:
Modify |DNAprefix| so that it returns the first item beyond the pattern
in the search-string i
15 matches
Mail list logo
