search for: poignant

Displaying 20 results from an estimated 37 matches for "poignant".

2007 Jan 23
7
RedCloth and SuperRedCloth
...to the parliament of RedCloth followers gathered here. Grave matters at hand!! I''m personally quite unhappy with the state of RedCloth and am reluctant to release the code in the repository. I can''t say if the code works with any confidence because I can''t generate the (Poignant) Guide with the current RedCloth. I know some things are fixed, but I''m afraid that much is still broken. I think I''d rather re-release 3.0.3 as 3.0.5, you know? So, my first question is: what to do with the RedCloth 3.x series?? --- The next pressing item is SuperRedCloth.[1...
2009 Dec 17
2
[LLVMdev] updated code size comparison
...s > miscompiled on GCC 3.4 and SunCC 5.10. Yeah, there are definitely several examples where small code is generated by miscompilation, especially of volatiles. However I would prefer to leave these testcases in, unless there is a strong feeling that they are too distracting. They serve as poignant little reminders about how easy it is to get volatile wrong... John
2006 Apr 09
7
The search on this forum should improve to improve the forum
The search on this forum should improve to improve the forum -- Posted via http://www.ruby-forum.com/.
2007 Mar 19
3
Tell me the truth about WINE
...it comes to gaming, only Windows seems to be functionally complete. If I have to install Windows *anyway*, I might as well use it for everything instead of having to reboot every time I feel like playing a game. Realistically, can Linux/WINE replace Windows for a gamer? The question is especially poignant here and now, with Vista on the horizon and DX10 compatibility forcing Windows users to upgrade (for the record, I'm still on 2k by choice, and have no desire to continue using Windows as it becomes more invasive with regard to WGA, DRM, product activation and the like.) I would like an honest...
2009 Dec 17
0
[LLVMdev] updated code size comparison
> However I would prefer to leave these testcases in, unless there is a > strong feeling that they are too distracting. They serve as poignant > little reminders about how easy it is to get volatile wrong... They skew the results in favor of the less careful compilers so they are more than simply distracting, they are unfair. -- Eric Botcazou
2020 Nov 20
4
return (x+1) * 1000
...unction that returns 10 minute slots slot <- function (seconds) { return (seconds %/% 600) * 600 } Obviously I found the issue while debugging and corrected my code with surrounding parenthesis, but I was surprised that the R parser did not catch this syntactic error. This is especially poignant when we have to switch between languages like python where the original line would produce the desired result. Mateo. -- Mateo Obreg?n. On Friday, 20 November 2020 21:58:29 GMT Gabriel Becker wrote: > Hi all, > > I can confirm this occurs for me as well. > > The one thing that...
2014 Sep 30
1
Silence Detection for stream - Linux (Ubuntu 12.04/14.04) ALSA ONLY
2006 Mar 24
3
Picking apart the rails codebase / transitioning from novice
Alright, I''ve done some tinkering and I''ve read through the DHH book. I''d like to humbly solicit some advice from the rails gurus. I''d like to get a real firm grip, and it seems that navigating the actual codebase might be the best course of action. Any advice as to the best route to take for maximum comprehension? What would be the most sensible way to
2007 Sep 01
2
@content_for_layout or changing default fields on "new" page
Hi all, I test my small Rails apps using SQLite3, but I think the problem appeares in every type of database. . When I create table and scaffolding apps, a HTML view is based on columns types. Everything is OK until I want to change preconfigured behaviour. . I created table with a column of type INTEGER, but I wanted to display check box instead of text field and then save 0 or 1 in database.
2020 Nov 20
1
return (x+1) * 1000
...n (seconds %/% 600) * 600 > > > > } > > > > Obviously I found the issue while debugging and corrected my code with > > surrounding parenthesis, but I was surprised that the R parser did not > > catch this syntactic error. > > > > This is especially poignant when we have to switch between languages like > > python where the original line would produce the desired result. > > That's legal code, so the parser can't catch it, it needs to be caught > by some lint-like thing that looks for bad usage. The package check > code has...
2006 Feb 11
4
Starting Ruby On Rails
Hi, i m a web developer(php,ajax). i want to start with ruby on rails. can one suggest me online tutorials for ruby on rails? How would i start with ruby on rails,i knew something about ruby? editor for ruby on rails? Plase..... Thank You. -- Posted via http://www.ruby-forum.com/.
2009 Dec 16
3
[LLVMdev] updated code size comparison
[cross-posting to the GCC and LLVM lists] I've updated the code size results here: http://embed.cs.utah.edu/embarrassing/dec_09/ The changes for this run were: - delete a number of testcases that contained use of uninitialized local variables - turn off frame pointer emission for all compilers - ask all compilers to target x86 + SSE3 - ask all compilers to not emit stack protector
2009 Dec 16
0
[LLVMdev] updated code size comparison
On 12/16/2009 03:21 AM, John Regehr wrote: > Hopefully the results are more fair and useful now. Again, feedback is > appreciated. I would also avoid testcases using volatile. Smaller code on these testcases is often a sign of miscompilation rather than optimization. For example, http://embed.cs.utah.edu/embarrassing/src_harvested_dec_09/076389.c is miscompiled on GCC 3.4 and SunCC
2009 Dec 17
1
[LLVMdev] updated code size comparison
On Thu, Dec 17, 2009 at 19:54, Eric Botcazou <ebotcazou at adacore.com> wrote: >> However I would prefer to leave these testcases in, unless there is a >> strong feeling that they are too distracting.  They serve as poignant >> little reminders about how easy it is to get volatile wrong... > > They skew the results in favor of the less careful compilers so they are more > than simply distracting, they are unfair. Yes, that was my point. If you want to make a separate section for volatile, that would in...
2006 Jul 05
1
Process incoming SOAP requests?
We currently have a SOAP server that processes incoming requests. I''d like to rewrite this system (maintaining the same SOAP interfaces) utilizing RoR. What is the easiest way to go about this? Thanks. -- Posted via http://www.ruby-forum.com/.
2006 Jul 25
3
dynamic languages - how to leverage/make best use?
Hi, Does anyone have any links to, or info on, how best to leverage the power of a dynamic language. That is coming across from Java to Ruby I''m now pondering what would be the typical scenarios where I could actually call upon the power of a dynamic language. This info could be in the form of best practice for dynamic language usage, or dynamic language patters perhaps.
2006 Nov 13
3
(A bit offtopic): A good starting book for ruby programming?
Hi all Guess it''s time for me to dig a bit deeper into the ruby language. Can you recommend some good starting books on ruby programming? Thanks. -- Med venlig hilsen Juri Rischel Jensen Fab:IT ApS Vesterbrogade 50 DK-1620 København Tlf: 70 202 407 / Fax: 33 313 640 www.fab-it.dk / juri@fab-it.dk
2020 Nov 20
0
return (x+1) * 1000
...t <- function (seconds) { > return (seconds %/% 600) * 600 > } > > Obviously I found the issue while debugging and corrected my code with > surrounding parenthesis, but I was surprised that the R parser did not > catch > this syntactic error. > > This is especially poignant when we have to switch between languages like > python where the original line would produce the desired result. > > Mateo. > -- > Mateo Obreg?n. > > On Friday, 20 November 2020 21:58:29 GMT Gabriel Becker wrote: > > Hi all, > > > > I can confirm this occurs f...
2020 Nov 20
0
return (x+1) * 1000
...lot <- function (seconds) { > return (seconds %/% 600) * 600 > } > > Obviously I found the issue while debugging and corrected my code with > surrounding parenthesis, but I was surprised that the R parser did not catch > this syntactic error. > > This is especially poignant when we have to switch between languages like > python where the original line would produce the desired result. That's legal code, so the parser can't catch it, it needs to be caught by some lint-like thing that looks for bad usage. The package check code has lots of that kind of ch...
2007 Aug 23
20
Eliminating bad tests from SuperRedCloth
...be running an older version of this). There are some new things Textile2 does that SRC does not and I''d like to impliment those and also strip out the cruft I mentioned. This may break backwards compatibility for some people''s content (I''m thinking perhaps the poignant test cases), but I think that''s okay with a major release (3 -> 4) such as this would be. You can''t ever move ahead if you don''t own up to mistakes and leave them behind. What do you all think? Can I start cleaning up test cases to be how they ought to be? I&...