-
```
As described in issue 19, the current implementation of dynamic data won't work
in windows because it relies on:
* from sys/mman.h: mmap(), munmap()
* from unistd.h: close()
These header files…
-
```
As described in issue 19, the current implementation of dynamic data won't work
in windows because it relies on:
* from sys/mman.h: mmap(), munmap()
* from unistd.h: close()
These header files…
-
```
As described in issue 19, the current implementation of dynamic data won't work
in windows because it relies on:
* from sys/mman.h: mmap(), munmap()
* from unistd.h: close()
These header files…
-
```
As described in issue 19, the current implementation of dynamic data won't work
in windows because it relies on:
* from sys/mman.h: mmap(), munmap()
* from unistd.h: close()
These header files…
-
```
There are many uses of the "new" operator in the CLD source code, such as in
scoreonescriptspan.cc's "new ScoringHitBuffer":
https://code.google.com/p/cld2/source/browse/trunk/internal/scoreones…
-
Originally reported on Google Code with ID 27
```
There are many uses of the "new" operator in the CLD source code, such as in scoreonescriptspan.cc's
"new ScoringHitBuffer":
https://code.google.com…
ghost updated
2 years ago
-
```
As described in issue 19, the current implementation of dynamic data won't work
in windows because it relies on:
* from sys/mman.h: mmap(), munmap()
* from unistd.h: close()
These header files…
-
```
As described in issue 19, the current implementation of dynamic data won't work
in windows because it relies on:
* from sys/mman.h: mmap(), munmap()
* from unistd.h: close()
These header files…
-
```
What steps will reproduce the problem?
1. try to detect the language of attached input file
2. see the output is "unknown"
What is the expected output? What do you see instead?
I would expect eit…
-
```
As described in issue 19, the current implementation of dynamic data won't work
in windows because it relies on:
* from sys/mman.h: mmap(), munmap()
* from unistd.h: close()
These header files…