Displaying 6 results from an estimated 6 matches for "thell".
Did you mean:
tell
2007 Dec 17
2
[LLVMdev] PointerType API Change
...ving you the same safety properties but without having to
change all occurrences. If clients do handle address spaces, they could use
getQual(...) and getUnqual().
I don't see how this would be counter to your goals. If a module with
address spaces comes along, the pass could still abort and thell the user
that it doesn't know how to handle this, which would give users a complete
incremental upgrade path.
I know that this approach might not really encourage developers to consider
address space issues. Are they important and widespread enough that
everybody should (or is proper addre...
2007 Apr 12
1
Destar web interface problem
People, I have a Debian box with Asterisk and I've installed the Destar
package in order to get web managing of my voip system.
After I installed Destar, it runs on "localhost:8080", but my server
does not have X-Window to access to it so I can engter the web interface..
So how can I change localhost:8080 to IP_ASTERISK:8080 in order to
access Destar via web from another PC ???
2007 Dec 17
0
[LLVMdev] PointerType API Change
...ties but without
> having to
> change all occurrences. If clients do handle address spaces, they
> could use
> getQual(...) and getUnqual().
> I don't see how this would be counter to your goals. If a module with
> address spaces comes along, the pass could still abort and thell
> the user
> that it doesn't know how to handle this, which would give users a
> complete
> incremental upgrade path.
>
> I know that this approach might not really encourage developers to
> consider
> address space issues. Are they important and widespread enough...
2014 Mar 18
0
Writing R Extensions: clarification/modification request
...the extent of the R
user base but hopefully the fact that these tools and many others (
linkers, autoconf tools, etc...) have recognized, as you are doing
with R-3.1.0 and c++11 support, that times have changed and the people
have set the groundwork for best-practice and standards.
--
Sincerely,
Thell
[footnote 13]: http://cran.r-project.org/doc/manuals/r-devel/R-exts.html#FOOT13
[Package-subdirectories]:
http://cran.r-project.org/doc/manuals/r-devel/R-exts.html#Package-subdirectories
[rev at 40010]: https://github.com/wch/r-source/commit/cc84426f5b665fb0cba9945c4726348307f36831
[hpp-patch]: ht...
2007 Dec 17
0
[LLVMdev] PointerType API Change
On Dec 17, 2007, at 1:22 AM, Torvald Riegel wrote:
> Would it be possible to keep get() unchanged, with a default
> behaviour, plus
> a warning? Otherwise everybody (assuming everybody gets type void*)
> will
> have to update their LLVM passes, and either maintain two versions
> of the
> passes or require their clients to use a certain LLVM version.
AFAIK API
2007 Dec 17
2
[LLVMdev] PointerType API Change
Would it be possible to keep get() unchanged, with a default behaviour, plus
a warning? Otherwise everybody (assuming everybody gets type void*) will
have to update their LLVM passes, and either maintain two versions of the
passes or require their clients to use a certain LLVM version. Then passes
could be "address-space-safe" or not. If the default parameter value for
get() could