Why not require things that are potentially case sensitive to be in quotes?
On Tuesday, December 30, 2014, Alex Peshkoff wrote:
> On 12/30/14 02:15, Daniel Rail wrote:
> > Hi,
> >
> > At December 29, 2014, 7:00 AM, Adriano dos Santos Fernandes wrote:
> >
> >> About config keywords using OS case
On 12/30/14 15:44, Adriano dos Santos Fernandes wrote:
> On 30/12/2014 10:35, Alex Peshkoff wrote:
>>> Would it be feasible to insist that all plug-ins are installed
>>> with lower-case file/directory names on case-sensitive file
>>> systems? (And nothing else will be recognised.)
>>>
>>> Then the
30.12.2014 13:44, Adriano dos Santos Fernandes wrote:
> On 30/12/2014 10:35, Alex Peshkoff wrote:
>>> Would it be feasible to insist that all plug-ins are installed
>>> with lower-case file/directory names on case-sensitive file
>>> systems? (And nothing else will be recognised.)
>>>
>>> Then the
On 30/12/2014 10:35, Alex Peshkoff wrote:
>> Would it be feasible to insist that all plug-ins are installed
>> with lower-case file/directory names on case-sensitive file
>> systems? (And nothing else will be recognised.)
>>
>> Then the content of your config files can be completely
>> case-insens
On 12/30/14 14:42, Geoff Worboys wrote:
> Alex Peshkoff wrote:
>> I wanted to make sure what do we understand under "config
>> keywords". In a sample
>> Key = Value
>> "Key" is obviously config keyword. But what about "Value"?
>> FYI - "Key" is case-INsensitive in FB3. But what about
>> "Value" - i
Alex Peshkoff wrote:
> I wanted to make sure what do we understand under "config
> keywords". In a sample
> Key = Value
> "Key" is obviously config keyword. But what about "Value"?
> FYI - "Key" is case-INsensitive in FB3. But what about
> "Value" - it depends upon usage. Certainly things like
> T
On 12/30/14 02:15, Daniel Rail wrote:
> Hi,
>
> At December 29, 2014, 7:00 AM, Adriano dos Santos Fernandes wrote:
>
>> About config keywords using OS case sensitivity/insensitivity -> makes
>> no sense.
> I totally agree, since that is what Dimitry is referring to in his
> original post.
>
I want
Hi,
At December 29, 2014, 7:00 AM, Adriano dos Santos Fernandes wrote:
> About config keywords using OS case sensitivity/insensitivity -> makes
> no sense.
I totally agree, since that is what Dimitry is referring to in his
original post.
--
Best regards,
Daniel Rail
Senior Software Developer
On 29/12/2014 08:33, Martijn Tonies (Upscene Productions) wrote:
>> -Original Message-
>> From: Alex Peshkoff
>> On 12/29/14 12:07, Martijn Tonies (Upscene Productions) wrote:
>>> IMO,
>>>
>>> case sensitivity is always a bug. ;)
>>>
>> That you should say to posix standard developers :)
29.12.2014 10:51, Alex Peshkoff wrote:
> That's an old problem with writing portable software for case-sensitive
> and case-insensitive (in filenames) operating systems. What do you think
> will be the best solution here?
At the beginning of plugins.conf write comment "all names here are case
>From: Alex Peshkoff
>On 12/29/14 13:33, Martijn Tonies (Upscene Productions) wrote:
>>> -Original Message-
>>> From: Alex Peshkoff
>>> On 12/29/14 12:07, Martijn Tonies (Upscene Productions) wrote:
IMO,
case sensitivity is always a bug. ;)
>>> That you should say to po
On 12/29/14 13:33, Martijn Tonies (Upscene Productions) wrote:
>> -Original Message-
>> From: Alex Peshkoff
>> On 12/29/14 12:07, Martijn Tonies (Upscene Productions) wrote:
>>> IMO,
>>>
>>> case sensitivity is always a bug. ;)
>>>
>> That you should say to posix standard developers :)
>> P
>-Original Message-
>From: Alex Peshkoff
>On 12/29/14 12:07, Martijn Tonies (Upscene Productions) wrote:
>> IMO,
>>
>> case sensitivity is always a bug. ;)
>>
>
>That you should say to posix standard developers :)
>Plugin will just not load on posix system if it's filename is provided
>i
On 12/29/14 12:07, Martijn Tonies (Upscene Productions) wrote:
> IMO,
>
> case sensitivity is always a bug. ;)
>
That you should say to posix standard developers :)
Plugin will just not load on posix system if it's filename is provided
in wrong case.
BTW, it's documented make utility behavior tha
On 12/28/14 13:18, Dimitry Sibiryakov wrote:
> Hello, All.
>
> Plugin names set in pligins.conf on Windows are case sensitive while
> those that are
> used without this config - aren't.
> For example, if I put into plugins.conf line "Plugin = engine12r", and in
> firebird.conf
> refer
IMO,
case sensitivity is always a bug. ;)
With regards,
Martijn Tonies
Upscene Productions
http://www.upscene.com
Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!
Hello, All.
Plugin names set in pligins.conf on Window
Hello, All.
Plugin names set in pligins.conf on Windows are case sensitive while those
that are
used without this config - aren't.
For example, if I put into plugins.conf line "Plugin = engine12r", and in
firebird.conf
refer it as "Engine12r", I'll get "unavailable database" error and
Hello, All.
Plugin names set in pligins.conf on Windows are case sensitive while those
that are
used without this config - aren't.
For example, if I put into plugins.conf line "Plugin = engine12r", and in
firebird.conf
refer it as "Engine12r", I'll get "unavailable database" error and
18 matches
Mail list logo
