Displaying 20 results from an estimated 397 matches for "lexing".
Did you mean:
vexing
2009 Nov 17
3
gem install rails - errors MAC OSX (snow leopard)
This produced quite a mouthful of text.
I''m stuck on the error messages and wondering if I messed something
up. Any advice would be very appreciated. Thank you.
dust:~ Lex$ gem install rails
WARNING: Installing to ~/.gem since /Library/Ruby/Gems/1.8 and
/usr/bin aren''t both writable.
WARNING: You don''t have /Users/Lex/.gem/ruby/1.8/bin in your PATH,
gem executables
2006 Sep 25
5
HTTP Parser (Regal)
Hi I was interested to see how Mongrel uses Lex/Yacc to parse the HTTP
requests using a Regal generated parser. I downloaded the source but do
not see the lex and yacc files...
2006 Mar 08
3
Multiple logistic regression
Dear R-users,
Is there a function in R that classifies data in more than 2 groups using
logistic regression/classification? I want to compare the c-indices of
earlier research (lrm, binary response variables) with new c-indices
obtained from 'multiple' (more response variables) logistic regression.
Best regards,
Stephanie Delalieux
Department Biosystems
M?-BIORES
Group of Geomatics
2010 Jun 21
2
[LLVMdev] MC: Object file specific parsing
...unsigned SyntaxVariant,
@@ -235,12 +240,15 @@ namespace llvm {
/// createAsmParser - Create a target specific assembly parser.
///
+ /// \arg Triple - The target triple string.
/// \arg Parser - The target independent parser implementation to use for
/// parsing and lexing.
- TargetAsmParser *createAsmParser(MCAsmParser &Parser) const {
+ AsmParser *createAsmParser(const std::string &Triple, SourceMgr &SM,
+ MCContext &Ctx, MCStreamer &Out,
+ const MCAsmInfo &MAI) const {...
2008 Jun 13
5
Installing a .msp patch
On Thursday 12 June 2008 18:03:10 wine-users-request at winehq.org wrote:
> DO NOT RUN WINE AS ROOT. ?By running Wine as root, you have damaged your
> wine install. ?This is in the FAQ.
> http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014
>
> You'll need to fix your ~/.wine first before you can do anything else.
>
2006 Jan 20
1
error on compiling wine 0.9.6 on fedora core 4 - wine 0.9.5 works!
gcc -g -O2 -o widl client.o hash.o header.o proxy.o server.o typegen.o
typelib.o utils.o widl.o write_msft.o parser.tab.o lex.yy.o -L../../libs
-lwpp -lwine_port -lfl
../../libs/libwpp.a(lex.yy.o)(.text+0x5e8): In function
`_yy_dummy_uses_of_static_functions_b2f4_517d_02ff_b30c_3e5a_47d7_aaa3_3b5d_':
/usr/local/rpm/wine-0.9.6/libs/wpp/lex.yy.c:3357: multiple definition of
2001 Apr 19
0
lex error building on Solaris 8
I get the following error when attempting to build wine 20010326 on
Solaris 8, MU3
./tools/wineinstall
...
cd `dirname winebuild/__depend__` && make depend
../../tools/makedep -I. -I. -I../../include -I../../include -C.
import.c main.c parser.c relay.c res16.c res32.c spec16.c
spec32.c utils.c -C.
cd `dirname wmc/__depend__` && make depend
../../tools/makedep -I. -I.
1997 Dec 05
2
lex, yacc
Hi there!!
Can someone tell me where I can find 'supported' lex and yacc
utilities that work on NT?
Pardon me if this question is not relevant in this list..
Please send me the replies directly to my e-mail
'k.sundram@blr.sni.de' ; since I find that this list
is getting bigger and better..
Thanx in advance
K R Sundaram
--
************************************************
*****
2011 Jan 19
2
[LLVMdev] Building 176.gcc
Hi folks,
I have been stumped on a compilation problem when I tried to build
176.gcc of SPEC CPU2000 with clang v 2.8 (trunk 427) on Linux and intel.
First, I tried to compile with 'clang -std=c89 *.c -o gcc.clang' since
the default C standard of Clang is c99 while that of gcc is c89. It
reported this error:
./c-gperf.h:14:1: error: unknown type name 'inline'
inline
^
2007 May 23
2
about lex/yacc
hello,
what about these functions lex/yacc which can parse and recognize a syntax?
thanks
_____________________________________________________________________________
[[alternative HTML version deleted]]
2007 Sep 23
7
v1.1.beta1 released
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz.sig
Alpha6 seemed to finally work quite well, so I think it's time for a
feature freeze (except for dbox changes).
I started a new wiki page to list incompatibilities between v1.0 and
v1.1: http://wiki.dovecot.org/Upgrading/1.1
Fixes since alpha6:
- deliver + maildir
2007 Sep 23
7
v1.1.beta1 released
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz.sig
Alpha6 seemed to finally work quite well, so I think it's time for a
feature freeze (except for dbox changes).
I started a new wiki page to list incompatibilities between v1.0 and
v1.1: http://wiki.dovecot.org/Upgrading/1.1
Fixes since alpha6:
- deliver + maildir
2012 Jun 28
4
Optimizing grep, sort, uniq for speed
This snippet of code pulls an array of hostnames from some log files.
It has to parse around 3GB of log files, so I'm keen on making it as
efficient as possible. Can you think of any way to optimize this to
run faster?
HOSTS=()
for host in $(grep -h -o "[-\.0-9a-z][-\.0-9a-z]*.com" ${TMPDIR}/* |
sort | uniq); do
HOSTS+=("$host")
done
2014 Nov 12
2
[LLVMdev] Increase the flexibility of the AsmLexer in parsing identifiers.
...get's assembly syntax has this fancy characteristic
where different operands are separated by '$' (dollar) like in:
add r0$5$r3
The default AsmLexer would lex the entire r0$5$r3 as a single "Identifier"
and it is not possible to Lex every operand separately , but some custom
lexing logic must be applied over the returned "Identifier" Token to split
and recognize each of the operands.
This is a stupid example, but there are other cases where something similar
happens and can be a hassle to deal with, because what an Identifier is
entirely dependent from some arbitra...
2011 Jan 19
0
[LLVMdev] Building 176.gcc
On 01/18/2011 06:38 PM, Bin Zeng wrote:
> Hi folks,
>
> I have been stumped on a compilation problem when I tried to build
> 176.gcc of SPEC CPU2000 with clang v 2.8 (trunk 427) on Linux and intel.
> First, I tried to compile with 'clang -std=c89 *.c -o gcc.clang' since
> the default C standard of Clang is c99 while that of gcc is c89. It
> reported this error:
>
2006 May 08
2
have any one tried Snmp extension to Net-SNMP daemon
Dear all,
I am looking for a way for creating a gui for managing qos in linux ,
i came across snmp extension to net snmp at
http://x-ray.prokon.cz/data/snmp/
and i found qosd-0.0.1-13122003.tgz ,
in which there is a client server program using soap which was realy intresting but when i tried to compile it ended up with many errors ,,
does and one have tried it , or have
2004 Feb 26
2
winbind and unix/nt login match use unix uid
Hi,
I'm on solaris 9, and using winbind to be a part of our NT domain.
I'm trying to determine if it's possible to configure winbind/smb so
that when the nt login name matches the unix login name the share is
mounted using their unix uid. With none matching account names,
username map works fine. It doesn't appear that "johnsmith =
johnsmith" works in the username map
2008 Sep 30
1
Quantile Regression for Longitudinal Data. Warning message: In rq.fit.sfn
Hi,
I am trying to estimate a quantile regression using panel data. I am trying
to use the model that is described in Dr. Koenker's article. So I use the
code the that is posted in the following link:
http://www.econ.uiuc.edu/~roger/research/panel/rq.fit.panel.R
While this code run perfectly, it does not work for my data providing a
warning message:
In rq.fit.sfn(D, y, rhs = a) : tiny
2008 Jun 12
2
How to install a .msp?
I am trying to install a WordPerfect Service Pack, the file is a .msp format.
Wine does nothing with it.
When I try: msiexec /p "etc" I get the following from the terminal:
root at Icarus:~# msiexec /p /media/disk/WordPerfect12/WP12SPEN.msp
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Application tried to create a window, but no driver could
2017 Jan 27
2
Linking Linux kernel with LLD
> Hmm..., the crux of not being able to lex arithmetic expressions seems to
> be due to lack of context sensitivity. E.g. consider `foo*bar`. Could be a
> multiplication, or could be a glob pattern.
>
> Looking at the code more closely, adding context sensitivity wouldn't be
> that hard. In fact, our ScriptParserBase class is actually a lexer (look at
> the interface; it