I have a use of regular expressions where I need the "atomic" matching
features that I can get for several other languages, such as atomic
matching groups and "possessive" quantifiers. I'm willing to forego the
blazing performance of Go's standard library dfa matcher for this
particular case. I
I never have understood the *serious* hatred of Python's "indentation as
syntax" approach. I've used lots of bracketed and begin/end languages
(C/C++, Algol & relatives, Ruby, and most other programming languages), and
when I write code in those languages I usually indent as I write.
Obviously,
t;> Given the writing on the wall that GOPATH is going away, what I have
>>>>> done is created a single module where I keep all my own code, each
>>>>> different experiment in its own subdirectory. I named it "
>>>>> github.com/...", bu
e.
>
> On Feb 25, 2021, at 3:08 PM, Bob Alexander wrote:
>
>
> GOPATH mode does *not *limit your Go code to a single directory. I've
> seen this misunderstanding stated in probably hundreds of various posts.
>
> $GOPATH allows specification of multiple directories.
GOPATH mode does *not *limit your Go code to a single directory. I've seen
this misunderstanding stated in probably hundreds of various posts.
$GOPATH allows specification of multiple directories. I've used that
capability for several years to distribute my Go code to my personal
general library
inevitable short delay *only* in
the less common case.
On Sun, Aug 16, 2020 at 11:27 AM Bob Alexander wrote:
> Note that the "retry loop for deleting the executable" technique has zero
> wait time if the delete succeeds.
>
> A year or so ago I submitted a bug report because I h
few times that
it is necessary.
On Sat, Aug 15, 2020 at 9:31 AM Bob Alexander wrote:
> Here's what I think is really going on:
>
> At the end of a process's execution, 2 things happen:
> - The process's code finishes its execution -- wait returns.
> - The OS closes the execut
Here's what I think is really going on:
At the end of a process's execution, 2 things happen:
- The process's code finishes its execution -- wait returns.
- The OS closes the executable file.
The second item always "comes after" the first. On Windows the delay might
be a few milliseconds,
