search for: setf

...be addressed by this new feature. Is it possible to use new splice feature to create `6 - 5 + 4` expression rather than `6 - (5 + 4)`? b = quote(5+4) b #5 + 4 c = bquote(6-.(b)) c #6 - (5 + 4) d = bquote(6-..(b), splice=TRUE) d #6 - (5 + 4) There is corresponding LISP code provided CL-USER> (setf b `(5 + 4)) (5 + 4) CL-USER> (setf c `(6 - , at b)) (6 - 5 + 4) CL-USER> (setf c-non-spliced `(6 - ,b)) (6 - (5 + 4)) CL-USER> Thanks, Jan Gorecki

Testing version of Emacs Rails (http://rubyforge.org/projects/emacs-rails/) was released. If you have some suggestion or you find some bugs please inform us. Features: * Management of WEBrick/Mongrel * Display color log file * Toggle Switch between Action/View and other file (tests, helpers) automaticly or with menu * Switching to file from current line f.e. from redirect_to :controller =>

...o create `6 - 5 + 4` > expression rather than `6 - (5 + 4)`? > > b = quote(5+4) > b > #5 + 4 > c = bquote(6-.(b)) > c > #6 - (5 + 4) > d = bquote(6-..(b), splice=TRUE) > d > #6 - (5 + 4) > > There is corresponding LISP code provided > > CL-USER> > (setf b `(5 + 4)) > (5 + 4) > CL-USER> > (setf c `(6 - , at b)) > (6 - 5 + 4) > CL-USER> > (setf c-non-spliced `(6 - ,b)) > (6 - (5 + 4)) > CL-USER> > > Thanks, > Jan Gorecki > > ______________________________________________ > R-devel at r-project.org m...

...he implementation is slow for data objects and needs to be re-architected. The implementation for the others is more than adequate. 3) At the suggestion of Sandy Weisberg, I have incorporated PARCIL, a C-to-Lisp Parser. This allows users to type a=2*(b+c)^2 rather than the awkward lisp equivalent: (setf a (^ (* 2 (+ b c)) 2)) (I'm sorry I can't give a proper reference to PARCIL, I'm not at home). 4) Pedro Valero, Gabriel Molina, Michael Friendly and I, in various combinations, are working on the documentation problem. 5) Printing, while better than LispStat, is still not adequate. 6)...

...uot;$force_color_prompt" ]; then if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then # We have color support; assume it''''s compliant with Ecma-48 # (ISO/IEC-6429). (Lack of such support is extremely rare, and such # a case would tend to support setf rather than setaf.) color_prompt=yes else color_prompt= fi fi if [ "$color_prompt" = yes ]; then PS1=''''${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '''' else PS1=''...

...EFMACRO LSP/HELPFILE LSP/EVALMACROS LSP/LOGGING LSP/MAKEARRAY :TINY :PRE-CMP CMP/CMPSETUP CMP/CMPGLOBALS CMP/CMPVAR CMP/COMPILE-MAIN CMP/LLVM-IR CMP/EXCEPTION-HANDLING CMP/DEBUGINFO CMP/LAMBDA-LIST CMP/COMPILE-VAR-LOOKUPS CMP/CMPQUOTE CMP/COMPILER CMP/COMPILE-FILE CMP/COMPILE-BUNDLE CMP/CMPWALK LSP/SETF LSP/SETFREST LSP/LISTLIB :CMP :STAGE1 LSP/PREDLIB LSP/SHARPMACROS LSP/CMUUTIL LSP/SEQMACROS LSP/SEQLIB LSP/SEQ LSP/ASSERT LSP/DEFSTRUCT LSP/IOLIB LSP/MODULE LSP/TRACE LSP/LOOP2 LSP/PACKLIB LSP/DEFPACKAGE LSP/FORMAT :STAGE2 CLOS/PACKAGE CLOS/HIERARCHY CMP/CMPREPL CLOS/CPL CLOS/STD-SLOT-VALUE CLOS/SL...

I upgraded my versions of llvm, clang and compiler-rt to the top-of-tree versions from last night (r180162, April 24). I recompiled debug versions of llvm, clang and my code. I then regenerated my test case and the results were the same - I can list lines of dwarf1.lsp in lldb but I can't set break-points or do anything else (what else should I be able to do?). The updated file that

Hi Christian, Thanks for sharing this. Yaron Keren has been investigating some problems in the EH frame registration code recently, and I think this may be related. It at least sounds similar to the type of variations in behavior based on code size that Yaron was seeing. -Andy -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of

...d2d1: Implement d2d_d3d_render_target_FillGeometry(). d2d1: Implement d2d_geometry_sink_AddLines(). d2d1: Properly trace "vertex_count" in d2d_path_geometry_triangulate(). d2d1/tests: Don't call compare_surface() inside ok(). d2d1: Implement d2d_geometry_sink_SetFillMode(). d2d1: Implement initial support for drawing bezier curves. d2d1: Add some FIXMEs for unimplemented functionality to d2d_d3d_render_target_DrawGlyphRun(). d3d10core: Implement d3d10_device_CopySubresourceRegion(). d2d1: Add a missing TRACE to d2d_d3d_render_target_F...

I switched my Common Lisp compiler to use MCJIT on the weekend and ran into a weird problem compiling one particular function. It crashes with an EXC_BAD_ACCESS error in MCJIT::finalizeObject when calling processFDE. The weird part is that the function does not appear to do anything special and I've whittled it down to the minimum size that still causes the crash. If I remove even one