02.09.2014 23:10, Gabor Boros wrote:
>
> Available snapshots date is august 27. Is it a known issue?
Yes, Windows builds are broken.
Dmitry
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.or
Hi,
Available snapshots date is august 27. Is it a known issue?
Gabor
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
Firebird-Devel mailing list, web interface at
https://lists.sourcefor
2014-09-02 21:31 GMT+04:00 Dmitry Yemanov :
> Let me disagree.
+1
--
Roman Simakov
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
Firebird-Devel mailing list, web interface at
https://l
02.09.2014 21:27, Dimitry Sibiryakov wrote:
> if (temp.rpb_flags & rpb_delta)
> temp.rpb_prior = data;
>
> doesn't look much better.
Let me disagree.
Dmitry
--
Slashdot TV.
Video for Nerds. Stuff that mat
02.09.2014 19:08, Dmitry Yemanov wrote:
> This example violates the project coding style.
Oh, yes. But
if (temp.rpb_flags & rpb_delta)
temp.rpb_prior = data;
doesn't look much better.
--
WBR, SD.
--
Slas
02.09.2014 18:35, Dimitry Sibiryakov wrote:
>
> When was decided that one-line blocks must not be enclosed with parentheses?
It didn't change for the past few years:
http://www.firebirdsql.org/en/coding-style/
http://geosoft.no/development/cppstyle.html
"82. Single statement if-else, for or whil
02.09.2014 19:05, Dimitry Sibiryakov wrote:
> if (some condition &&
> some other condition)
> hardly recognized line that doing something;
This example violates the project coding style.
Dmitry
-
Access rights for CREATE DATABASE operator
--
Key: CORE-4538
URL: http://tracker.firebirdsql.org/browse/CORE-4538
Project: Firebird Core
Issue Type: Sub-task
Components: Engine, ISQL
Something to keep in mind is that code is written once, modified a couple
of times, and read hundreds of times. Legitibilty is everything from a
maintenance perspective.
I've written, oh, close to a million lines of code. Two 4gls, four
relational database systems, a JVM, a search engine, a temp
Users were told they could expect a FB3 beta on August 31. This date has been
moved back several times now.
What's the new date, based on an honest and realistic assessment?
How many times will this happen before interested users stop watching and
waiting?
On Aug 31, 2014, at 7:51 AM, Carl
On Tue, 02 Sep 2014 16:11:43 +0100, Lester Caine
wrote:
> On 02/09/14 16:00, Mark Rotteveel wrote:
>> Braces around single statements would have made this bug less likely.
> Have made many bugs less likely ...
> It's not 'dangerous' just a little more error prone.
> My IDE code completion is set t
On 02/09/2014 12:05, Dimitry Sibiryakov wrote:
> 02.09.2014 17:00, James Starkey wrote:
>> Mandatory indentation makes it clear.
>No. With tabstop == 4, it is placed exactly under if's condition,
> pretending to be
> condition's continuation:
>
> if (some condition &&
> some oth
On 02/09/2014 12:00, Mark Rotteveel wrote:
> On Tue, 02 Sep 2014 11:43:54 -0300, Adriano dos Santos Fernandes
> wrote:
>> On 02/09/2014 11:35, Dimitry Sibiryakov wrote:
>>>Hi, All.
>>>
>>>When was decided that one-line blocks must not be enclosed with
>>>parentheses? It is a
>>> rather
OR'ed optimization in 3.0 is ineffective when `WHERE` clause contains two
expression and they do NOT match order of SP input arguments
--
Key: CORE-
On 02/09/14 16:00, Mark Rotteveel wrote:
> Braces around single statements would have made this bug less likely.
Have made many bugs less likely ...
It's not 'dangerous' just a little more error prone.
My IDE code completion is set to add the braces on every language.
--
Lester Caine - G8HFL
On Tue, 02 Sep 2014 17:00:01 +0200, Mark Rotteveel
wrote:
> On Tue, 02 Sep 2014 11:43:54 -0300, Adriano dos Santos Fernandes
> wrote:
>> On 02/09/2014 11:35, Dimitry Sibiryakov wrote:
>>>Hi, All.
>>>
>>>When was decided that one-line blocks must not be enclosed with
>>>parentheses? It
02.09.2014 17:00, James Starkey wrote:
> Mandatory indentation makes it clear.
No. With tabstop == 4, it is placed exactly under if's condition, pretending
to be
condition's continuation:
if (some condition &&
some other condition)
hardly recognized line that doing som
September 4, 1984.
Why do you say it's dangerous? Mandatory indentation makes it clear.
Clear code separated into functional block is more legible if not cluttered
with superfluous punctuation.
On Tuesday, September 2, 2014, Dimitry Sibiryakov wrote:
>Hi, All.
>
>When was decided that
On Tue, 02 Sep 2014 11:43:54 -0300, Adriano dos Santos Fernandes
wrote:
> On 02/09/2014 11:35, Dimitry Sibiryakov wrote:
>>Hi, All.
>>
>>When was decided that one-line blocks must not be enclosed with
>>parentheses? It is a
>> rather dangerous style...
>>
> It's not, it was not and it
02.09.2014 16:43, Adriano dos Santos Fernandes wrote:
> It's not, it was not and it will never be a dangerous style.
>
> Everything is dangerous if you write code without attention.
For me it looks like code obfuscation. May be harmless, but unpleasant.
--
WBR, SD.
---
On 02/09/2014 11:35, Dimitry Sibiryakov wrote:
>Hi, All.
>
>When was decided that one-line blocks must not be enclosed with
> parentheses? It is a
> rather dangerous style...
>
It's not, it was not and it will never be a dangerous style.
Everything is dangerous if you write code without
Hi, All.
When was decided that one-line blocks must not be enclosed with parentheses?
It is a
rather dangerous style...
--
WBR, SD.
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.o
On Tue, 2 Sep 2014 15:34:33 +0300, marius adrian popa
wrote:
> MariaDB switched to the PCRE regular expression library
>
>
https://mariadb.com/kb/en/mariadb/documentation/functions-and-operators/string-functions/regular-expressions-functions/pcre-regular-expressions/+source/
>
> I wonder how har
MariaDB switched to the PCRE regular expression library
https://mariadb.com/kb/en/mariadb/documentation/functions-and-operators/string-functions/regular-expressions-functions/pcre-regular-expressions/+source/
I wonder how hard it will be to switch to it ?
Idea from Jiri
https://twitter.com/cinc
On 02/09/2014 02:42, Dmitry Yemanov wrote:
> Agreed wholeheartedly. The point was that it restores exactly what was
> possible prior to v3 without compromising the system tables protection
> and that it's easy (if not easiest) to implement. I didn't pretent it
> looking elegant.
>
>
Not only the
Hi,
If I do "similar to '[a-z\_-]' escape '\'" I got a error about invalid pattern.
The "-" is causing problems. Surprisingly doing '[a-z-\_]' is fine and also
'[a-z-]' is fine. Testing the first regex on various parsers it worked. Why it
doesn't work on Firebird?
--
Mgr. Jiří Činčura
Indepen
I quickly also checked Postgres and it works there.
--
Mgr. Jiří Činčura
Independent IT Specialist
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
Firebird-Devel mailing list, web interface
Another possible solution: a set statement that controls the state of the DDL
engine to save source or not (defalut is save). Essentially the same as the
dpb item but syntax. The positive is that it doesn't mess with the syntax of
already complex declarations and needs only appear once in a sc
28 matches
Mail list logo
